Optical Drive not being found

[saarg]

Ok, looks like permissions issue. Please post one more output of

Code: Select all

ls -la /dev/sg*

Code: Select all

root@8501bf9102c1:/# ls -la /dev/sg*
ls: cannot access /dev/sg*: No such file or directory

Running this in a docker container, and only pass through /dev/sr*. Checking ls -la /dev/sg* gives this output on the host.

Code: Select all

root@unXeon:~# ls -la /dev/sg*
crw-rw---- 1 root disk  21, 0 Jan 22 08:51 /dev/sg0
crw-rw---- 1 root disk  21, 1 Jan 22 08:51 /dev/sg1
crw-rw---- 1 root disk  21, 2 Jan 22 08:51 /dev/sg2
crw-rw---- 1 root disk  21, 3 Jan 22 08:51 /dev/sg3
crw-rw---- 1 root cdrom 21, 4 Jan 22 08:51 /dev/sg4

Starting the container in privileged mode solves the problem. I guess you have changed the way a drive is accessed/detected since this worked in earlier versions?
I also tested to pass through only /dev/sg4 and that also works. So going forward, it's /dev/sg* MakeMKV looks for when detecting a drive?

Thanks for the help

[spl147]

Ok, looks like permissions issue. Please post one more output of

Code: Select all

ls -la /dev/sg*

Code: Select all

root@8501bf9102c1:/# ls -la /dev/sg*
ls: cannot access /dev/sg*: No such file or directory

Running this in a docker container, and only pass through /dev/sr*. Checking ls -la /dev/sg* gives this output on the host.

Code: Select all

root@unXeon:~# ls -la /dev/sg*
crw-rw---- 1 root disk  21, 0 Jan 22 08:51 /dev/sg0
crw-rw---- 1 root disk  21, 1 Jan 22 08:51 /dev/sg1
crw-rw---- 1 root disk  21, 2 Jan 22 08:51 /dev/sg2
crw-rw---- 1 root disk  21, 3 Jan 22 08:51 /dev/sg3
crw-rw---- 1 root cdrom 21, 4 Jan 22 08:51 /dev/sg4

Starting the container in privileged mode solves the problem. I guess you have changed the way a drive is accessed/detected since this worked in earlier versions?
I also tested to pass through only /dev/sg4 and that also works. So going forward, it's /dev/sg* MakeMKV looks for when detecting a drive?

Thanks for the help

im running MakeMKV in a docker on unRAID, i left the device as /dev/sr0, and just toggled ON privileged and it works again!

[Djoss]

im running MakeMKV in a docker on unRAID, i left the device as /dev/sr0, and just toggled ON privileged and it works again!

It seem that passing both /dev/sr? and /dev/sg? associated to your drive also works, without the need of the privileged mode.

[spl147]

im running MakeMKV in a docker on unRAID, i left the device as /dev/sr0, and just toggled ON privileged and it works again!

It seem that passing both /dev/sr? and /dev/sg? associated to your drive also works, without the need of the privileged mode.

how do you pass both?

[Wild Penguin]

I'm confused, why is it looking for /dev/sgX? No Linux distribution I've used has a CD drive named that way.

Code: Select all

$ LANG=C ls -la /dev/sg* # Because my locale is not english
ls: cannot access '/dev/sg*': No such file or directory
$ ls -la /dev/sr*
brw-rw----+ 1 root optical 11, 0 20. 1. 16:43 /dev/sr0
$ ls -la /dev/cd*
lrwxrwxrwx 1 root root 3 20. 1. 16:43 /dev/cdrom -> sr0

How is this a permission issue?

[Djoss]

im running MakeMKV in a docker on unRAID, i left the device as /dev/sr0, and just toggled ON privileged and it works again!

It seem that passing both /dev/sr? and /dev/sg? associated to your drive also works, without the need of the privileged mode.

how do you pass both?

Just add another "--device" parameter to the "docker run" command (e.g. --device /dev/sgX).

