Can't verify, repair - Can Unarchive

[Map+Lobster]

I've run into quite a few files that give me the: "Invalid par2 files, cannot verify or repair"
But if I manually find the rar files & open them with The Unarchiver (OS X), I get my files. Might these files have errors that The Unarchiver doesn't catch? Do I maybe have an Sabnzbd+ issue?
I am newb.
Using SABnzbd+.app 0.7.20 Lion

[ALbino]

There's another thread about this here:

https://forums.sabnzbd.org/viewtopic.php?f=2&t=14897

I don't know if it really contains any answers though. Hope this helps.

[Map+Lobster]

Thanks

[mcfaul]

I'm getting this a lot recently too.

I dont really understand how/why the poster is managing to create par files which dont seem to be valid.

either they all look to be "damaged (0 blocks)"

OR

the have all the repair blocks.. but dont actually seem to have any files which they apply to (i.e. there are no "missing" rar files... they just seem to be par files for par files sake)

i hope the uploaders figure this out soon.

[jcfp]

Recently, something or somebody has been repeatedly posting jobs with utterly useless par2 files, that consist almost entirely of binary zeros (0x00). For sabnzbd, these broken files mean that both the quick check and the subsequent full par2 verification stage never succeed, which (in the typical absence of sfv files) results in a failed job unless the program is configured to continue postprocessing anyway (i.e., Post-Process Only Verified Jobs in config->switches is NOT checked). In that case, your chance of success depends entirely on the integrity of the downloaded rar files.

[mcfaul]

It seems strange that they are posting these zero par files, against perfectly working Rars tho? Am I missing the point

[ALbino]

I got 3 of these yesterday. It's out of control. Hope they fix it soon.

[jcfp]

Got another one this morning, this kind of result is typical when analysing the par2 files:

Code: Select all

$ hexdump <name>.vol127+128.par2 
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
63cb8a0 0000 a400                              
63cb8a4

Note that in hexdump, an asteriks denotes all lines precisely matching the preceding line (excluding the offset, obviously). So in this case, the entire file (size 63cb8a4 or almost 100 MBytes in decimal) is identical to the first printed line with its 16 bytes of all zeros, except for the very end were there's a single 0xa4. And once again, after wasting some bandwidth and storage space with those useless par2s, the job extracted just fine.

It seems strange that they are posting these zero par files, against perfectly working Rars tho? Am I missing the point

Join the club...

[mcfaul]

could it just be some kind of an error on their part when creating the Pars ? you would think if they were doing it to be malicious/wasting people's time/.bandwidth, they wouldn't post fully working rars?

but then how do they not notice that their pars dont work?

[killer8]

I also have this problem. Got many releases which got downloaded automatically through sickbeard but fail with the error "Ongeldige par2 bestanden, verificatie en reparatie is niet mogelijk ". However when I extract the .rar files manually the files are just fine.

When I check the par2 files they are just corrupt, the file only has null values when opening through notepad++ for example. A solution is to switch off "post-process only verified jobs" but this also moves and processes nzbs which are really corrupt and mess up my collection with crap.

Hopefully a better fix for this will be available soon.

[ALbino]

The disappointing thing about all of this is that if you get them right away then the rars are intact and you can extract them, but eventually every one of these posts is going to be worthless because the pars won't be able to repair them. So all that archived future content is down the drain.