SABnzbd Forums

Hello.
Seems current SABnzbd version have a bug which breaks unpacking (or maybe another download stage) and leaves in History messages like this:

Unpacking failed, unable to find CENSORED.r18
Unpacking failed, unable to find CENSORED2.r72

Also instead of leaving failed task's .r**+.par2 files as is, SABnzbd deletes them instead.

Debug logging seems on, I can provide log if it will help.

Disaer wrote: ↑August 6th, 2018, 2:20 pm Hello.
Seems current SABnzbd version have a bug which breaks unpacking (or maybe another download stage)

Which SAB version is that?

Did you try with another SAB version?

sander wrote: ↑August 7th, 2018, 12:00 am Which SAB version is that?

Did you try with another SAB version?

SAB 2.3.4
No, because this bug appears relatively rare.

Disaer wrote: ↑August 7th, 2018, 1:36 am

sander wrote: ↑August 7th, 2018, 12:00 am Which SAB version is that?

Did you try with another SAB version?

SAB 2.3.4
No, because this bug appears relatively rare.

Rare? If you repeat the same download, does it happen again?

In addition:
Could you enable +Debug logging in the Status and Interface settings window, then after it happens again send me the log and the NZB at [email protected]?

I am seeing a similar problem with an influx of partial posts getting processed by SABnzbd. I understand that if the original post isn't complete, then I will never have a complete download, it is just the combination of SABnzbd attempting the repair and failing, and then still attempting to unpack the files and also failing. Despite the two failures, SABnzbd is reporting that the download was complete. Email notification for successful download is also sent but the folder contains the partial download .

If the failure was detected then the download could be retried with an optional new NZB file. I would also imagine that less clean-up would be performed making the next steps to resolve the problem slightly easier. I know I have previously missed that the download had failed to complete because I regularly clear the successful downloads.

I am pretty sure you have Config > Switches > Post-process only verified jobs, turned off. It is on by default since it was introduced ages ago, so you must have switched it off manually.
You should turn that on. In that case it will indeed stop after repair.

Its not something that you remember clicking on but this was definitely the source of my problem. There is a good chance that fixes both of our problems.
Many thanks for your help.

The problem appears again:

Debug log + NZBs sent to [email protected].

The problem is this: Is this maybe an external or network drive that you are downloading too?

safihre wrote: ↑December 6th, 2019, 10:46 am Is this maybe an external or network drive that you are downloading too?

Definitely no. Drive D: is basic NTFS volume on SATA HDD, directly attached to chipset's port on the motherboard.
I'm using ESET antivirus and Windows 8.1, should I try to uninstall antivirus or upgrade to Windows 10?

It's probably good to exclude the d:\_download (USD)\.UseNet\incomplete folder from the virusscanner!