Repair failed

Get help with all aspects of SABnzbd
Forum rules
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.
Post Reply
ThaBlaze
Newbie
Newbie
Posts: 12
Joined: July 15th, 2022, 1:39 am

Re: Repair failed

Post by ThaBlaze »

sander wrote: ↑July 19th, 2022, 12:44 pm
ThaBlaze wrote: ↑July 19th, 2022, 10:22 am
here is the log from my pc where the same nzb file worked. I cant seem to replicate the crash issue but this is the same error i was getting when I had it running on truenas scale.
Which "crash"? Please tell what you consider a "crash". And "repair failed" and the other messages above are not a crash.
ThaBlaze wrote: ↑July 19th, 2022, 10:22 am right now its on ubuntu server. why would it work on windows but not the docker image for linux OS's.
I tried the same post on my Ubuntu (with eweka, not newshosting), and the download completes without a problem. So it's not a problem with Linux in general.

What can be the cause on your Linux system? As on Windows you use the same newsserver as on your Linux, that is unlikely the cause. So ... wild guesses:
* disk in your linux system
* the rar or par2 binaries
* ... ?

Do other downloads work on your Linux? Good test:

In SABnzbd's upper right corner, click on the wrench symbol ("Status and interface options"), then click on first tab Status, and there click on "Test download" 10GB ... what is the result?
Sorry, when I was getting the crash issue, what happened was whenever the file was unpacking, the docker container would crash and restart, and after the restart the file would show up on sabnzbd as corrupt rar files
however after switching to ubuntu server, im not getting that error anymore, I will upload the log if I do see it happen again.


* disk in your linux system
-very much not likely, I've done an extended smart test on all 4 drives, all passed, secure erased them as well, and ive tried different drives/ssd's as well.

* the rar or par2 binaries
-how would I repair those? Would it make sense for it to happen on both truenas scale and ubuntu server both? are the rar or par2 binaries in the OS or the sabnzbd docker/application.
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Repair failed

Post by sander »

the docker container would crash and restart,
Wow. Then you have bigger problems.
and after the restart the file would show up on sabnzbd as corrupt rar files
Yes, that seems logical to me. Is all this about that one download? If so, ignore, and do a fresh download.


Please reread my previous as there is a clear instruction which you missed/skipped.
Top
ThaBlaze
Newbie
Newbie
Posts: 12
Joined: July 15th, 2022, 1:39 am

Re: Repair failed

Post by ThaBlaze »

the 10gb test is successful without any issues.
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Repair failed

Post by sander »

ThaBlaze wrote: ↑July 19th, 2022, 3:47 pm the 10gb test is successful without any issues.
OK. Then do a new download of the one that didn't succeed on your Linux setup.
Top
ThaBlaze
Newbie
Newbie
Posts: 12
Joined: July 15th, 2022, 1:39 am

Re: Repair failed

Post by ThaBlaze »

sander wrote: ↑July 19th, 2022, 3:57 pm
ThaBlaze wrote: ↑July 19th, 2022, 3:47 pm the 10gb test is successful without any issues.
OK. Then do a new download of the one that didn't succeed on your Linux setup.
https://mega.nz/file/YWAHnQQI#rRK8mF2B5 ... 02p8YnFtJA

Repair Failed.
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Repair failed

Post by sander »

Code: Select all

$ cat sab_truenas_2.log | grep -i -e "quick-check" -e "crc error" -e "repair failed"
First download:

Code: Select all

2022-07-19 02:56:13,454::INFO::[decoder:263] CRC Error in rEEzhdBr8jdNwVX9ZjVe@tBn-bmd.5xo
2022-07-19 02:56:20,948::INFO::[decoder:263] CRC Error in BuhPDxF1qPmoiuKZ5REexL325kE@db-q0_iNj.TjZ
2022-07-19 02:56:22,662::INFO::[decoder:263] CRC Error in hJ_IGDjrvINiT81wz2iqevUX@fuKz_.KNQ
2022-07-19 02:56:25,030::INFO::[decoder:263] CRC Error in 1T9RUDNAvlBZX0YPvg5Fq46CLci@E4sQrj.nvP
2022-07-19 02:56:50,776::INFO::[decoder:263] CRC Error in Zw5pcibITe1Rnpp4mpb612@0YmjekZ.xL0
2022-07-19 02:56:51,182::INFO::[decoder:263] CRC Error in BcD0l1pgWJlvhlnpN6R24f_MG@i_bL2kPV.ytp
2022-07-19 02:57:35,991::INFO::[decoder:263] CRC Error in 9IJDu0ugd429ssj-t4ie-@ldqLRHiH.rxD
2022-07-19 02:58:05,132::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part091.rar failed!
2022-07-19 02:58:05,132::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part030.rar failed!
2022-07-19 02:58:05,132::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part093.rar failed!
2022-07-19 02:58:05,133::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part024.rar failed!
2022-07-19 02:58:05,133::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part012.rar failed!
2022-07-19 02:58:05,134::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part014.rar failed!
2022-07-19 02:58:05,134::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part031.rar failed!
2022-07-19 02:58:05,135::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part011.rar failed!
2022-07-19 02:58:05,135::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part023.rar failed!
2022-07-19 02:58:05,136::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part072.rar failed!
2022-07-19 02:58:46,690::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part091.rar failed!
2022-07-19 02:58:46,690::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part030.rar failed!
2022-07-19 02:58:46,691::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part093.rar failed!
2022-07-19 02:58:46,691::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part024.rar failed!
2022-07-19 02:58:46,691::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part012.rar failed!
2022-07-19 02:58:46,691::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part014.rar failed!
2022-07-19 02:58:46,691::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part031.rar failed!
2022-07-19 02:58:46,692::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part011.rar failed!
2022-07-19 02:58:46,692::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part023.rar failed!
2022-07-19 02:58:46,692::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part072.rar failed!
2022-07-19 02:59:48,854::INFO::[newsunpack:1508] Repairing failed, Repair Failed.
10GB download:

