jlesage / docker-makemkv

Docker container for MakeMKV
MIT License
423 stars 48 forks source link

Can't find optical drives #72

Closed jamesmorganti closed 4 years ago

jamesmorganti commented 4 years ago

Hi,

I'm trying to rip some DVDs onto our NAS, running on Ubuntu 18.04.4, docker community edition 19.03.8.

The optical disc is on /dev/sr0 and /dev/sg0 as confirmed by running the container without passing any devices with the --device flag. I've since passed both in:

docker run -d \

    --name=makemkv \

    -p 5801:5800 \

    -v /docker/appdata/makemkv:/config:rw \

    -v $HOME:/storage:ro \

    -v $HOME/MakeMKV/output:/output:rw \

     --device /dev/sr0 \

     --device /dev/sg0 \

jlesage/makemkv

On a whim, I tried all the other sgX values, none worked. The only srX is sr0. Privileged mode doesn't help either.

After around 20 seconds after booting, the pane at the bottom states:

The program can't find any usable optical drives.

The container can extract MKVs from an ISO from the hard drive. By using your handbrake container, I can rip the DVD from /dev/sr0 but once I move onto the blurays I've got to do, handbrake won't work. I've tried v1.13.1 and latest of your makemkv container.

The logs are:

[cont-init.d] 90-makemkv.sh: exited 0.
[cont-init.d] 95-check-optical-drive.sh: executing...
[cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives...
[cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg0], group 24.
[cont-init.d] 95-check-optical-drive.sh: exited 0.
[cont-init.d] 96-install-autodiscripper-srv.sh: executing...
[cont-init.d] 96-install-autodiscripper-srv.sh: automatic disc ripper disabled.
[cont-init.d] 96-install-autodiscripper-srv.sh: exited 0.
[cont-init.d] done.

Permissions for the device seem fine:

$ ls -la /dev/sg*
   crw-rw-rw-+ 1 root cdrom 21, 0 Apr 12 19:27 /dev/sg0
   crw-rw----  1 root disk  21, 1 Apr 12 19:27 /dev/sg1
   crw-rw----  1 root disk  21, 2 Apr 12 19:27 /dev/sg2
   crw-rw----  1 root disk  21, 3 Apr 12 19:27 /dev/sg3
   crw-rw----  1 root disk  21, 4 Apr 12 19:27 /dev/sg4

$ ls -la /dev/sr*
   brw-rw-rw-+ 1 root cdrom 11, 0 Apr 13 00:53 /dev/sr0

Have you got any advice I could try?

Many thanks, James

jlesage commented 4 years ago

If privileged mode didn't help, I'm not sure what could be the problem. Could you provide the output of :

docker exec -ti <container name> /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999

Also, try latest image, which have an updated version MakeMKV.

jamesmorganti commented 4 years ago

Hi,

I've attached the output of the command and updated to the newest version of the image.

$ docker exec -ti makemkv /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.15.1 linux(x64-release) started","%1 started","MakeMKV v1.15.1 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
MSG:5042,0,0,"The program can't find any usable optical drives.","The program can't find any usable optical drives."
DRV:0,256,999,0,"","",""
DRV:1,256,999,0,"","",""
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
TCOUNT:0

I've also reinstalled ubuntu which aside from changing the drive mappings (which I've updated) hasn't helped. I'm leaning towards thinking this is an issue with the specific drive I'm using and MakeMKV, as I tried MakeMKV with this drive on a windows laptop to no avail.

Thanks, James

jlesage commented 4 years ago

Looks like MakeMKV is not seeing the drive. And if you tried on a laptop and the drive is still not seen, then it's definitely an issue/incompatibility with MakeMKV.

jamesmorganti commented 4 years ago

Yeah I think that's the most likely scenario unfortunately. I'll mark this as closed and do some more research before reporting a bug to MakeMKV directly.

Thanks