SABnzbd Forums

I have an issue with the par2 repair on my linux server. i have par2 installed and when i try to download an nzb which has errored articles i always get the same error.
"Not enough repair blocks left (have: 0, need:322) " it will then go and download the par2 files and the then repeat the same message before it reports that it cannot unpack the file. i have tested this several times and always seem to get the same error, with different amount of blocks needed.
has anyone else had this issue?

I don't quite understand the question.
Why do you "download the par2 files"?
SABnzbd is supposed to do that by itself.
Which postprocessing option do you use?
" ", "R", "U" or "D" ?

Did you check which files need to be downloaded?
Are the extensions of the par2-files "PAR2" instead of "par2"?
Some dumb Windows user download such stuff, making life difficult for Linux users.

Sorry that bit didn't come out right,
"it will then go and download the par2", the "it" part was SABnzbd. it seems to be downloading the par2 file, just not doing anything with them.  i use the R+U+D processing. I have updated to v0.4.3 and am just re-testing now

Thanks for the help, but the upgrade seems to have fixed it. SABnzbd has just repaired the file, No idea what was going on, just happy its working, thanks again for the quick response shypike 

shypike wrote: Are the extensions of the par2-files "PAR2" instead of "par2"?
Some dumb Windows user download such stuff, making life difficult for Linux users.

I'm downloading many files with PAR2 extension uppercased and the stage PAR2 fails while postprocessing.

Could SABNZBD ignore the case of these files while processing them?

In alternative, could a user script be created that is run in the folder to rename those uppercased file extension?

One other thing: once I rename the .PAR2 files in .par2, I have to run par and unrar manually, it would be great if SABNZBD would allow the users to run postprocessing stages manually (for failed ones obviously).

There's no 100% fix for this problem.
Linux is case-senstive, Windows is not.
Windows users are particularly sloppy in their filenaming habits.

I will have a look at some solution, but it will never be fail safe.
Just renaming the PAR2 files to par2 may be sufficient in some cases.
However, when the payload (the rar files) has the wrong case,
then there is no way to solve it.

Don't want to get into a Linux-Windows discussion...

Since sabnzbd runs on both platforms, I think the best thing would be that it should "mask" the differences of the OSs it runs on.

For this specific problem, from what I read in some posts, the problem is just that the filenames are uppercased and SABNZBD doesn't find them...I think this could easily be solved, even not touching the files, but when looking for them...I know you will find the best way.

A user script could also be created that normalizes all the filenames before sabnzbd processes them...

One last thing: would it be difficult to add manual post-processing control for failed unrar/par stages? I mean, when we find the problem and fix it it would be great to tell SAB to process it again.

Thank you very much for this great piece of software...

SABnzbd already looks for and recognized independent of casing.
It's the par2 program itself that causes problems.
Renaming the par2 files to lowercase is relatively easy and necessary.
When the files to be checked have the wrong case, repair is not possible,
because SABnzbd will not much about with the content of the par2 files.

I'm looking at the auto renaming of PAR2 files, but no more then that.

Well, if the contents of the PAR2 files refer to files with uppercase then it should not give errors...

If the contents of the PAR2 files refer to files with lowercase and a dumb guy uploaded uppercased files, then renaming the files should solve the problem...

I don't think there's a third case...

What about unrar? Is the multivolume handling of unrar case-sensitive too?

Are you also thinking about letting us manage the "stages" manually for failed ones? I mean run repair, unpack and delete manually...

Thank you.

We don't look inside the par2 files, so we don't really know what they refer to.

Manual retries are on the long-term list, requires too much redesign for the short term.