CRC Failed

[vinnie19]

Im using now Sabnzbd+ 0.3.0.
I first used newsleecher but now im gonna try sabnzbd

But its working great. Running it on my server and nzb input / downloads / incompletes are on my laptop
And i enter it from my laptop.

So its working great and i love it.

But when i go to history i see sometimes this:

ERROR: CRC Failed in .................

What does this mean?

Because when i use quickpar myself and fix the rars it works good and i can unpack it.

I selected +DELETE
So it will be repaired / unpacked and deleted.
Config:
Enable Unrar
Enable Unzip
Enable filejoin
Enable Par cleanup
Top Only
(are enabled or on yes)

But why i get this error?

[shypike]

Could you specify the exact Operating system version and possibly email your sabnzbd.log file (preferably zipped) to [email protected] ?

[vinnie19]

Im using Windows XP Pro SP2 NL

I mailed the log in a zip file i hope this can be solved. because i like sabnzbd very much

[shypike]

Your logfile is incomplete, it does not contain the post-processing part, where things went wrong.
Could you send all of the logfiles (like sabnzbd.log.1 .2 etc.).

Somehow the repair by PAR2 failed, the CRC error comes from unrar (which received an incorrect file).

One extra check: assuming the job was called "HELLO THERE.nzb", was a "HELLO THERE" directory created or also (or only) a "HELLO THERE.1".
If so you may have encountered a bug which will be solved in the coming 0.3.1 release.

[vinnie19]

it only creates a directory called HELLO THERE

Send you the whole log directory with all the logs i got

[nzb_leecher]

I have that too, about once every 25 dloads, no big problem. Its most of the times a (small) bad memory problem. If i repair or unpack it mysefl 99% its ok. Sometimes i have to reboot and then try it before it works. seen that problem reported in many forums before, alsoi with newsleecher grabit etc. 99% of the times it traced back to a bad mem problem.

[shypike]

Vinny,

Studying the logs gives no conclusions.
Ok, it's easy to blame memory. It looks like the PAR2 processing passed OK, otherwise you would have had an error message before.
The error message comes from Unrar. Maybe the PAR2 program makes mistakes? I don't know for sure. I've never seem it on my systems.

One last thing that may help me analyse a bit more is the actual NZB file of the failing job. Should have asked this before.
Please send it to the same email address.

Thanks for your patience.

[shypike]

I find see something in the logs:
Par verify failed on \\XXXXLaptop\sabdown\Incomplete\wwo2-dvd 1²2\wwo2-dvd 1+2.vol000+01.PAR2!

Is this the job that failed?

Looks like PAR2.EXE indeed concludes that the set is not correct, if that is justified I don't know.
SAB tries no further download of PAR2 files, assuming that there would not be enough available anyway.
Unfortunately, the current SABnzbd goes on unpacking the files anyway. This is something to be fixed in a later release.
The other thing is that there's an odd character in the directory name (the superscripted 2).
This should not be a problem, but I can only test this when you send me the NZB file.

[vinnie19]

That was one of the few where it went wrong
I sent you the nzb file.

But when i try to repair it myself it works good.

And its not so big deal because i always repaired it myself for 3 years when i was using newsleecher. But now i wanted something else and not running on my laptop because that takes more memory. So i tryed this running on my server and putting the files unpacked on my laptop. So i only have to burn the files and delete them.
But i think it works great because its webbased and i can enter it from my laptop.

But i hope you can find it where the problem is.
And my server has 512mb memory.
My laptop has 2GB memory.
connected with a 100mbit switch

[vinnie19]

Any development on this problem?

[shypike]

Not yet, I have my hands full with lots of other stuff too.
This slipped through. I'll stuff it in my nightly test queue.

[vinnie19]

I think the problem is away.
I downloaded the new release 0.3.1 Final and installed it over my older version (0.3.0) and now it is working great.
Dont get this error anymore.