Auto disc ripper does not seem to work - Unraid 7.2.2 SATA controller: JMicron Technology Corp. JMB58x

[RBDK95]

Hi,

I am using unraid and really want to automate disc ripping a bit, but I am a noob at this and setting something up manually like Automatic Ripping Machine is not currently an option for me. Maybe down the line as I learn more.

Having this container with an automatic ripping script is an awesome idea 🤩

It is very hit or miss for me though. Both my blu ray drives are patches through, seen and work with the container.

However I can rarely get the auto ripping script to work.

Is it because I use a PCIe to sata adapter? Maybe its just an unraid specific quirk?

Any help or clarification is appreciated.

Thank you for making this container by the way. 😄

[jlesage]

However I can rarely get the auto ripping script to work.

What is the problem exactly? Did you look at the container's log for any clues?

[RBDK95]

Thank you for your quick response.

The problem is I go insert 2 discs and either the rippers never starts, only starts on 1 drive (not always the same), starts on both drives (rare) but then when I go add 2 new discs after the rip is done it only starts on 1 or never again.

Log most often ends with the below with no autoripper being ready. I have 2 optical drives. This time as per below, 1 drive rips and the other doesn't.

Not sure this is helpful, but to me as a noob it seems it only starts for 1.

[supervisor ] starting service 'autodiscripper-0'...
[supervisor ] starting service 'autodiscripper-1'...
[supervisor ] all services started.
[supervisor ] service 'xrdb' exited (with status 0).
[autodiscripper-0] Ready.
Log.rtf

[RBDK95]

It is mighty kind of you to look into. I will recreate the issue tomorrow and upload the requested logs 🙏

[RBDK95]

docker inspect MakeMKV.rtf
docker logs MakeMKV.rtf

Here is a good example. In this case I restarted the container and then inserted 1 blu ray in drive 1 and 1 dvd in drive two. Both autoripped in parallel as wished for.

Once the dvd in drive 2 was done ripping (blu ray still going as its much larger), I replaced the ejected dvd with a new dvd. As you can see from the "docker logs MakeMKV" no Autodiscripper-0 began with the 2. dvd in drive 2, despite a 10min wait.

I hope this showcases my issue. At this point drive 2. will no longer autorip.

Thank you in advance for your time spend looking at this 🙏

[jlesage]

In container settings, can you add the variable CONTAINER_DEBUG, with value 1 ? This enables some debug log that would be helpful to better understand what's happening.

[RBDK95]

Certainly, I will enable and then do another test with the log files you requested, thank you 🙏

[RBDK95]

I did not run an additional test yet but noticed after adding that parameter that the container CPU use was pinned around 38% which is far higher than then it was ripping in parallel (around 10%). Just attaching the log for now in case its useful.
Debug log no additional test.rtf

[RBDK95]

docker logs MakeMKV with debug.txt

Here the issue is again with the debug variable. Hope this clarifies 🙌

[RBDK95]

docker logs MakeMKV with debug no autorip 0 stuck on autorip 1.txt

One more log where autodiscripper-0 seems to have permanently been terminated and autodiscripper-1 is stuck on scanning drives.

So from this log I managed to rip 1 dvd with autodiscripper-1 before it became stuck. 1 dvd with autodiscripper-0 was terminated as the disc was toast. When replacing it with another dvd in the drive autodiscripper-0 runs on it seems to never recover and check for new discs.

Thank you in advance.

[jlesage]

Do you see the issue if you rip one disc at time, one drive at time ?

Some users reported that with recent versions of MakeMKV, it can stuck on loading discs (example: https://forum.makemkv.com/forum/viewtopic.php?f=3&t=40948). Some also reported that going back to MakeMKV 1.17.7 helped.

Can you try the Docker image v24.07.1 (which has MakeMKV 1.17.7) to see if it's better ?

[RBDK95]

I believe so, but let me retry. I am traveling and will not be able to test for several weeks, but I appreciate your time looking into this and will retry when I am home again.