I downloaded a fairly large archive yesterday (24 GB) which apparently had lots of corruption. I needed over 400 repair blocks accounting for 4% of the file. For some reason, alt.binz 0.31.6 failed to even download the additional PAR2 repair files even though there were enough to repair the damage (nearly 600 available). I downloaded the PAR2 repair files manually and initiated a repair. The repair went surprisingly fast considering the damage (and did in fact max out all 8 cores on my Core i7
). However, after the repair completed it stated "Repair Failed".
I checked the files with MultiPar and found that the repair had in fact completed successfully. Indeed, the alt.binz log states:
6/30/2010 12:05:09 PM] [PAR2&Unrar] "File" Par2 repair successful
[6/30/2010 12:05:28 PM] [Main] Download queue autosaved in 0ms
[6/30/2010 12:05:28 PM] [Main] RSS tree autosaved in 0ms
[6/30/2010 12:06:15 PM] [PAR2&Unrar] "File" unrar started
[6/30/2010 12:06:17 PM] [PAR2&Unrar] Source dir: l:\in process\file\
[6/30/2010 12:06:17 PM] [PAR2&Unrar] Unrar dir: L:\somewhere\
[6/30/2010 12:06:17 PM] [PAR2&Unrar] Archive name: file
[6/30/2010 12:06:17 PM] [PAR2&Unrar] Error[0]No Password!
[6/30/2010 12:06:17 PM] [PAR2&Unrar] "l:\in process\. . .part001.rar" unrar failed
As you can see, the repair was successful. The unrar failed because the archive was encrypted and alt.binz didn't know the password. In that case the error should have been "Unrar failed; encrypted archive", not "Repair failed".