Par2 checking on some files is incorrect ->Set doesn't un

[TheFireman]

It seems that for some reason some files do not get par2-checked correctly after they are downloaded. They are recognized as good, while there are not, or are recognized as not good while they are good. This is not very often but has happened here 3-4 times.
Don't have any ideas why this might happen.

Anyway, this alone isn't such an issue, but in the case where a file is at first par2-recognized as not good, while it is good, after additional par2 files are downloaded, par2 checking is good (no repair needed, as the file was good anyway), however that rarset remains rared and does not unrar as expected.

I'm not sure if there is any problem in the opposite scenario.

Using build of 12.02.2007 at the time being.

[Rdl]

Can you provide log? Also if that is the case this can be reproduced every time with the same par2 set / files, so nzb file is also needed

[d4f0rc3]

sorry I have no log but it happened to me too with 1 dvd and 2 tv shows. 1 part was missing and altbinz didn't dl the missing part and repair/extract as usual I had to do that manually. next time I'll provide a log.

[Mystic2010]

This happened to me too once, was for the file departed-ftc (remove this whenever you read this) and I thought it was just a slip up. That maybe, before ending par check I decided to shut down the program. But that is hardly imaginable. So I got the same symptoms as topicstarter. If I recall it was in the 1202 build. Haven't seen it since..

[TheFireman]

Sorry, no log available here as well. However I can add the following.

In one case when I saw a rarset had 1 bad block in one file (while other files of the same set were downloaded), I manually checked the rarset with quickpar. It checked out OK (no errors on the file that was suposed to have a bad block). After that I exited Alt.Binz and reopened it. After Alt.Binz rechecked the rarset, the file that was suposed to have a bad block was found to be OK this time.

So I don't think the problem has to do with the nzbs, or the files, but with the way the files are par2-checked. It seems that under some conditions (not known yet) the result of the par2 check of some files is not correct and good files are marked as bad and bad files as good.

There also seems to be a second bug here, that should be easier to find. I saw the log for this example, but haven't kept it. What I read was the following, as I remeber it:

1. One file is found to have a bad block after it is downloaded (which was a false reading as it turned out, which is the first bug).
2. After all the files are downloaded, the needed par2 blocks are downloaded.
3. Then a repair of the rarset is initiated, however no bad files are found ("no repair needed" reported in log)
4. After that, there is no attempt to unrar the release (This is the second bug. Maybe Alt.Binz expects another exit code from par2cmdline, after the repair, e.g. repair successful, or something like that and that's why it does not start the unrar process).

[TheFireman]

Since I just posted what happens when a good file is recognized as having bad blocks here is what happens in the opposite case (when a bad file is recognized as good).

1. All files are downloaded and checked as good (although 1 of them has a bad block)
2. Since all files are recognized as good, no par2 files are downloaded.
3. Unrar process is initiated
4. Unrar returns an error (red X on unrar icon)
5. No further actions are initiated

What could be done in this case? If the first bug did not exist, no further actions would be needed. However in any case the following would help:

If unrar fails -> new par2 check on all files (1 time only, no endless loop) -> download needed blocks -> repair rarset -> unrar rarset.

[TH0R]

Since I just posted what happens when a good file is recognized as having bad blocks here is what happens in the opposite case (when a bad file is recognized as good).

1. All files are downloaded and checked as good (although 1 of them has a bad block)
2. Since all files are recognized as good, no par2 files are downloaded.
3. Unrar process is initiated
4. Unrar returns an error (red X on unrar icon)
5. No further actions are initiated

What could be done in this case? If the first bug did not exist, no further actions would be needed. However in any case the following would help:

If unrar fails -> new par2 check on all files (1 time only, no endless loop) -> download needed blocks -> repair rarset -> unrar rarset.

I have had the same problem several times already.
For example: post FTD#322783 Verweg_s4_d5 has the problem.
The first 2 rars are missing 1 block each, but alt.binz thinks they are ok.
Alt.binz did make .parx files of the corrupt rars, though
When I use quickpar it uses the .parx files to quickly repair.

I have no logs, but if you want I can redownload the post with maximum logging or something.