SABnzbd Forums

Spotted this problem a couple of times now. SABnzbd will add an NZB to its queue normally (set to 'unpack', no category), and when it's downloaded the files it will report the job as 'failed': "Repair failed, not enough repair blocks (18 short)" and subsequently won't unpack (as well as renaming the dir to "_failed_...").
The log however shows the files were repaired successfully, and a manual unpack after the fact works fine.

2010-11-26 14:49:06,161::INFO::[newsunpack:846] Verified in 4 seconds, repair is required
2010-11-26 14:49:08,269::INFO::[newsunpack:959] Repaired in 2 seconds
2010-11-26 14:49:08,269::INFO::[newsunpack:684] Par verify finished ok on .vol000+01.par2!

Version: 0.5.6
OS: WinXP SP3, patched to date
Install-type: Windows Installer
Firewall Software: WinXP SP2 Firewall
Are you using IPV6? no
Is the issue reproducible? yes

Does the NZB contain multiple sets of rar/par files?
If any set fails, the NZB fails.
Do you have any example NZB files?

I'll PM you a link to reproduce this, but I think I figured it out. I've set 'ignore samples' to 'do not download', but for some releases, the par2 files are named '.other.par2' (as they also cover the included srr file) and those will result in a failed repair. Setting 'ignore samples' to 'delete after download' seems to allow sabnzbd to continue with the unpack stage.

That's very likely the cause.
SABnzbd does like properly named sets.
The "don't download samples" option isn't great, because quite often posters disregard conventions.