SABnzbd Forums

Hi Folks,

I'm running this great piece of software in a very resource-limited hardware (a Synology NAS), and therefore, when par2 reports an issue on a downloaded file and sabnzbd instructs it to repair the archive set, it takes *several* hours to go thru the repair process, 'cos of the hardware limitations. My desktop PC is a quad-core machine, and if I run the very same repair from it, accessing the files via NFS in the very same NAS, the process takes only some dozens of minutes.

Therefore, hence the question: Is it possible, somehow, to instruct sabnzbd to unpack an archive only if a quick check (or even a par2 check) reports that it isn't corrupted and otherwise (repair needed) leave the fileset untouched for manual intervention?

I'm asking this because I have a repair task that is running for almost 16 hours now (it's at 85%, the fileset has about 8.3GB) and it has created a huge backlog queue (62GB) for post-processing that based in the previous occurrences of this scenario, will take *days* to be processed.

Best Regards,
Ed.

Currently there's  no such option.
Maybe we could do something for 0.6.0.
It would be something like "use only QuickCheck and never par2".
Distinguishing between par2-verify and par2-repair is not possible,
because SABnzbd always uses par2-repair.

Thanks very much for your prompt answer! And what about setting the default post-processing to "none" and creating a user-script (probably a lot of its content would come from the sabnzbd source code) that has this intelligence ? Do you think that would do the trick ? BTW, in exactly which part of the "completion life cycle" are these user-scrips executed?

Best Regards,
Ed.

Just downloading would work, but you would get all the par2 files all of the time.
If you skip post processing,  it defeats the purpose of using SABnzbd in the first place.

The user scripts run as the very last step of post processing.

I think you would be better of with a conditional post-processing option as described.
I'll have a look at such an option.
It would mean that any download requiring actual par2-handling would be flagged as failed.
Release 0.6.0 offers retries from the History view.

This will be in 0.6.0 as the special option "never_repair".
It will limit par2 handling to QuickCheck and par2-verify.
A successful job will be processed as usual.
When verification fails, all available par2 files will be downloaded and the job will be flagged as failed.

Hi, thanks very much that's very good news, indeed. When Par2-verify fails, it reports which files are corrupted, missing, etc. Will this report be available, somehow, after marking the job as failed, to avoid a second round of par2-verify ?

Best Regards,
Ed

It will be as if the repair failed.
All normal actions will be done, except for par2-repair.
It will never attempt a repair, so you have to do it yourself.