SABnzbd Forums

I have run into a couple dozen instances where par2 runs at 25% (on my Windows 7 64-bit quad-core machine) in a 'Verifying' status and never finishes.

I believe it has something to do with the way the files are named (163265-0.0.1, 163265-0.0.2, etc.) and there are multiple mkv's associated to the nzb. I can get some of the files (in my incomplete folder) to open in 7zip, but only the partial mkv file is unzipped (unrar'd). Since there are sometimes over a thousand files I cannot figure out the naming convention, nor how to rename the files. I have run into one instance where the nzb completed, but the result ended in just the thousands of files (again 163265-0.0.1, etc.) being in my completed folder.

I use am running a basic sabnzbd (0.7.16) setup. Other than configuring it with my Usenet provider and Sickbeard, I have not changed any settings that I can think of. I would say I am pretty much running a default setup.

Sabnzbd works perfectly for me other than the couple dozen or so times this occurs.

I have a couple of example nzb files I can provide for each of the two scenarios I am talking about. I will email them to bugs@sabnzbd.org just in case you would like to take a look at them (immediately after submitting this).

Any thoughts on what I can do/try to get around these issues?

Disable 64-bit tools in Config->Special.
On some 64bit systems the 64bit versions of unrar and par2 don't work properly.

I have unchecked allow_64bit_tools in Config->Special, re-started SABnzbd, and tried one of the nzbs again.

It doesn't seem to be helping (>30 minutes showing "Verifying: 01/01") but I'll let it run over night again to see if it will eventually finish.

I can tell that the 32-bit version of par2 is being used because I see *32 next to the par2.exe process in task manager.

Is there any troubleshooting I can do to help figure out what is going on or 'fix' these problematic nzb's?

Yes, there's another setting in Config->Special->par2_multicore to disable.
This will make sure that only the classic (slower) par2 version is used.
All in all it would make me suspicious of my hardware.

I just logged on to inform you that I just unchecked "par2_multicore" and am trying again.

I have downloaded 'lots' of 'things' from usenet. I have only had a problem with < .0001% of them (unless of course the content is no longer there to be had!).

I have one more thing to try. It's a setting in my BIOS that I had to make in order for Oracle VM VirtualBox to allow multicore support for my Ubuntu virtual machines. Since I no longer use VirtualBox (or Ubuntu) I can disable that setting.

Unchecking "par2_multicore" in Config->Special did the trick!

I will still try the BIOS setting that I mentioned above and try the nzb again. I want to be able to rule it out for you guys.

I am having this same problem on one particular NZB.

It gets to verifying 120/120 and just doesn't complete (after 6+ hours)

I have switched off

allow_64bit_tools ( on )

par2_multicore ( on )


I can see that par2-classic.exe is now running, instead of par2.exe. It's a 467-part RAR file.

Does it use CPU and disk?
Unfortunately there's nothing we can do to improve par2.

shypike wrote:Does it use CPU and disk?
Unfortunately there's nothing we can do to improve par2.

Yeah it did.

Quickpar worked though I had to manually source the recovery files.