There have been a lot of questions lately about CRC errors, so rather than having 50 different threads about CRC errors, here's one great big thread.
A CRC error means some of your files didn't survive the long and arduous journey across the internet. Usenet has a rather sophisticated recovery system with Par2, but Par2 still needs a good amount of data to repair files, and even Par2 is fallible. I've only come across three ways to end up with CRC errors in SABnzbd 0.5:
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, but we'll still try to unrar it for you. 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 and install unrar, either from your distro's repository or directly from RARLAB
. SABnzbd conveniently warns you of this issue now.
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.
It's almost always #1, sometimes #2, and rarely #3.