Page 1 of 1

Par repair fails

Posted: January 25th, 2014, 7:03 pm
by ghdoostg
Hi,

I have Sabnzbd 0.7.6 installed on a linux box (Ubuntu 12.04 64bit) along with par2cmdline-0.4 multi-core version (64bit), and i'm having some trouble trying to repair files.

I do not believe this to be a problem related to sabnzbd but rather to some misconfiguration or another problem i can't figure out and was hoping someone could shed any light

When downloading files through sabnzbd if i'm lucky and no article is missing, checks ok and unrars ok. If some articles are missing, sometimes it is able to repair itself with the par2 files provided in the .nzb but some others (i can't be more specific since i haven't been able to identify any patterns here) it fails no matter how many times i click "retry"
After this i run the par2 commands manually just to be sure it's not related to sabnzbd with this result:

Code: Select all

Scanning extra files:

Repair is required.
51 file(s) exist but are damaged.
504 file(s) are ok.
You have 8236 out of 8323 data blocks available.
You have 765 recovery blocks available.
Repair is possible.
You have an excess of 678 recovery blocks.
87 recovery blocks will be used to repair.

Computing Reed Solomon matrix.
Constructing: done.
Solving: done.
Wrote 590093460 bytes to disk
Wrote 590093460 bytes to disk
Repairing:.....%

Repair failed
...and it doesn't give me any indication as to why it failed. If i look at the download folder after the failed repair i see those files with .1 added to the file name but the size corresponds to an unrepaired file.

If i run this same .nzb on a windows machine with a different newsreader but same provider, sometimes i can even download without any missing articles, but even when articles are missing i can always repair all fine using Quickpar.
Would appreciate any ideas on how to solve this. I have even considered removing this version of par2 with multithread support and installing directly from ubuntu repository..... no idea if that could help but i guess repairs would be slower since that does not have multithread support.
Another workaround i could live with is manual post-processing of every job with a different utility other than par2 but i can't seem to find one.
Thanks.

Re: Par repair fails

Posted: January 26th, 2014, 11:16 am
by shypike
Consider upgrading.
Later SABnzbd versions fix the problem of posts with weird non-standard naming of files.

Re: Par repair fails

Posted: January 27th, 2014, 5:48 am
by ghdoostg
Thanks for replying!

Ok, i'm going to look into upgrading but it doesn't seem to be sabnzbd related, at least not the part of repairing files. Unless the reason why par2 can't repair some files is because sabnzbd messed up in the download process.

Re: Par repair fails

Posted: January 27th, 2014, 7:42 am
by shypike
SABnzbd doesn't miss articles, this basic functionality has been amply tested.
I may reject some malformed articles if you set a specific option in Config->Switches (Fail on yenc crc Errors).
Also other client may have a different number of retries and timeouts.
QuickPar can repair oddly named posts, because you tell it which par2 files to use.
Previously SABnzbd used well-defined naming rules.
Recently people started violating these rules and later SABnzbd versions follow suit.

Re: Par repair fails

Posted: January 27th, 2014, 11:32 am
by ghdoostg
Looks like I have the "Fail on yenc crc Errors" option enabled, so i'll disable that and try to download some nzbs again. Maybe that's the reason for all the problems i'm having