www.makemkv.com

MakeMKV support forum
It is currently Wed Jul 18, 2018 8:46 am

All times are UTC




Post new topic Reply to topic  [ 90 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6  Next
Author Message
PostPosted: Mon Jan 22, 2018 1:28 pm 
Offline

Joined: Sat Jan 20, 2018 12:14 pm
Posts: 6
mike admin wrote:
Ok, looks like permissions issue. Please post one more output of
Code:
ls -la /dev/sg*


Code:
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:
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 :D


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 2:48 pm 
Offline

Joined: Mon Dec 10, 2012 4:59 pm
Posts: 82
saarg wrote:
mike admin wrote:
Ok, looks like permissions issue. Please post one more output of
Code:
ls -la /dev/sg*


Code:
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:
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 :D


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


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 3:00 pm 
Offline

Joined: Tue Jun 13, 2017 2:56 pm
Posts: 8
Quote:
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.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 3:01 pm 
Offline

Joined: Mon Dec 10, 2012 4:59 pm
Posts: 82
Djoss wrote:
Quote:
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?


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 3:06 pm 
Offline

Joined: Sun Nov 19, 2017 5:25 pm
Posts: 3
I'm confused, why is it looking for /dev/sgX? No Linux distribution I've used has a CD drive named that way.

Code:
$ 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?


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 4:26 pm 
Offline

Joined: Tue Jun 13, 2017 2:56 pm
Posts: 8
spl147 wrote:
Djoss wrote:
Quote:
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).


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 4:31 pm 
Offline

Joined: Tue Jun 13, 2017 2:56 pm
Posts: 8
Wild Penguin wrote:
I'm confused, why is it looking for /dev/sgX? No Linux distribution I've used has a CD drive named that way.

Code:
$ 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.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 4:40 pm 
Offline

Joined: Sat Jan 20, 2018 12:14 pm
Posts: 6
Djoss wrote:
Quote:
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.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 4:46 pm 
Offline

Joined: Mon Dec 10, 2012 4:59 pm
Posts: 82
saarg wrote:
Djoss wrote:
Quote:
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


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 5:08 pm 
Offline

Joined: Sat Jan 20, 2018 12:14 pm
Posts: 6
spl147 wrote:
my docker will not load the Webui without both sr0 and sg1


Then you are using the wrong container :wink:


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 5:11 pm 
Offline

Joined: Mon Dec 10, 2012 4:59 pm
Posts: 82
saarg wrote:
spl147 wrote:
my docker will not load the Webui without both sr0 and sg1


Then you are using the wrong container :wink:

LOL, using the jlesage/MakeMKV container


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 9:27 pm 
Offline

Joined: Wed Nov 26, 2008 2:26 am
Posts: 3386
saarg wrote:
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.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 10:25 pm 
Offline

Joined: Sat Jan 20, 2018 12:14 pm
Posts: 6
mike admin wrote:
saarg wrote:
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.


Top
 Profile  
Reply with quote  
PostPosted: Mon Jan 22, 2018 11:28 pm 
Offline

Joined: Tue Jun 13, 2017 2:56 pm
Posts: 8
mike admin wrote:
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!


Top
 Profile  
Reply with quote  
PostPosted: Tue Jan 23, 2018 4:36 am 
Offline

Joined: Mon Jun 19, 2017 11:47 pm
Posts: 9
mike admin wrote:
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?


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 90 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group