Quick Check OK but corrupt RAR file

[cohns]

Hello,

i have been having this issue since forever. For me Quick Check never fails but sometimes SABnzbd still fails to unpack and says "corrupt RAR file". It does not do an automatic repair. But if i do it manually with par2repair the repair succeeds and i can unpack it just fine. I know there was a way to disable Quick Check in some earlier versions, but i cannot seem to find it in the current one. Is there any way to disable it or at least force par2 to run. If you need anything, just let me know. Thanks in advance stay healthy.

[safihre]

Can you share one of these failing NZB's with me at [email protected]?
We have never had Quickcheck fail, since it's using the same logic as par2.

[cohns]

It is not specific to any NZB. In the beginning i just redownloaded them and then it would unpack. But this is very inefficient when it comes to 100+ GB NZBs.
Quick Check always says everything is fine. SABnzbd tries to unpack but it fails and says "corrupt rar". Then i have to run par2 manually, which finds the corrupt rar and repairs it. Then i can unpack it via SAB.
Most of the time the RAR files are fine. But somtimes one is corrupt and quick check does not catch it, so SAB does not try to repair.

[safihre]

Can you make sure that you have Post process only verified jobs in Config Switches turned On?

[cohns]

"Post process only verified jobs" is turned on.
This is what SAB shows me, when it happens.

[safihre]

Oke, can you enable Debug logging in the Status window and then run this job again and send me the logging (click Show Logging in the Status window) at [email protected]

[cohns]

Something funny happened. I switched the language to englisch for the picture i posted (usually i use german). But since then i have tried to recreate the error without success. I even saw SAB verifying some downloads and repairing them with out my intervention. Could the language setting be at fault?
I will send you the logs next time it happens. But for now using english as the display language seems to have fixed my problem.

[safihre]

If that is the case, I would also would like to know!

[cohns]

Happened again. It does not seem to be the language setting. I will send you the log right away. Thanks a lot for your help.

[Blubor2]

I'm having exactly the same issue (Ubuntu 22.04, sabnzbd 4.0.0, unrar 6.11 beta1).
How can I disable Quick Check? I see it mentioned in old forum posts, but I cannot find a switch to do so in the GUI nor in the config file.

Thanks.

[safihre]

There is no way to disable it, because if quick check fails we know for sure par2 will also fail. Your source files are just corrupt.
Or you have a hardware problem, like memory or disk corruption.

[NeatMinion]

I've had the same issue and tracked it down to bad par2 switches under "post-processing". I'm unsure if the par2 command changed or how it handles its options have changed, or if something else triggered it. "-lc14 -t12" went from at the very least not breaking things to causing par2repair to simply exit saying, "Cannot specify limit files unless creating.".

[safihre]

It's because you used a switch that is meant for Windows Multipar and not Linux based par2cmdline.
Or the other way around.

https://sabnzbd.org/wiki/configuration/ ... multi-core

[NeatMinion]

Yup, I have to admit I'm more curious as to why it ever "worked" than I am as to why it's not working.