Quick Check

[gedekran]

It seems sabnzbd is failing to unrar some nzb's that contain multiple files and corresponding par2. I've noticed that with quick check enabled, not all the files within the nzb was listed as being checked. I believe the issue is that with quick check, sabnzbd only downloads the smallest .par2 file. If one of those par2 files fail, then the corresponding rar files are not checked and thus ends up failed. Where as before without quick check, sabnzbd would download parts of other par2 files for a rar set. In which case if one of the par2 files failed, it wouldn't be affected as it would have other parts of par2 files to check against.

SABnzbd Version: 0.5.0Beta4 | smpl Version: 1.3

[shypike]

Have you checked with the QuickCheck option off?
When QuickCheck sees any problem with the file checksums
it still runs par2-verify. After that, it's business as usual.
It always only loaded the smallest par2 file, that hasn't changed.

I'm not claiming there can be no error in the QuickCheck implementation.
Can you email an example of a suspected NZB file (bugs at sabnzbd.org)?

[gedekran]

Out of 22 file sets in a nzb, only 17 showed up in the quick check list as ok. The others were missing, and I had to manually download more par2 files to repair each of those as each needed to be repaired. I am downloading another nzb in that set. That will be finished in a few hours without quick check. I'll report back how that one turned out. I'll then turn quick check back on for the next nzb set and see how that turns out and give details here. After this I'll email the nzb files.

So far I've not seen a file fail quick check and then be listed in that list as being repaired. It either passes and then shows up in the list as ok, or does not show.

[gedekran]

Very interesting... With quick check off, after the nzb finished downloading, it has stalled at "Repairing: 32%". Par2 uses all available cpu usage in the task manager and this hasn't changed in thirty minutes. Memory usage is 2,860K. The par2 parameter is -t0. Going to reinstall sabnzbd and see if that fixes this issue with par2.

[gedekran]

I tried shutting down sabnzbd and it wouldn't respond. So I went and tried to terminate the par2 process. Then sabnzbd started to process the files and verify them with par2. The par2 process popped back up and is using considerably less resources. Then after it went through with no other files needing to be repaired, sabnzbd shut down.

Opening up the failed folder. There were all the rar files and two par2 files. Both for the file that had stalled the par2 process in sabnzbd. One had no repair blocks included, and another with one. Upon clicking on the par2, quickpar quickly repaired it.

[gedekran]

I reinstalled Sabnzbd, and it didn't correct the issues. So my next nzb I'm going to remove the par2 parameters. See if that changes anything. After that, if it still doesn't work then I'm going to see about replacing the par2 program file.

[shypike]

To repeat my question:
- Can you email one of the suspected NZB files to bugs at sabnzbd.org ?

[gedekran]

Emailed.

[shypike]

Confirmed that there is a potential QuickCheck problem with NZBs containing multiple rar-sets.
I found out what it is. Will be solved in next Beta.

[gedekran]

Thanks for all the great work!

[tehgooch]

Hi,

Sorry to thread dig, but I am getting this exact same problem with 0.5.0Beta6 and par2 parameter -t+. I have sent a NZB file to the email listed earlier in the thread with subject "PAR2 Failures Topic 3197.0".

[shypike]

Sorry to thread dig, but I am getting this exact same problem with 0.5.0Beta6 and par2 parameter -t+. I have sent a NZB file to the email listed earlier in the thread with subject "PAR2 Failures Topic 3197.0".

Don't know where you sent it too, but I cannot find anything related in the mailboxes.

[tehgooch]

Sent to bugs at sabnzbd.org.

[shypike]

Sent to bugs at sabnzbd.org.

Found it in the spam folder (way to go gmail!).
I can find nothing wrong with it.
It doesn't pass QuickCheck, because there's a slight error in the NZB file.
Therefore SABnzbd runs the par2 utility, which repairs successfully.
I downloaded it again and this time removed a complete rar segment from the NZB.
Again it was repaired successfully.

A couple of check questions.
- What's your operating system?
- Do you have a multi-core system (since you want to use -t+)?
- If not OSX or Windows, which par2 did you install?
- Are you using astraweb (or related servers), they recently went through a bad period

[tehgooch]

A couple of check questions.
- What's your operating system?

Windows 7 Ultimate x64

- Do you have a multi-core system (since you want to use -t+)?

Yes, Q6600 w/ 4GB DDR2-1066 RAM

- Are you using astraweb (or related servers), they recently went through a bad period

Nope, I'm on usenetserver. It only happened for 3 NZBs so far and now that I think about it they were partly downloaded with the last beta - perhaps that could have something to do with it?