Repair takes hours, also got extraction problems

[Marcoevich]

Hey All,

I've got some weird problems with SABNzbd recently.

Many dowloads just won't repair or extract. Alsways another error. Sometimes it's CRC error, sometimes to little repairblocks, sometimes it stucks at 'getting repair blocks'.

Also, repair/extract takes hours to complete. At this moment there are 6 completed downloads waiting to be extracted...

I don't have a clue about what's going on. I hope you guys can help me

[shypike]

par2 repairs can be extremely long, especially on hardware with slow CPUs.
Repairs are done by the par2 program, which we don't write.
What OS and hardware are you using?

[Marcoevich]

Hmm, my PC must be fast enough for the par2 repairs...

My current setup looks like this:
- AMD Phenom 2 X4 @ 3.2 Ghz
- AMD Radeon 5770 1GB
- MSI 870A-G54

I'm using Windows 7 x64

[Marcoevich]

I wish there was an option to stup the unrar process, and continue later on. Because all those downloads are stuck in the queue the unrar process goes on forever. And I cannot watch my movies while unrarring, because it will buffer continuously...

Help shypike

[shypike]

The problem isn't unrar, but par2 and there's nothing we can do about its performance.
The only thing you can do is schedule a no-postprocessing period in the Scheduler.
But that will also cause a queue of unprocessed jobs in the history queue.
One problem is that Windows is very bad at distributing disk-channel bandwidth over processes.
CPU prioritization is not a problem, but disk prioritization is.

[Marcoevich]

Pfff, I wish that the par2 crew wrote a dll or something like that so we can build our own par tools. Sadly this is not the case, and the development of par3 is in the hands of a few individuals who are not very active at this moment

Is there not a tool that handles the disk prioritatzion for windows? That would be very helpful.

I guess the only option for me now is to set a no-postprocessing period in the scheduler as you said. But doing that will make the queue even longer..

[sander]

Hmm, my PC must be fast enough for the par2 repairs...

My current setup looks like this:
- AMD Phenom 2 X4 @ 3.2 Ghz
- AMD Radeon 5770 1GB
- MSI 870A-G54

I'm using Windows 7 x64

I guess your RAM is as impressive as your other hardware?

If so, I would say your hardware is NOT causing any par2 slowness.

[Marcoevich]

I have 8 gb ram, so that's also not the cause of this.

Don't know what else it can be.

I also got incomplete downloads. Never had this so much with Newsleecher...

See:



If a download fails, I delete it and try to find another version with Couchpotato.
Sadly I get the same version very often, but note that in the picture above there are 3 different movies that cannot complete the repair/extraction process.
For Takers, Couchpotato found a different NZB, but with no success.

[sander]

I have 8 gb ram, so that's also not the cause of this.

Don't know what else it can be.

You're not using a network drive, are you? Just built-in harddisk?

If so, I don't know what can cause your slowness. Even incomplete posts should be handled quickly with your hardware.

[Marcoevich]

I do use a networkdrive, yes. But I assume that the repairjob is handled locally and not on the networkdrive? SABNzbd has a temporary download folder on my computer... If the downloads are completed, then they are moved to the network drive.

Now we're talking about it, isn't it possible to unrar on my local system and THEN push the files to my network share? I don't know if that gives any difference in performance, but maybe it's worth a try.

Excuse me if I confused you by not saying I had a network share.

[sander]

I do use a networkdrive, yes. But I assume that the repairjob is handled locally and not on the networkdrive? SABNzbd has a temporary download folder on my computer... If the downloads are completed, then they are moved to the network drive.

Now we're talking about it, isn't it possible to unrar on my local system and THEN push the files to my network share? I don't know if that gives any difference in performance, but maybe it's worth a try.

Excuse me if I confused you by not saying I had a network share.

Just to be sure, can you only use a local, built-in harddisk for temp, complete, incomplete, etc?

[Marcoevich]

Will try that, i have some gigabytes left

For the moment I only have my completed downloads folder on the network share, but I will try the nzb's in the picture above on my local system.

I'll keep you informed

[Marcoevich]

Hmm, it looks like the nzb's I was trying to download really where corrupt.. I've tried to download them to a local folder, but that didn't work.
I searched the interwebz for some new NZB's and they downloaded correct. Repair/extraction didn't take as long as usual.

This is pretty odd; In the case I use my networkdrive, I assume that my computer handles repairjobs locally. The files are only extracted to the network share...

Then what explains the difference in performance here? Or do I need to do some more testing?

[Marcoevich]

There's another thing that might explain why unrarring takes so long.

I just noticed that SABNzbd sends all the nzb/par2 files and sometimes even rar files to the network share

How is that possible lol? Now I understand why it takes so long... but why is sab doing this??

[shypike]

I just noticed that SABNzbd sends all the nzb/par2 files and sometimes even rar files to the network share

It does not, unless you tell it that it's "temporary download folder" is on the network drive.
Further, at the end of the post processing any left-over files will be moved to the final destination.
BTW: If you choose anything else than "+Delete" as post processing, the original RAR files will be moved
to the final destination, instead of being deleted.