SABnzbd Forums

Hi,

I'm facing an issue with sab which does not
1. repair the files downloaded correctly, while Quickpar does it very well (so it seems that sabnzbd has downloaded enough .par2 to repair it), or
2. does not even download enough .par2 files while lot's of them are available in the .nzb (if repair is not possible so why sabnzbd does not try to download more .par2 ?)

I'm using right now the latest beta 0.7.6beta1 but I already faced this issue with previous version

I face these issue using the par2 multi-thread version. What is interesting is when I use the non-multithread version of par2 (par2-classic ?), sabnzbd does repair the file correctly (but veeeeeeryyyyyyyyyy slooooooooowwwwwwwww)

Here are some .nzb example that do the current issue (sorry, big file, more than 15gig to download)

http://kouze.plouc.eu/sab/test%201.nzb
http://kouze.plouc.eu/sab/test%202.nzb

Thanks
kouze

You can see for yourself whether SABnzbd has downloaded all available par2 files.
Also, if QuickPar and par2-classic can repair, then by definition enough par2 files have been downloaded.
This is not a case of badly named files either, so using 0.7.6B1 won't do better than 0.7.5.

Conclusion: a bug in par2-tbb.
Do you have a 64bit operating system?
If so, what happens if you try the 32bit version of par2 instead of the 64bit one?

I also read that par2-tbb can be buggy on some systems

I tried phpar2 which seems to work fine (http://paulhoule.com/phpar2/index.php)

I'll try the 32bit version of par2-tbb now

All true.
We're looking at phpar2, but it has two problems: Windows-only and rather incompatible (different options, different output).

I tried the 32bit version of par2-tbb which repairs my files correctly. I will continue with this version for a while to see if it solves my issue in the long term
Thanks shypike

OK, it only confirms that we should give support of phpar2 more priority.