Support Forum

Safihre, I noticed two situations. One: 100% disk usage cause by sabnzbd and prolly by sickbeard moving the finished file. This time the queue was still filling up and there seemed to be a lot of IO backlog present. In order to regain control over the disk killing the unrar process isn't enough. It ...

I added a big queue, didn't cancel any items on the queue but resulted in many (8 to 9) "Unable to stop the unrar process." on average hourly. Seems like if you let it run eventually unrar issue will resolve. At least in this download of 50x (300GiG) queue. https://imgur.com/a/SXcPvAb Befo...

I noticed it this week multiple times. Not using the new method. I started sabnzbd again but without the 100% disk load. There was a big queue of downloads and it was performing as expected. After removing the big queue (select 'all' button and then delete) I noticed the "Unable to stop the unr...

I've got the same issue. I am able to kill the process by docker rm -f [dockername] or by killoff the process of the docker. Killing off the unrar process will just restart the unrar process to create 100% disk usage. After starting the sabzbd docker unrar creates 100% disk usage again. There were s...