Intermittently accessible drive #180
Comments
|
Error 'Scsi error - ILLEGAL REQUEST:2104' occurred while reading 'BD-RE PIONEER BD-RW BDR-S12U 1.01 AIDL005196WL' at offset '983040' |
|
Happened again. Error 'Scsi error - ILLEGAL REQUEST:2104' occurred while reading 'BD-RE PIONEER BD-RW BDR-S12U 1.01 AIDL005196WL' at offset '524288' |
|
CLEAN YOUR DISKS! unable to read at a specific offset is a dirty/scratched disk! even if it's clean/brand new clean it again not to mention pioneer support is iffy. why not just use a tried and true drive? |
|
Not a problem with my disk. As I stated in the first post the drive becomes unresponsive within the docker. Restarting the machine sometimes resets the problem. Pionner support being iffy is news to me. Any way you know for me to test that? |
|
could be a cable issue, power issue. the makemkv forum clearly states pioneer support is experimental. i would start by trying the drive in a windows machine. not docker, not vm. see if the issue persists. |
|
Since a power cycle can fix the issue temporarily, the problem doesn't seem to be the container itself. |
|
Correct. |
|
I am having a similar problem but with an LG drive. It started yesterday when I tried to begin ripping new movies we received for Christmas. The first one failed twice due to an "Scsi error - Illegal Request." I tried a different disc to see if maybe it was an issue with the disc. However, the drive no longer would recognize any disc placed into it. I restarted the unRaid server and tried ripping a movie before going to bed. I don't have the logs, but it was unsuccessful and the container was disconnected. Now, MakeMKV keeps saying it cannot find the optical drive. However, I checked the terminal using "lsscsi -g" and verified I am using the correct device parameters. It shows up in the system. When I restart MakeMKV, the logs show it finding the device. However, when I connect to the web interface, it says it cannot find an optical drive. Container log below 12/26/2023
|
Current Behavior
Docker works as expected but sooner or later it will state that drive is inaccessible. This seems to occur in between disks, as in, if it starts to read a disk it will complete the disk.
Restarting the docker doesn't help, the only solution I've found is to power cycle the host, which only works some of the time.
If drive was detected at boot and it fails to access the drive later it complains about something or other offset. I will update next time it errors out.
Upon restart of the container the only error is the generic "The program can't find any usable optical drives." error.
Expected Behavior
Drive is accessible all the time.
Steps To Reproduce
Start docker.
Wait.
Environment
Container creation
docker run
-d
--name='MakeMKV'
--net='bridge'
-e TZ="America/Los_Angeles"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="Tower"
-e HOST_CONTAINERNAME="MakeMKV"
-e 'MAKEMKV_KEY'='BETA'
-e 'AUTO_DISC_RIPPER'='1'
-e 'AUTO_DISC_RIPPER_EJECT'='1'
-e 'AUTO_DISC_RIPPER_PARALLEL_RIP'='0'
-e 'AUTO_DISC_RIPPER_BD_MODE'='mkv'
-e 'AUTO_DISC_RIPPER_FORCE_UNIQUE_OUTPUT_DIR'='0'
-e 'AUTO_DISC_RIPPER_NO_GUI_PROGRESS'='0'
-e 'USER_ID'='99'
-e 'GROUP_ID'='100'
-e 'UMASK'='000'
-e 'APP_NICENESS'=''
-e 'DISPLAY_WIDTH'='1280'
-e 'DISPLAY_HEIGHT'='768'
-e 'SECURE_CONNECTION'='0'
-e 'X11VNC_EXTRA_OPTS'=''
-e 'AUTO_DISC_RIPPER_MAKEMKV_PROFILE'=''
-e 'AUTO_DISC_RIPPER_INTERVAL'='5'
-e 'AUTO_DISC_RIPPER_MIN_TITLE_LENGTH'=''
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:5800]'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/makemkv-icon.png'
-p '7806:5800/tcp'
-p '7906:5900/tcp'
-v '/mnt/user/Media/':'/storage':'ro'
-v '/mnt/user/Media/Output/':'/output':'rw'
-v '/mnt/user/appdata/MakeMKV':'/config':'rw'
--device='/dev/sr0:/dev/sr0'
--device='/dev/sg2:/dev/sg2' 'jlesage/makemkv'
Container log
Container inspect
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: