-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Disc not auto ejecting after rip is finished #84
Comments
I've tried tinkering with it all weekend still no luck, if anyone has any ideas |
Can you provide the container's log ( |
When I do a sudo docker exec makemkv lsscsi -g -k [4:0:0:0] cd/dvd HL-DT-ST BD-RE WH16NS60 1.02 /dev/sr0 /dev/sg0 |
First messages are missing from the logs you provided. You may need to restart the container and take them again. I think you may need to expose additional devices to the container. This should be indicated in the container's log. |
Thanks, try to also expose |
I have the same issue but I think a different situation. I'm running this docker container on a Synology NAS with an externally (USB) attached dvd drive. The host controller for this drive is showing as a dash.
And the docker logs show this:
Is this just a limitation of the controller used for the external dvd drive or is there something I can do? Backup works fine if I just specify /dev/sg4 but will not eject when completed. |
Ever sort this out? Seems to me that synology doesn't have the right kernel support that the app expects. I've managed to get auto ripping but not auto ejecting to work. |
Same here, Synology, even in command line it doesn't work:
But ripping goes through totally fine |
Can you try with the latest image to see if it's better ? |
I am having the same issue with a QNAP NAS. |
Can you share the container's log ? |
[autodiscripper] [makemkvcon] Copy complete. 7 titles saved. |
Same Problem here. My setup "Proxomox Host with BlueRay Drive" --> Bindmount to unpriviliged LXC container running alpine linux --> Docker container I can eject the drive on each stage but not inside the docker container. I assume it has something to do how docker is mounting the devices: From inside the docker container: The drives are mounted as tmpfs (none) not as actual devices:
ChatGPT says: "none on /dev/sr0: This means that there is no physical device mounted at /dev/sr0. Instead, it's a virtual filesystem." Maybe therefore the eject command refuses to "talk" to the drive, cause it doesn't find any real device:
|
What about ejecting from the GUI ? Is it working ? |
Also, please share the full container log. |
Yes, this is working fine 👍🏻 |
full container log:
|
Can you try to see if ejection works with:
|
Amazing app, works like a charm, and stores the disk on my server. However when the rip is finished it does not eject.
I am running ubuntu server 18.04 lts
the code I used
sudo docker run -d --restart unless-stopped
--name=makemkv
-p 5800:5800
-v /docker/appdata/makemkv:/config:rw
-v $HOME:/storage:ro
-v $HOME/mnt/media/:/output:rw
-e AUTO_DISC_RIPPER=1
-e AUTO_DISC_RIPPER_EJECT=1
-e AUTO_DISC_RIPPER_PARALLEL_RIP=1
-e AUTO_DISC_RIPPER_MIN_TITLE_LENGTH=1200
--device /dev/sg0
--device /dev/sg1
jlesage/makemkv
I tried to change -e AUTO_DISC_RIPPER_EJECT=1 \ to 0 but that had no effect.
I am new to linux and docker so I am unsure how to generate a log
Update
Jlesage is amazing :) It was fixed with their suggestion
sudo docker run -d --restart unless-stopped
--name=makemkv
-p 5800:5800
-v /docker/appdata/makemkv:/config:rw
-v $HOME:/storage:ro
-v $HOME/mnt/media/:/output:rw
-e AUTO_DISC_RIPPER=1
-e AUTO_DISC_RIPPER_PARALLEL_RIP=1
-e AUTO_DISC_RIPPER_MIN_TITLE_LENGTH=1200
-e AUTO_DISC_RIPPER_EJECT=1
--device /dev/sg0
--device /dev/sg1
--device /dev/sr0
--device /dev/sr1
jlesage/makemkv
The text was updated successfully, but these errors were encountered: