SABnzbd Forums

Unraid Box running 0.7.3.

Everything fails due to crc or unable to repair (not enough repair blocks), etc...

retry works occasionally

Quickpar is able to repair all files in almost every case.

Ive emailed the log and the nzb.

Please help!

The log and the NZB have no relationship.
In other words, the download of that NZB is not in the log file.
What you can try is to download all files, including the par2 files.
Use "Download" instead of "+Delete" for that.
Then use the par2 program on the UnRaid box to do the verification. I suspect that the par2 program doesn't work.
Please email the output of that verification to bugs@

... I dont know how to do that

perhaps im out of my depth here lol

Is there a way I can just reinstall the Par2?

If it's the par2 program, then reinstalling won't fix things.
The only way to test the reliability of par2 is to run it directly on the files.
It's either that or wait for 0.7.4 which will log the output of par2 to SABnzbd's log file.

So redid my unraid box... no change

sabnzbd/couchpotato/sickbeard is installed on the usb drive, data is all stored on the cache drive, it also unpacks and renames in cache drive before moving it off to the intended share... at least the ones that work

I'm having similar problems, all of a sudden 90% of downloads are failing with CRC errors, only thing which may have changed is the Sab version. This is a Cenos Linux VM running in VMWare ESX and I have it set to "yum update" regularly, which also updates SAB.

My news provider is newshosting and using the same account downloading is working fine on an old (6.x) copy I have on a Mac.

CRC errors are very unlikely to be be caused by SABnzbd itself.
Typically it means that either the poster screwed up or that the par2 app didn't do it's job.
The first cause is easy to eliminate by re-downloading on your Mac.
The second one isn't very likely; par2 has proven it reliability over the years.
There is one potential soft spot in SABnzbd itself and that is QuickCheck,
where SABnzbd does a fast verification using the first par2 file.
That one is easy to diagnose.
Turn off the QuickCheck option in Config->Switches.
SABnzbd will then still perform the QC, but will also run par2.
Moreover, it will file a warning when QC and par2 disagree.
Such a warning would indicate a problem in QC and I would be interested in your results.

So just an update. All of these issues I have been having were all caused by..... wait for it......



BAD RAM



Im back fulling up and running.

It often is for bizarre problems.
I'm always a bit reluctant to suggest it early on, because it sounds too much as a "blame the victim" answer...