SABnzbd Forums

Hey,

just moved from nzbget to sabnzbd.

This morning I was greeted by some weird thing: SABwas pauzed because my download disk (1TB SSD) was full.
Upon further investigation, I see that there are a lot of files in the history tab, being processed one by one.
Now, some files need repairs, which takes up a long time, halting progress for all other files.

There are also files in there with statuses that would make them eligible to be moved on to the HDD by sonarr, if only SAB would mark them as processed.
The statuses are "Direct unpack: completed" and files which have status " waiting" , but have obviously failed (for example, size 0 B, all articles missing).

These files need to be dealt with asap, so sonarr can either move them out of the SSD when completed, or find a better NZB when failed.
However, none of this happens, because SAB is busy repairing another file in the queue.

My queue is now already at 80 files. When a file is encountered that needs repairing, it can take a very long time.
I would hope that there is a way to prioritize the PP queue? files needing repairs vs files not needing repairs?

There is a limited mechanism for this, where it will first handle easy jobs before hard ones (needing repair).
However, to make sure the hard jobs still get done, we force 1 hard job for every 3 easy jobs.
We don't have the parallel mode that nzbget has, unfortunately.