SABnzbd Forums

Version: 0.5 Final
OS: Windows 2003
Install-type: Windows Installer(updated from 0.5 RC3)
Skin: Default
Firewall Software: None
Are you using IPV6? no
Is the issue reproducible? don't know, but doubt it

I downloaded a nzb from binsearch and after it downloaded, it hanged at starting repair(Starting Repair 1.44 GB Verifying...) for more than 12 hours now.

I started the repair manually and there was one corrupted file and there was 1 par2 block downloaded so it should have been able to repair it fine(it worked manually). When another download finished, it got queued and won't start.

If you have more question or want me to test something, it's stilled hanged.

Kill the par2 process, head to config -> switches, and disable "Prevent Duplicate Downloads".

Try to download it again. If it hangs AGAIN, kill the par2 process again, go back to config -> switches and disable "Enable MultiCore Par2".

Try to download it a third time (promise this is the end), and if it fails a third time I don't know what to do.

If it passes downloading the second time through (still with multi-core Par2), I still suggest turning off "Enable MultiCore Par2", just to be safe.

And please report back with results. Prior to 0.5 final we were very close to pulling MultiCore Par2 altogether, if you can find a reproducible case where it fails it would help us make a decision.

This time it didn't hang, but it failed verification when it shouldn't have. There was still 1 block corrupt and 1 available and it repair fine manually.

I didn't change any settings since "Prevent Duplicate Downloads" was already disabled.

The repair method does rely on a proper naming convention.
Sometimes there are uploaders who do as they please.
Please email the culprit.

Ah, that make sense. It wasn't a scene release and the name was the title with spaces, so that must be why.

Hmm, It just failed verification twice with properly named scene releases. 1 that needed repair and 1 that didn't. I also downloaded 3 others that worked fine.

I'll try to disable MultiCore Par2 and see what happens.

I'm using 0.5.0 (Final, upgraded w installer from 0.4.12) on Windows 2003 R2 x64 and I'm getting a hangup on par2 repairs only (quick verify is ok)
Skin (if applicable): Classic, Dark Blue
Firewall Software: Windows Firewall >.<
Are you using IPV6? No
Is the issue reproducible? (yes/no) umm it is CONSISTENT for me but I dunno if reproducible

I have it set to pause downloading while verify/repair is going on
I have multi-core enabled with -t0 option passed
Duplicate nzb check disabled

It finishes the download, finishes the verify (fails), then sits on status 'verifying' until I kill the par2-classic*32 process... I check the files in incomplete dir and the repair was successful
Then I restart SABnzbd and everything continues with no problem (download is marked as complete and the files have been moved to appropriate category)

If the verify doesn't fail then the download completes perfectly and it moves to the next item in the queue.

I just checked the SABnzbd installation folder and found a x64 dir under /par2/win so I renamed the par2-classic.exe and par2.exe and put the x64 version in their place... Not sure why it was using 32bit but now it has no choice.. hopefully this (blind) approach will fix it XD  I'll post back with results.

Tested with the x64 par2 exe and it works fine now.. My guess is some problem with the return value from par2 classic 32bit but I don't know how to check.
If you can tell me where I might find some logs I'll try to see what happened - I don't see any logs in the program directory or subdirs.

Very strange. We have never seen any problem with par2-classic.
It works fine on x64 too.
That the 64bit variants are not used at all on your system is due to the fact that
we only support 64bit Vista, Win7 and Server2008.
We ignore XP-64bit and Server2003-64 bit (treat them as 32bit).

BTW: you may get problems with some downloads requiring joining,
because par2-multicore has a bug in that area. When detected
we silently run par2-classic instead.

I haven't had any error since I disabled multi-core par2