Repair failed

[ThaBlaze]

any and all nzbs fail, only direct unpack ones work.

getting error Repairing failed, Repair Failed.

Using version 3.6.0
Running in docker on truenas scale

[sander]

any and all nzbs fail, only direct unpack ones work.

Try the reference download: 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" 1GB .

What is the result, with and without Direct Unpack?

[ThaBlaze]

[/quote]
Try the reference download: 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" 1GB .

What is the result, with and without Direct Unpack?
[/quote]

the test downloads work fine, I believe theyre all direct unpack?

[sander]

the test downloads work fine

Good. Then you have proven yourself that not all downloads fail.

I believe theyre all direct unpack?

Uh? Direct Unpack is not something in the NZB. Direct Unpack is what you want/choose SAB to do: unpack during download, or unpack after download. See http://127.0.0.1:8080/sabnzbd/config/sw ... ect_unpack

So, again, if you think it has to do with Direct Unpack, do a download with, and the same download without Direct Unpack turned on in SAB.

[ThaBlaze]

the test downloads work fine

Good. Then you have proven yourself that not all downloads fail.

I believe theyre all direct unpack?

Uh? Direct Unpack is not something in the NZB. Direct Unpack is what you want/choose SAB to do: unpack during download, or unpack after download. See http://127.0.0.1:8080/sabnzbd/config/sw ... ect_unpack

So, again, if you think it has to do with Direct Unpack, do a download with, and the same download without Direct Unpack turned on in SAB.

apologies, I'm not quite sure of how the nzb downloads work, but files that dont need to be repaired after download fail, and files that dont need to be repaired don't fail. Im running smart tests on all 4 of my HDD's which will take 14 hours but i dont think that is the issue as I tried it on a separate nvme drive and had the same outcome.

[sander]

Did you read https://sabnzbd.org/wiki/faq#toc32

[ThaBlaze]

Did you read https://sabnzbd.org/wiki/faq#toc32

its definitely not an issue with the nzb file as I have had others test it with no issues, and i dont think its an issue with sabnzbd either as again, the files load and repair fine for other users using sabnzbd.

[sander]

I see these possible causes:

1) those other users have different newsservers, which do have the full post available
2) something wrong with your setup (disk, rights, truenas), but I find that unlikely because the reference test downloads OK for you.

So, ad 1, which newsservers do you use? And which newsserver do those other users use?

[ThaBlaze]

I see these possible causes:

1) those other users have different newsservers, which do have the full post available
2) something wrong with your setup (disk, rights, truenas), but I find that unlikely because the reference test downloads OK for you.

So, ad 1, which newsservers do you use? And which newsserver do those other users use?

2 of the news servers are the same as well, so I dont think its the usenet backbone issue, also have a block server. still running the smart tests so we will see what comes up with my disks, again its not likely the disks.

[ThaBlaze]

the decoder crashes whenever its trying to unpack files and afterwards it shows corrupt rar file

[sander]

Then post that logging from sabnzbd.log here

[ThaBlaze]

https://mega.nz/file/NeYgxKgY#1L8Dx0N3L ... 70XSf3p8Gk

here is a link to the log, I couldn't find a way to upload the file in the forums here. This exact nzb downloads/unpacks fine on my windows machine with no issues. Ive tried using truenas scale, openmediavault and now even ubuntu server on bare metal. Still the same issue. Ive tried different drives, used nvme ssd's.

[sander]

the decoder crashes whenever its trying to unpack files and afterwards it shows corrupt rar file

I had a glance at your sabnzbd.log, and did not see "crash" or "traceback". So can you post that crash line here?

I do see

Code: Select all

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!

par2 stuff:

Code: Select all

2022-07-19 02:59:24,887::INFO::[newsunpack:1321] Verified in 38 seconds, repair is required
2022-07-19 02:59:48,854::INFO::[newsunpack:1508] Repairing failed, Repair Failed.

Those are bad indicators, but no "crash", so please show us

EDIT: on your Windows, did you check your sabnzbd.log for message like above?

[ThaBlaze]

the decoder crashes whenever its trying to unpack files and afterwards it shows corrupt rar file

I had a glance at your sabnzbd.log, and did not see "crash" or "traceback". So can you post that crash line here?

I do see

Code: Select all

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!

par2 stuff:

Code: Select all

2022-07-19 02:59:24,887::INFO::[newsunpack:1321] Verified in 38 seconds, repair is required
2022-07-19 02:59:48,854::INFO::[newsunpack:1508] Repairing failed, Repair Failed.

Those are bad indicators, but no "crash", so please show us

EDIT: on your Windows, did you check your sabnzbd.log for message like above?

https://mega.nz/file/ZW4hwaTK#ICVslT_9Z ... uC9c__ItKM

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. right now its on ubuntu server. why would it work on windows but not the docker image for linux OS's.

[sander]

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.

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?