[Djoss]

I'm confused, why is it looking for /dev/sgX? No Linux distribution I've used has a CD drive named that way.

Code: Select all

$ LANG=C ls -la /dev/sg* # Because my locale is not english
ls: cannot access '/dev/sg*': No such file or directory
$ ls -la /dev/sr*
brw-rw----+ 1 root optical 11, 0 20. 1. 16:43 /dev/sr0
$ ls -la /dev/cd*
lrwxrwxrwx 1 root root 3 20. 1. 16:43 /dev/cdrom -> sr0

How is this a permission issue?

Not sure why you don't have /dev/sgX device on your system, but in my case, the optical drive can be accessed by both /dev/srX and /dev/sgY, I think they are just 2 different ways to access the drive: /dev/sdX is a block device while /dev/sgY is used to communicate via SCSI commands.

[saarg]

im running MakeMKV in a docker on unRAID, i left the device as /dev/sr0, and just toggled ON privileged and it works again!

It seem that passing both /dev/sr? and /dev/sg? associated to your drive also works, without the need of the privileged mode.

You don't need both, only the /dev/sg* device. You see which device is the DVD/BD-ROM by the ls -la /dev/sg* listing. The one which is in the cdrom group is the drive.

[spl147]

im running MakeMKV in a docker on unRAID, i left the device as /dev/sr0, and just toggled ON privileged and it works again!

It seem that passing both /dev/sr? and /dev/sg? associated to your drive also works, without the need of the privileged mode.

You don't need both, only the /dev/sg* device. You see which device is the DVD/BD-ROM by the ls -la /dev/sg* listing. The one which is in the cdrom group is the drive.

my docker will not load the Webui without both sr0 and sg1

[saarg]

my docker will not load the Webui without both sr0 and sg1

Then you are using the wrong container

[spl147]

my docker will not load the Webui without both sr0 and sg1

Then you are using the wrong container

LOL, using the jlesage/MakeMKV container

[mike admin]

You don't need both, only the /dev/sg* device. You see which device is the DVD/BD-ROM by the ls -la /dev/sg* listing. The one which is in the cdrom group is the drive.

You DO need both.

Starting from 1.10.8 the /dev/sgX that corresponds to drive is required . MakeMKV will work without access to /dev/srX , but performance will be slow.

MakeMKV figures out device names by analyzing /sys/bus/scsi, same way as lsscsi does.

[saarg]

You don't need both, only the /dev/sg* device. You see which device is the DVD/BD-ROM by the ls -la /dev/sg* listing. The one which is in the cdrom group is the drive.

You DO need both.

Starting from 1.10.8 the /dev/sgX that corresponds to drive is required . MakeMKV will work without access to /dev/srX , but performance will be slow.

MakeMKV figures out device names by analyzing /sys/bus/scsi, same way as lsscsi does.

I just checked if the drive was found. I didn't notice that the speed was slower though and I have ripped about 6 discs.

[Djoss]

You DO need both.

Starting from 1.10.8 the /dev/sgX that corresponds to drive is required . MakeMKV will work without access to /dev/srX , but performance will be slow.

MakeMKV figures out device names by analyzing /sys/bus/scsi, same way as lsscsi does.

Thanks Mike for confirming and clarifying the new requirements!

[JohnJasonJordan]

You DO need both.
Starting from 1.10.8 the /dev/sgX that corresponds to drive is required . MakeMKV will work without access to /dev/srX , but performance will be slow.
MakeMKV figures out device names by analyzing /sys/bus/scsi, same way as lsscsi does.

My Ubuntu 14.04.5 computer has a built-in Blu-ray drive and a USB DVD drive. I looked at /sys/bus/scsi and came away shaking my head. I understood nothing of the many folders and sub-sub-sub folders in there.
When all this started I went back to 1.10.8, which works fine. Before I try to reinstall 1.10.10, could we have an idiot's guide for how to tell 1.10.10 where the drives are?