N00b -- Sabnzbd says there's an unpacking error...

[bytehead]

Yet I can extract all the files without any errors. 7-Zip.

Maybe a PAR failed, I dunno. I don't even see a PAR to run an external check myself (although I know it downloaded one...)

I used to be active in this stuff, but got out right before .nzb started to be anything, so this .nzb is completely new to me.

Of course, the total file size was over 4.2GiB.

Win 7, 64-bit.

I'm just going to kill that download now, but I don't know if it's a bug or just something weird on my end. The file size is scary enough.

[shypike]

What is the exact message of SABnzbd regarding the "unpacking error".

[bytehead]

Crap, I've already blown that one out. From my not so good memory (next time, I'll take a damn screen shot!) "sabnzbd has encountered an unpacking error. Please download more files" and I have the option of retrying with the optional different .nzb. Which I would try to do, it appeared that I was download a .PAR file, and then I'd end up with the same error message.

It may be a problem with how the whole thing was packaged. After I posted, I went back to read the discussion on the .nzb from where I downloaded it (NZBMatrix), and was having similar problems, there seemed to be missing files, but due to the convoluted paths and path length, that was where he was having problems. His newshost was giganews (and mine is xsusenet, and I'm not complaining it works most of the time).

And that's how I'm going to look at this issue. It's not a newshost, sabnzbd or computer error, it's a bad packaging problem.

Thanks!

[shypike]

There are a number of possible scenario's.
1. SABnzbd says that some files were not unpacked.
The reason can be there there are incompatibilities with encoding of file names.
This usually happens on embedded platforms or when OSX users unpack Windows generated RAR files (or vv)
Another reason can be overlong names or just an ordinary full disk.
2. CRC errors during unpack/unrar
Sometime posters just post corrupt RAR files.
This should not happen on fully par2-verified files, unless you have unreliable memory or a bad version
of par2 and/or unrar.
3. Download cannot be repaired.
Two possible causes: the post is incomplete and there are not enough par2 file for repairing.
The poster used some weird naming convention that SABnzbd doesn't understand.

[bytehead]

#1 has to be the issue (although with 750GB free, a full disk is not one of the worries right now :-p), since I tested and extracted the archive with no issues, which rules out #2 and #3.

As I said, this is my first foray into the new .nzb world. I expect hiccups in learning what's new.

[shypike]

There is an extra option in Config->Switches which allows you to skip the post-unpack check.
Item "Check result of unpacking".

[bytehead]

Cool. Thanks.