Code: Select all

2022-07-19 12:59:50,925::INFO::[newsunpack:1125] Quick-check for SomeTestfile-10GB is OK, skipping repair
No errors. Interesting.

Second download

Code: Select all

2022-07-19 14:36:57,515::INFO::[decoder:263] CRC Error in UNflPcLLD3W9mrx_fyezREi5fm59@txXaI3c1s.paM
2022-07-19 14:37:18,398::INFO::[decoder:263] CRC Error in xsxTqZKFad2LLiuqd8q7@8y9y5Bp0.JKG
2022-07-19 14:37:36,203::INFO::[decoder:263] CRC Error in Rz14Mstu1-la7D7U6ZwORNQ2S@2WKmE.pnQ
2022-07-19 14:37:40,774::INFO::[decoder:263] CRC Error in lIpAM_6qaGZ4WN26qmno58WxABY@n7MF76S1.Tia
2022-07-19 14:38:21,744::INFO::[decoder:263] CRC Error in W-GDbRd-JuK23PuI6lU7kw@dJAnzU.Iz6
2022-07-19 14:38:26,654::INFO::[decoder:263] CRC Error in SmWq8RrzLPvOZV1dryhr@VVLRoahJc.XXH
2022-07-19 14:38:45,451::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part114.rar failed!
2022-07-19 14:38:45,452::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part087.rar failed!
2022-07-19 14:38:45,452::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part048.rar failed!
2022-07-19 14:38:45,452::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part038.rar failed!
2022-07-19 14:38:45,453::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part095.rar failed!
2022-07-19 14:38:45,453::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part127.rar failed!
2022-07-19 14:38:45,454::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part071.rar failed!
2022-07-19 14:38:45,454::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part062.rar failed!
2022-07-19 14:38:45,455::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part007.rar failed!
2022-07-19 14:38:45,456::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part060.rar failed!
2022-07-19 14:39:27,279::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part114.rar failed!
2022-07-19 14:39:27,279::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part087.rar failed!
2022-07-19 14:39:27,279::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part048.rar failed!
2022-07-19 14:39:27,279::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part038.rar failed!
2022-07-19 14:39:27,279::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part095.rar failed!
2022-07-19 14:39:27,280::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part127.rar failed!
2022-07-19 14:39:27,280::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part071.rar failed!
2022-07-19 14:39:27,280::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part062.rar failed!
2022-07-19 14:39:27,280::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part007.rar failed!
2022-07-19 14:39:27,281::INFO::[newsunpack:2020] Quick-check of file <HASH>f0b8764.part060.rar failed!
CRC Errors, but in different articles. Weird. I would distrust your hardware (disk, RAM), but that does not explain why the 10GB download went OK.

How are your other downloads going?

I already told you I had no problems with your download on Ubuntu (but with eweka as newsserver)

To rule out hardware: do you have other hardware with Linux? Or / if not: start a Ubuntu subsystem on your Windows, install SABnzbd, and download the problematic post, and see what happens

Also: on your Linux hardware (with problematic hardware): run memtest86.
Top
ThaBlaze
Newbie
Newbie
Posts: 12
Joined: July 15th, 2022, 1:39 am

Re: Repair failed

Post by ThaBlaze »

so ran memtest, turns out my recent ram upgrade has a faulty dimm that was throwing out a lot of errors in the memtest hammer test. removed the new dimms and problem completely solved.

thanks for all the help!
Top
User avatar
sander
Release Testers
Release Testers
Posts: 9429
Joined: January 22nd, 2008, 2:22 pm

Re: Repair failed. "CRC Error"

Post by sander »

Cool.

TIL: "CRC error" in an article are a very bad sign (maybe SAB should send a WARNING instead of an INFO?), and sign of bad hardware (and I would say: bad RAM, as AFAIK an article is not saved to disk but stored in RAM.
@safihre: What do you think?

Furthermore: I'm surprised and disappointed that the 10GB test download went OK without CRC errors. Maybe because those files are just zero's? I'll change that so they contain random bytes, hopefully triggering CRC Errors on faulty hardware like yours.
Top
User avatar
safihre
Administrator
Administrator
Posts: 5678
Joined: April 30th, 2015, 7:35 am
Contact:
Contact safihre

Re: Repair failed

Post by safihre »

CRC error is not always bad hardware, more of often its just bad upload by the poster or some server being funky.
We then go and try to get the article from the other backup servers, which sometimes works.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Top
Post Reply

Return to “General Help”