Unusual situation for "The program can't find any useable optical drives."

[blackvykyng]

I'm very new to Linux distros, using Unraid for the past several months having crashed it several times (that's kind of how I learn, lol). I had been using Makemkv for the past five months and I liked it so much I paid for the license key. For the past month, I've been getting these errors, rather "Warnings" an the "This program can't find any useable optical drives" message. I took a look into the logs and found a bunch of "Warning: Could not resolve keysym [variable]". I've made all the usual checks that I can think of searched the forums for similar issues, but to no avail. I've attached a copy of the log. Any help would be appreciated Log for_ MakeMKV.txt .

[C4Wiz]

"This program can't find any useable optical drives" .

look in the log for this:

[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/sg1], but it is not usable because:
[cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sg1 is not exposed to the container.
[cont-init.d] 95-check-optical-drive.sh: no usable optical drive found.
[cont-init.d] 95-check-optical-drive.sh: exited 0.

you need to pass both like this:

—device /dev/sr0 --device /dev/sg1

[C4Wiz]

I took a look into the logs and found a bunch of "Warning: Could not resolve keysym [variable]". .

I can confirm the errors, not sure when it started, container still works as expected.

[C4Wiz]

@jlesage

you should add this to the overview:

NOTE: For the container to have access to your optical drive(s), you need to
add them to your containers Extra Parameters configuration. An optical drive is 
represented by two Linux device files: /dev/srX and /dev/sgY. For optimal performance, the container needs
both of them.This is done by clicking the button on the top right labeled Basic View to
switch to Advanced View. To determine the right devices to use, start the container and
look at its log. Then copy and Paste the Devices to the Extra Parameters Line.

Example Log Output:
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/sg1, group 19.
cont-init.d 95-check-optical-drive.sh: exited 0.

then add as follows:
—device /dev/sr0 --device /dev/sg1

[blackvykyng]

The extra parameters were added prior to requesting help (--device /dev/sr0 --device /dev/sg4). However, app does not work as intended.

On Fri, Jan 21, 2022 at 7:18 AM C4Wiz @.***> wrote:

@jlesage https://github.com/jlesage

you should add this to the overview:

NOTE: For the container to have access to your optical drive(s), you need to

add them to your containers Extra Parameters configuration. An optical drive is

represented by two Linux device files: /dev/srX and /dev/sgY. For optimal performance, the container needs

both of them.This is done by clicking the button on the top right labeled Basic View to

switch to Advanced View. To determine the right devices to use, start the container and

look at its log. Then copy and Paste the Devices to the Extra Parameters Line.

Example Log Output:

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/sg1, group 19.

cont-init.d 95-check-optical-drive.sh: exited 0.

then add as follows:

—device /dev/sr0 --device /dev/sg1

— Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-makemkv/issues/135#issuecomment-1018602747, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALXUDVDMNI66MFYFYHG22KTUXF2NJANCNFSM5MPRC7UA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[blackvykyng]

Also, I tried deleting the "sg4" device portion to see if the logs would catch it but...nothing.

On Fri, Jan 21, 2022 at 8:04 AM Zero Gravity @.***> wrote:

The extra parameters were added prior to requesting help (--device /dev/sr0 --device /dev/sg4). However, app does not work as intended.

On Fri, Jan 21, 2022 at 7:18 AM C4Wiz @.***> wrote:

@jlesage https://github.com/jlesage

you should add this to the overview:

NOTE: For the container to have access to your optical drive(s), you need to

add them to your containers Extra Parameters configuration. An optical drive is

represented by two Linux device files: /dev/srX and /dev/sgY. For optimal performance, the container needs

both of them.This is done by clicking the button on the top right labeled Basic View to

switch to Advanced View. To determine the right devices to use, start the container and

look at its log. Then copy and Paste the Devices to the Extra Parameters Line.

Example Log Output:

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/sg1, group 19.

cont-init.d 95-check-optical-drive.sh: exited 0.

then add as follows:

—device /dev/sr0 --device /dev/sg1

— Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-makemkv/issues/135#issuecomment-1018602747, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALXUDVDMNI66MFYFYHG22KTUXF2NJANCNFSM5MPRC7UA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[C4Wiz]

The extra parameters were added prior to requesting help (--device /dev/sr0 --device /dev/sg4). However, app does not work as intended.> remove the () use: --device /dev/sr0 --device /dev/sg4

post output of the makemkv container log showing cont-init.d 95-check-optical-drive.sh: executing...

[blackvykyng]

Sorry, not sure what you're asking or rather how to do what you're asking.

[C4Wiz]

Sorry, not sure what you're asking or rather how to do what you're asking.

Look for that portion in the log and post it

[blackvykyng]

Yeah, It's not there. All I see looks like references to vnc.

Errors from xkbcomp are not fatal to the X server [services.d] starting x11vnc... [services.d] starting app... [x11vnc] starting... [app] starting MakeMKV... [services.d] done.

[C4Wiz]

I would delete the container and image and then re add it

[blackvykyng]

I don't see anything that looks like your example in the makemkv log.

[blackvykyng]

I've tried that several times. It comes up the same. But I will try it again.

[C4Wiz]

How are you installing it?

[blackvykyng]

I'm installing it as a docker app on Unraid.

[C4Wiz]

I get that but are you installing it from the community apps plugin? Or commandline? Xml file?

[blackvykyng]

Yes I'm installing it from community apps

[jlesage]

You can get the full log by running the command docker logs MakeMKV.

[blackvykyng]

kk will do

[C4Wiz]

I just click the docker icon then click log

[blackvykyng]

Usually, I do the same. but it was not listing everything. Running it via command gave me everything. I had removed the "--device /dev/sg4" portion so that I could get a return for the correct setting. It gave me "sg6" I changed it in MakeMKV and of course now it works.

[C4Wiz]

Yea, it can change. I usually add them all

[blackvykyng]

However, it still gives me all these warnings and selecting the logs from the docker doesn't give me any of the container info. Why is that?

[blackvykyng]

How do I add them all?

[C4Wiz]

--device /dev/sr0 --device /dev/sg0 --device /dev/sg1 --device /dev/sg2 up to 10 or so, if you get a error then remove them 1 by one till the error stops

[jlesage]

You can ignore warnings, they are harmless.

[C4Wiz]

@jlesage is it related to this? https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/137

[blackvykyng]

Thanks, I didn't know I could do that. I'll remember that for next time.

Thanks for all you r help. Cheers!

On Fri, Jan 21, 2022, 12:22 PM C4Wiz @.***> wrote:

@jlesage https://github.com/jlesage is it related to this? https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/137

— Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-makemkv/issues/135#issuecomment-1018831932, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALXUDVGDAVWTZOGOVVLYYCDUXG56XANCNFSM5MPRC7UA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[bjaurelio]

I too am getting an error that MakeMKV cannot find any useable drives. The container was working for me just a couple days ago. I checked the log, and it finds the drive. However, the UI states that it did not find a drive. Any help would be much appreciated.

[jlesage]

Can you try to run and see if drive is seen:

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

Also, make sure to update the Docker image to the latest version.

[bjaurelio]

Here's the terminal screen from running that command. It does not see the drive even though the log says it's found. Unraid says my container is up to date. I tried to force an update, but it's still the same version.