Page 1 of 1

[0.7.5] Repair failed, not enough repair blocks

Posted: November 6th, 2012, 4:24 pm
by blade-runner
Since i'm running version 0.7.5 SABnzbd is giving me failed downloads (not all of them but enough to post here)
When i load the exact same NZB in version 0.7.4 all is fine and the download is good.

The settings/setup from both instances are exactly the same except that 0.7.5 is running on a NAS and 0.7.4 is running on my desktop.

Re: [0.7.5] Repair failed, not enough repair blocks

Posted: November 6th, 2012, 4:30 pm
by shypike
You would have to email some NZB examples that exhibit this problem.
With just this description there's nothing I can do.
Please email some NZB files to [email protected]
Also add the URL of this post, the difference in behaviour (what says the History popup?),
and which Usenet provider you're using.

Re: [0.7.5] Repair failed, not enough repair blocks

Posted: November 6th, 2012, 4:50 pm
by blade-runner
Mail send.

If more info is needed just let me know.

Re: [0.7.5] Repair failed, not enough repair blocks

Posted: November 6th, 2012, 5:08 pm
by shypike
I think you made a mistake in your diagnose.
The repair indeed fails with 0.7.5 and I know why.
However it ALSO fails with 0.7.4 and it must do so, because of the NZB.
What happened is that the poster renamed the files after generating the par2 files.
Not a single version of SABnzbd ever supported such posts.

Don't despair. This week a Beta of 0.7.6 will come out that will tackle this issue.
After installing the Beta you will be able to "Retry" these failed jobs (so keep them) and properly post-process them.

Why posters do this?
Rumours are that it is some dimwitted way of dodging DMCA notifications.

Re: [0.7.5] Repair failed, not enough repair blocks

Posted: November 6th, 2012, 5:12 pm
by blade-runner
Thanks for your quick help on tackling this.
Did you see this in the NZB itself?

Re: [0.7.5] Repair failed, not enough repair blocks

Posted: November 6th, 2012, 5:46 pm
by shypike
Just downloaded the stuff.
I recognize the pattern by now, running par2 manually will tell you what's going on.
If you're impatient you can use QuickPar to repair and WinRAR to unpack manually.