Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No access to Optical Drive (unRaid) #82

Closed
BrainGameFactory opened this issue Jul 9, 2020 · 8 comments
Closed

No access to Optical Drive (unRaid) #82

BrainGameFactory opened this issue Jul 9, 2020 · 8 comments

Comments

@BrainGameFactory
Copy link

Hi i did everything as described but it will not recognize my Optical Drive.

grafik

The Log output for the right drives:
[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/sg2], group 19.
[cont-init.d] 95-check-optical-drive.sh: exited 0.

Here my Extra Parameters : --device /dev/sr0 --device /dev/sg2

@jlesage
Copy link
Owner

jlesage commented Jul 10, 2020

Can you try to enable privileged mode to see if this makes MakeMKV to see your drive ?

@BrainGameFactory
Copy link
Author

Sorry dose not work with privileged mode enabled

@jlesage
Copy link
Owner

jlesage commented Dec 31, 2020

It seems that some drives are not recognized by MakeMKV, event though they are seen correctly by Linux. I'm suspecting an issue on MakeMKV side.

See #98.

@devlinandrew
Copy link

Switching to privileged mode fixed this issue for me.

@jlesage
Copy link
Owner

jlesage commented Sep 21, 2021

@devlinandrew, could you share the permissions/ownership of Linux devices associated to your optical drive ? E.g. ls -l /dev/sr0 /dev/sg2

@devlinandrew
Copy link

devlinandrew commented Sep 22, 2021

@jlesage See attached.

923AE022-8090-4D7C-BFCA-CFD4770C5F79

@whiteadam
Copy link

I've encountered this problem a few times as well and noticed that a full system reboot "fixes" it, but not a docker restart. I'll try to gather more info the next time it happens.

@jlesage
Copy link
Owner

jlesage commented Feb 13, 2023

and noticed that a full system reboot "fixes" it, but not a docker restart

That seems to be the "fix" for other people also.

Closing this issue. Please re-open if needed.

@jlesage jlesage closed this as completed Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants