Is the primary server in a "Readnews" farm?
Try this:
[x] Fail on yEnc CRC Errors
Repair Failed, Unpacking Failed, and CRC errors
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Repair Failed, Unpacking Failed, and CRC errors
Multiple ,par files have been downloaded. I have fail on yenc crc errors turned on.
I downloaded quickpar today - managed to fix one file with it, but others throw memory fault errors. Ran memtest - memory is fine.
On thundernews.
I downloaded quickpar today - managed to fix one file with it, but others throw memory fault errors. Ran memtest - memory is fine.
On thundernews.
Re: Repair Failed, Unpacking Failed, and CRC errors
Crap I was wrong - didn't have fail on yenc crc error. Have it rechecked now. Will see if this fixes it.
Re: Repair Failed, Unpacking Failed, and CRC errors
So checked it and everything works now. I'm incredibly perplexed as to why this problem suddenly cropped up though - been running fine for 6 months.konowl wrote:Crap I was wrong - didn't have fail on yenc crc error. Have it rechecked now. Will see if this fixes it.
Re: Repair Failed, Unpacking Failed, and CRC errors
So everything has been running great since I fixed the yenc ccc check. Suddenly last night I'm getting failed on everything again. This time I'm getting "files can't validate against .sfv file".
Any ideas?
Any ideas?
Re: Repair Failed, Unpacking Failed, and CRC errors
This is a secondary message.
It means that SABnzbd wasn't able to verify using par2 files.
Either because there were none or that the repair failed.
SABnzbd then tries any available SFV file to do a verification.
If that fails too, you get the error message you listed.
The SFV check can be disabled (Config->Switches), but that won't solve the actual problem.
It means that SABnzbd wasn't able to verify using par2 files.
Either because there were none or that the repair failed.
SABnzbd then tries any available SFV file to do a verification.
If that fails too, you get the error message you listed.
The SFV check can be disabled (Config->Switches), but that won't solve the actual problem.
Re: Repair Failed, Unpacking Failed, and CRC errors
I have been bitten by this as well using SuperNews. Something is definitely going on. Looking for good solutions without having to bite the bullet and use a backup usenet server.
It should be worth mentioning that I really don't think this is a SAB issue. Newsleecher fails too. I contacted SuperNews and they reported no issues.
It should be worth mentioning that I really don't think this is a SAB issue. Newsleecher fails too. I contacted SuperNews and they reported no issues.
Re: Repair Failed, Unpacking Failed, and CRC errors
Same problem. Also see here: http://forums.sabnzbd.org/viewtopic.php ... 150#p74150
There are more and more takedowns at my usenetprovider so I will cancle my subsctiption by the end of the day.
Even oneclick hosters are more reliable these days as this nzb trash
There are more and more takedowns at my usenetprovider so I will cancle my subsctiption by the end of the day.
Even oneclick hosters are more reliable these days as this nzb trash
Re: Repair Failed, Unpacking Failed, and CRC errors
One click hosters based on Usenet will fare no better.sp4wny wrote:Even oneclick hosters are more reliable these days as this nzb trash