I've been using unRAID and SABnzbd for a while now and things had been working fine.  But last night, it seemed like SAB got stuck - the file being repaired stayed at 0% and did not progress even after a few hours.  I tried to restart and shutdown via the GUI but was unsuccessful.  So then I did a 'killall python' after telneting into the server.  The SAB GUI was not responding anymore (as expected).

 

I wanted to then reboot the server.  So I went to the unRAID GUI and attempted to Stop the Array (after which I would do a Restart).  But this is where I am currently stuck.  The cache drive is stuck on 'Unmounting' and the other drives are all green and as far as I can tell, they are unmounted because I don't see them when I look under /mnt.

 

Any ideas on what else I can try to unmount the cache drive?

 

Based on this post by Joe L, I figured out that 'par' was keeping my cache drive busy.  I killed the process and the array then stopped. 

FYI, you can just do a shutdown or reboot on the command line once you were in that state. The array had been shut-down properly by then. I have done it a number of times and it doesn't even cause a parity check. Best to try and get the drive unmounted if you can but you don't have to.

 

Peter

Cool, good to know! 

This has been happening every time I try to Stop the array through webUI lately.

 

I run the commands in the post by Joe L.  Sometimes it works, sometimes it doesn't completely stop it, so I end up having to powerdown through command line.

 

Any reason why this may be happening so often?