SABnzbd Forums

I have one job that's stuck at 99% repairing for the longest time. This affects the other jobs because they are in "waiting" state. What gives?

Depending on your hardware repair can take a very long time.
If you suspect it's crashed somehow then do this:
Use the operating system's tools to stop a task called "par2" (or starting with "par2").
SABnzbd will flag the job as failed.
Then either retry or delete the job.

Oh this is definitely not because of hardware. It's been like this for around 2 days already. Ok, I'll try that.

So I stopped the par2 process and for some reason it did fix the job in question (it did not mark it as failed). Any reason why it did that?

We have no control over what par2 does and little knowledge about its internals