SABnzbd Forums

Posted: **December 29th, 2025, 10:21 pm**

A download and unpacking completed with the message on the History tab - "Unpacking failed, see logfile" , but I don't see any errors in the log.

There is a huge single line in the log file that I searched for the words "error" and "failed" without getting results on that line.

Note that the initial download failed , and I retried it without making any changes. Then it failed again, but it failed at the time I expected it to complete and had the size and number of files that I expected.

Is it possible the first failed somehow caused the second attempt to also report status as failed?

sabnzbd.log file excerpt below:

Code: Select all

The log includes a copy of your sabnzbd.ini with
all usernames, passwords and API-keys removed.
--------------------------------
(unpacked files line removed.  My VS Code editor said the line was 1.6 MB of data , so I didn't paste that!)
2025-12-29 16:08:46,471::INFO::[filesystem:319] Checking if any resulting filenames need to be sanitized
2025-12-29 16:08:46,580::INFO::[postproc:460] Finished unpack_magic on Sony PlayStation 1 NTSC-U Redump 2-13-2013 [AcePuppy]-xpost
2025-12-29 16:08:46,698::INFO::[nzbstuff:1831] [N/A] Purging data for job Sony PlayStation 1 NTSC-U Redump 2-13-2013 [AcePuppy]-xpost (delete_all_data=False)
2025-12-29 16:08:46,699::INFO::[notifier:166] Sending notification: Download Failed - Sony PlayStation 1 NTSC-U Redump 2-13-2013 [AcePuppy]-xpost (type=failed, job_cat=prowlarr)
2025-12-29 16:08:46,814::INFO::[database:310] Added job Sony PlayStation 1 NTSC-U Redump 2-13-2013 [AcePuppy]-xpost to history
2025-12-29 16:08:46,815::INFO::[database:287] Removing completed jobs older than 30 days from history
2025-12-29 16:08:46,817::INFO::[postproc:136] Saving postproc queue
2025-12-29 16:08:46,818::INFO::[downloader:412] Post-processing finished, resuming download
2025-12-29 16:08:50,819::INFO::[nzbqueue:230] Saving queue
2025-12-29 16:08:50,821::INFO::[postproc:136] Saving postproc queue
2025-12-29 16:08:50,821::INFO::[notifier:166] Sending notification: SABnzbd - Queue finished (type=queue_done, job_cat=None)

Posted: **December 30th, 2025, 2:53 am**

And if you search sabnzbd.log* for "Unpacking failed, see logfile" or just "Unpacking failed"?

Because I think it's from https://github.com/sabnzbd/sabnzbd/blob ... 1004-L1007 ... so the default message for a 7z unzip that goes wrong (in a unexpected way). If so, the next line in your SAbnzbd.log at least shows the return code. Not that will help you much.

To verify: this is a 450+ GB download? If so: enough disk space etc?

EDIT:

You could run a manual 7z unzip on the files in incomplete

Posted: **December 30th, 2025, 11:55 am**

You're a genius! I didn't think to look at the incomplete folder. There are 2 7z files in there. I got errors trying to extract them on my Desktop computer. I was able to source those files someplace else while typing this reply, so I'm good there.

It's odd because this is a my second download of these files, and the first time it completed without issue. But I ran a command line utility one them that was supposed to change the data into a better format...and if it has worked as advertised I wouldn't be here downloading them again

On a better note, I'm learning a bit from this failure as I never examined the nzb file before to learn what the contents should be. I just did that and there should be 1695 .7z files.

Something else that is a first, I looked in the __ADMIN__ folder and discovered 34 zero byte "SABnzbd_nzf*" files in there, which may be the source of the problem.

Anyway, I think you answered my question, so I'll mark this thread as solved if this forum has that feature. Now I need to go count some files to see if anything else is missing.

Thank you for your help!

SABnzbd Forums

Unpacking failed, see logfile" , but I don't see any errors in the log.

Unpacking failed, see logfile" , but I don't see any errors in the log.

Re: Unpacking failed, see logfile" , but I don't see any errors in the log.

Re: Unpacking failed, see logfile" , but I don't see any errors in the log.