SABnzbd Forums

I'm losing about 20% of downloads to CRC errors, and re-downloading produces the same error. Is there soemthing I can do to remedy this or at the least fix the downloads?

Thanks

-axel


Version: 0.5.0 beta 6
OS: Ubuntu Intrepid server
Install-type: linux repository
Skin: Plush
Are you using IPV6? No
Is the issue reproducible? Yes

Do you have a decent unrar program installed?

It should be this one:
http://www.rarlab.com/rar/rarlinux-3.9.1.tar.gz
All platforms:
http://www.rarlab.com/rar_add.htm

I have been using the default unrar package within ubuntu. I will give the real program a shot and report back.

We have only heard bad news about all off the FOSS unrars.
The rarlabs' version is non-FOSS but it is free to use and the only good one.

I think we should build in a check that warns people about this issue.
And no, we cannot redistribute rarlab's version, because the Ubuntu package rules don't allow it.

Upgraded to 3.9.1 and am still getting the same error with all 3 of the tested downloads. Is there a log file for me to post or is there another solution to try?

Thanks again

Do you have "Post-Process Only Verified Jobs" checked in Config -> Switches?

There are three known ways you can get CRC errors with SABnzbd:

1) You have "Post-Process Only Verified Jobs" turned off, and your host is missing more parts than we can repair. The rar set ends up incomplete. Solution: Turn on "Post-Process Only Verified Jobs" and get a better news host. (Astraweb is a likely source of these errors right now)

2) You are on Linux and are using your distro's equivalent of unrar-free instead of unrar. The "free" version of unrar is notorious for screwing up even the simplest actions. Solution: uninstall unrar-free install unrar, either from your distro's repository or directly from RARLAB.

3) The post itself is screwed up as posted to usenet, and either there aren't enough pars to repair or the pars were also generated using a broken rar set. Solution: download something else.

Sounds like you may be falling into the first category if you're using unrar-nonfree now. If you'd like me to verify that it's screwed up only on your news host, please PM me details of the post.

Hi I am getting about the same number, and type of errors. I am using OSX 10.5.8, SabBeta 6, with Astraweb. The errors are consistent, attempting to re-download the file still ends in failure. But files which should be similar - same encoder / settings etc... are inconsistent, as in some will work while others fail. If I then try to use another program (MacParDeluxe) http://www.xs4all.nl/%7Egp/Site/MacPAR_deLuxe.html to unrar the failed files they still fail.

I will PM you an NZB which fails for me.

Thanks.

dukevim wrote: Hi I am getting about the same number, and type of errors. I am using OSX 10.5.8, SabBeta 6, with Astraweb. The errors are consistent, attempting to re-download the file still ends in failure. But files which should be similar - same encoder / settings etc... are inconsistent, as in some will work while others fail. If I then try to use another program (MacParDeluxe) http://www.xs4all.nl/%7Egp/Site/MacPAR_deLuxe.html to unrar the failed files they still fail.

I will PM you an NZB which fails for me.

You fall into category #1. That NZB is fine on Giganews. Verified in SABnzbd and Grabit for safe measure. Works fine from Giganews, 125 blocks short on Astraweb.

Yeah, I fall into category 1 using Astraweb...tough to beat $11/mo but it looks like I'm getting what I pay for. Odd that I never had these problems before this month, did something happen to cause these issues or have they always been this unreliable and I've simply been lucky?

My last 5 downloads from Easynews had these errors (never had problems in the past):
"Unpacking failed, an expected file was not unpacked"

Is this related to the CRC error? I just turned off "Post-Process Only Verified Jobs", hopefully that will help.

tstack77 wrote: Yeah, I fall into category 1 using Astraweb...tough to beat $11/mo but it looks like I'm getting what I pay for. Odd that I never had these problems before this month, did something happen to cause these issues or have they always been this unreliable and I've simply been lucky?

It's a recent change. It only started in the past couple months.

richlin71 wrote: My last 5 downloads from Easynews had these errors (never had problems in the past):
"Unpacking failed, an expected file was not unpacked"

Is this related to the CRC error? I just turned off "Post-Process Only Verified Jobs", hopefully that will help.

Don't turn off "Post Process Only Verified Jobs". If you turn it off we'll go ahead and try to unrar stuff we know is broken. That's not going to help you at all.

Need not be related to CRC errors.
It may be caused  by a sloppy uploader working on Windows.
There is a "hidden" option in the sabnzbd.ini file, allowing you to stop this checking.
unpack_check = 1

Astraweb's completion looks all fixed up today.

Posts so screwed up at the time of posting that they can't be repaired are pretty rare.

inpheaux wrote: You fall into category #1. That NZB is fine on Giganews. Verified in SABnzbd and Grabit for safe measure. Works fine from Giganews, 125 blocks short on Astraweb.

Thanks very much for checking, I guess Astraweb are having some problems at the moment - thanks for the brilliant work, I run Sab 24 hours a day, and it is my most used, and most useful application.

shypike wrote: Need not be related to CRC errors.
It may be caused  by a sloppy uploader working on Windows.
There is a "hidden" option in the sabnzbd.ini file, allowing you to stop this checking.
unpack_check = 1

I'm not sure what you mean by this...are you saying that these files can be unpacked if checking is stopped?