sabnzbd+ is stuck on repairing..

[frason]

Is there a way to have both the new beta and the old 0.4.xx installed at the same time to test?

[shypike]

Yes, but the issue seems to be in the par2 binaries.
Not in SABnzbd itself.

You can replace the par2.exe file in the win\par2 subfolder
of SABnzbd's program folder.

[frason]

I did some more tests now.

Uninstalled 0.4.12
Reinstalled beta 6

Replaced par2 with the one from 0.4.12, didn't work.
Put back the new par2 (from beta 6), replaced unrar with the one from 0.4.12 = success.

I've been downloading a few nzbs with this config now and it's all working fine.

[frason]

Replaced the 0.4.12 unrar.exe with the official unrar.exe (x64) from WinRAR 3.9.1 (x64) = not working, so back to the unrar.exe from 0.4.12.

[shypike]

Are you sure your system is OK and 64bit?
I can find no problems with unrar 3.9.1, either the 32bit or 64bit versions.
All rarlab's unrar releases are all compatible, so you can exchange them at will.

The situation with par2 is a bit more complicated.
Depending on the system, par2.exe sometimes gives problems.
Especially if you have an older version of tbbmalloc.dll somewhere on your system.
(This problem will be solved in the next release).
If all else fails,  just remove everything from win\par2, except par2-classic.exe.
That one should always work.

[frason]

Yeah, all is ok in x64, I'm using WinRAR 3.91 x64 and a lot of other x64 apps and all is fine, except here.

I dunno what is wrong really.. Anything else I can look for?

I will try your par2 thing there..

[frason]

Same thing when I restored to the original unrar.exe and removed all but par2-classic.exe

Restored to original par2-folder and old unrar.exe and it's working again.

[shypike]

What happens if you copy unrar.exe from your WinRar installation to SABnzbd's folder?
Or did you try this already?
You may want to file a complaint at rarlab's website too.

[frason]

Yes, I tried that as well, but same result.

I've tried with the unrar.exe shipped with WinRAR to unpack the same files that fails, and it works then from the command-line so I don't know what's wrong really.

[veli]

Im having this same problem.  Unfortunately I have a crappy raid card so extended runs of 100% CPU cause drives to drop   I will say great program though!! ill try par classic.  Ive test my memory it passed..

[shypike]

Using -t+ isn't a very good idea anyway.
This means that verification is done with multiple cores.
It actually degrades performance because verification is limited by
disk performance, not by CPU at all.
Having two or more cores fight for disk access is not a good idea.

The best setting is -t0 which will only do the repair phase multi-core.
That phase is much more CPU dependent.

[MajorD]

Hi,

I encountered this problem earlier today.

Version: 0.5.0Beta6
OS: Windows 7 64bit
Install-type: Windows Installer
Skin (if applicable): Default
Firewall Software: Windows Firewall
Are you using IPV6? no
Is the issue reproducible? Not purposefully no.

Same as everyone else, default install of Beta6, was running through my queue fine until a certain repair job and then it stuck at 16% repair.

I'll just try swapping out the par exe's. Thanks for the information.

[shypike]

People saying repair is "stuck" do need to be aware
that repairs can sometimes take hours.
Especially on slower systems with large repairs.
The average Intel Core 2 Duo should be able to complete most repairs within 30 minutes.

[quaffapint]

I did have the stuck issue until I swapped out the par2.exe with the x64 one from the par2 website (for my W7x64 box).  It could just be coincidence, but still a week or so later and I having seen any stuck repair jobs.

[MajorD]

People saying repair is "stuck" do need to be aware
that repairs can sometimes take hours.
Especially on slower systems with large repairs.
The average Intel Core 2 Duo should be able to complete most repairs within 30 minutes.

I do appreciate what your saying however...

Q6600
4GB RAM
OS is on a 64GB SSD and files are downloaded to a RAID0 array. The download finished at 11:30pm (GMT) the previous day and I checked it this morning when I woke up and it was stuck at 16%.