Page 1 of 1

Failed, 1000+ blocks missing

Posted: March 31st, 2011, 9:41 am
by totallymike
Almost every package I download says this.  I can go in and manually repair the packages with the available par2s without trouble, yet SABnzbd+ cannot.  The Retry button verifies and reports the same error.

Attached is a screenshot showing the problem.

I'm using Arch Linux, and SABnzbd+ 0.6.0 Beta 4.

Any suggestions?
Mike

EDIT: Mentioned the attachment.

Re: Failed, 1000+ blocks missing

Posted: March 31st, 2011, 9:51 am
by totallymike
I'm attaching another screenshot.

This one shows par2repair repairing the same package SABnzbd+ refused to repair from the above screenshot.

Re: Failed, 1000+ blocks missing

Posted: March 31st, 2011, 11:54 am
by shypike
Most likely cause is inconsistently named par2 files.
Currently SABnzbd uses fairly strict rules about naming, primarily to support multi-set NZB.
We are looking at how to improve this.
If you think that there's no naming issue, then please send the NZB to bugs at sabnzbd.org

Re: Failed, 1000+ blocks missing

Posted: March 31st, 2011, 12:20 pm
by totallymike
I'm not sure there is a naming issue.  I'm sending an nzb to the address you listed.

Re: Failed, 1000+ blocks missing

Posted: March 31st, 2011, 12:47 pm
by shypike
There is a naming problem.
The par2 files expects files named *.PAR2 while actual files are called *.par2.
You're a victim of a sloppy poster working with Windows.
Since Linux has a case-sensitive file system, repair will fail.
This is one of the things we will tackle in a future release, but not for 0.6.0 any more.

Re: Failed, 1000+ blocks missing

Posted: March 31st, 2011, 1:26 pm
by totallymike
Very strange.  It seems pretty common.

The par2 tools themselves have no trouble with the files; can you point me to the problem in SABnzbd where I can squeeze in a quick patch?

Thanks.

Re: Failed, 1000+ blocks missing

Posted: April 2nd, 2011, 10:12 am
by shypike
Fixing it is not straightforward.
You'd have to know which files are expected given the par2 file.
Just renaming to lower case won't fix anything if the par2 file expects uppercase files.

The first priority for the successor of 0.6.0 will be a more flexible way of using par2.