Repair failed, not enough repair blocks but works fine in quickpar?

[LeetDonkey]

Version: (Ex: 0.5.0 Final)
OS: ClearOS
Install-type:  python source
Skin (if applicable):  Smpl-white
Firewall Software: : None
Are you using IPV6? no
Is the issue reproducible? yes

Hello

I've installed sabnzbd on a ClearOS installation by using this guide:
http://www.clearfoundation.com/componen ... w/id,6380/

It works pretty well so far, however when I've downloaded something first sabnzbd verifies it, then it starts repairing it, but somewhere along the way it claims that there are not enough repair blocks and places the files in my 'completed' folder.
Now the thing is, if I copy the entire directory to my windows PC and run quickpar from there it has plenty of repair blocks and will repair it just fine.
The .rar files are usually archives in the neighbourhood of 25-50gbs per rar set and i'm running it off a dualcore atom which means it takes around 12-18 hours to repair a full rarset that size.

My usenetprovider is giganews.

I was wondering if my CPU simply isn't fast enough to repair archives of that magnitude? Or if I need to do something else?

Thanks

[shypike]

The most likely cause is incorrectly named par2 files.
SABnzbd only uses correctly named par2 files, in order
to separate the different sets.
QuickPar hoovers up all available par2 files.

[LeetDonkey]

Thanks, I'll try to pay attention to it when the next rar set fails

[Nick123]

Had the same issue several times with windows SABnzb it may have been incorreclty named par2 files as Shypike but I didnt pay any attention to the file names, Will also keep a look out.