SABnzbd Forums

Hi all

Hope someone can shed some light on this one. I have been using SABNZBD for a while now without issues. Have Sickbeard pushing NZBs over and have the post processing putting the TV files in the right locale. This has been faultless till a couple of nights ago. A download for a show completed processed fine and all was good. When last night files ran they all failed due to CRC errors. It appears the the job is running against crc check is running against the wrong show and this happening for all files. If I download without the post processing on its fine.

Heres an example of the error.
Unpack [showa.720p] Unpacked 1 files/folders in 2 seconds
[125775] ERROR: CRC failed in "showb.mkv"
Repair [showa] Verified in 2 seconds, all files correct
Any help would be great.

Thanks in advance.

What happens if you use WinRar to unpack from the failed folder in the "incomplete" folder?

I cant do anything after it fails as it removes the files. It seems its constantly looking for showb to unpack. If I dont use post processing it downloads and unpacks fine.

angelus073 wrote:I cant do anything after it fails as it removes the files.

If the job shows up as Failed in History, then the RAR files are still in the "incomplete" folder.
Have you tries "Retry" from the History entry?

I am experiencing the exact same behaviour. It suddenly started happening about a week ago. Each and every file that is marked for post-processing by Sickbeard leads to an error saying "Unpacking failed. CRC error" However, when I look at Sickbeard, it says file processed and I can see the unpacked file has been correctly renamed and copied over to the final destination folder. I am running v0.7.11 of Sabnzbd and not sure what version of Sickbeard. I did update Sickbeard today to latest version to see if that helps.

My theory was that sickbeard was processing the file too quick, leading to Sab failing the CRC check as the unpacked file was no longer there.

Where do you see this error, in SABnzbd or SickBeard?

I am seeing the error in Sabnzbd. Sickbeard shows no errors and shows file as being correctly processed. The error in the logs is : ERROR: CRC failed in "122733"

Upgrading sickbeard to latest version did not fix the issue.

Do you see a failed entry in SABnzbd's History?
If so what does it say exactly ?

The exact entry in the History section of SABnzbd is ">> Unpacking failed. CRC error"

The files dont stay in the incomplete folder. They seem to get moved or deleted. Still happening to me after reinstalling both SAB and Sick Beard,

I cant understand why it keeps checking against show b when its actually unpacking a totally different show.

That behaviour is different for me. The files are still in the incomplete folder. Only the actual file that sick processes is moved into my other location after post-processing. All other files, like .srr; .sfv, are still in the incomplete folder.

It's always very confusing if people who claim to have to same issue report completely different results.
So far my conclusion is that you do not have the same issue.
To both of you:
Isolate the problem from SickBeard. Let SB send NZBs but not let it post-process.
Also, do not use SABnzbd's Sorting and SB's post-processing at the same time.
Otherwise it impossible to isolate the problem.
Capture (readable!) screenshots and the involved NZB and mail that to bugs@sabnzbd.org
(and add the URL of this post).

OK. Will do. SABnzbd sorting is already disabled. My guess is that disabling sb post-processing would lead to no issues, but that is only a guess. I'll make the change and then send email with the required data.

I've resolved my issue. Contrary to my expectation, after disabling SB post-process, I was still getting CRC errors. I had a closer look at my completed folder and noticed that there were a couple of rar files in there with missing bits. I deleted those rar files and all subsequent downloads were ok and not reporting CRC errors. I've re-enabled SB post-processing and everything is still fine.

That is a bit weird.
SABnzbd attempts to do recursive unpacking, but it should restrict its efforts to the (temp) job folder in "complete".
Must look into that some time.