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

container hangs on a bad disk #89

Open
tardol opened this issue Sep 11, 2020 · 4 comments
Open

container hangs on a bad disk #89

tardol opened this issue Sep 11, 2020 · 4 comments

Comments

@tardol
Copy link

tardol commented Sep 11, 2020

Hi

When using Unraid I've experienced multiple scenarios where a scratched disk causes the container to hang, but mainly during a rip or unmount/eject. If the disk can't be read the application will keep trying to complete the action (the time to finish during a rip will keep climbing) and trying to stop the container in unraid fails. Once trying to stop the container the url is unresponsive, but unraid still shows as started. A soft shutdown of the server has to wait for docker containers to stop, which in this state makemkv never does so I have to hard down the server.

If the disk errors saying failed to open, the unmount/eject will never complete and trying to stop the container will leave it in a hung state. If the disk does start ripping but gets stuck on a scratch the time to complete will climb forever and trying to stop the container will leave it in a hung state.

Killing the container via command line has also failed.

This seems to be more prevalent with DVDs, but has happened on bluray and 4K disks as well.

I am on the latest build of the container.

I'm hesitant to try any more of my DVD collection as most result in a hard down of the server.

Thanks

@jlesage
Copy link
Owner

jlesage commented Oct 4, 2020

Are you seeing this behaviour with the UI or the automatic disc ripper (or both)?

I think that this kind of problems with bad discs are also seen on standard Linux systems. In other words, the issue seems related to MakeMKV itself, rather than with the container.

@tardol
Copy link
Author

tardol commented Oct 6, 2020

Thanks jlesage - I haven't used the automatic disc ripper to know if that's also affected, only manual rips.

Have you had experience with bad discs causing the container to be unresponsive (stuck in running state despite being down) after trying to stop whatever task it's currently failing to complete?

If it's at the linux level and not the container level it sounds like there's not much that could be done, but I'd welcome any tips to force the container to stop so that I don't have to hard down the server. The docker kill failed for me.

@Zork87
Copy link

Zork87 commented Sep 5, 2021

I've been experiencing an issue that may be related. Like the OP I also have experienced this when a disk can't be read can create conditions where MakeMKV hangs, and also specifically an issue with DVD's that won't mount causing the same behavior.

I wonder if the OP is also using a SATA drive in a USB enclosure (as I am)? As the OP noted the troubling issue here is that the problem with the container creates a situation where the host running Docker actually becomes unresponsive. I happen to be running it on unRAID like the OP. The container can't be shutdown or killed even form the CL...creates a situation that effectively crashes the docker host and the system has to come hard down.

I've been researching this for a while, and wondering if this might be bad behavior of blkid as describe in this post on the MakeMKV forum?:

https://forum.makemkv.com/forum/viewtopic.php?f=3&t=25357&p=109149&hilit=hang#p109149

@jlesage any thoughts? I'm a docker noob and don't know if this fix has to be implemented on the docker host or could work in the docker container...

@jeaboswell
Copy link

I'd like to bump this, as I had this issue today.

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