SABnzbd Forums

Hi Shypike,

One of the reasons I thought it wasn't downloading the par2's though is that after one finishes downloading and it fails, with the status of "failed" and no other reasons, when I look in the incomplete directory at the file folder and see all the rar's, the other (excluding the actual .par2) par2 files do not exist. What I am seeing is that there are never additional par2 files even if I visually monitor the incomplete directory as it downloads and is eventually reported as being a failed download.

Thanks for continuing to look into this.

On my side i can confirm that -none- (i tried about 30 nzb, created by binsearch) of my downloads finish properly. When the files are OK (they do not need repair) they end up with the error message "Unpacking failed, an expected file was not unpacked ". When it is the case i just need to unpack them with unrar and it works. Otherwise, i need to download the par 2 manually, repair and unpack, manually.

B3nson wrote:On my side i can confirm that -none- (i tried about 30 nzb, created by binsearch) of my downloads finish properly. When the files are OK (they do not need repair) they end up with the error message "Unpacking failed, an expected file was not unpacked ". When it is the case i just need to unpack them with unrar and it works. Otherwise, i need to download the par 2 manually, repair and unpack, manually.

Your problem is most likely caused by a mismatch between how unrar and SABnzbd think
the filesystem works. I assume the filenames involved contain accented characters, like è and é?
A quick fix is to disable SABnzbd's extra check in Config->Switches, "check unpack result".

No need to look into it further on my behalf, but thanks for looking at it shypike. Turns out in between me installing it and finding out there was a problem a fix was already applied. The plugin was missing a library: http://forums.freenas.org/showthread.ph ... #post36332

Thanks heaps for your time shypike, I'm very sorry to have wasted it.

DarkCuddles wrote: Thanks heaps for your time shypike, I'm very sorry to have wasted it.

Well, OK.
Although the 1x22 episode NZB did have issues with the casing of the file names.
So, that's a problem that cannot have been solved.

shypike wrote:

B3nson wrote:On my side i can confirm that -none- (i tried about 30 nzb, created by binsearch) of my downloads finish properly. When the files are OK (they do not need repair) they end up with the error message "Unpacking failed, an expected file was not unpacked ". When it is the case i just need to unpack them with unrar and it works. Otherwise, i need to download the par 2 manually, repair and unpack, manually.

Your problem is most likely caused by a mismatch between how unrar and SABnzbd think
the filesystem works. I assume the filenames involved contain accented characters, like è and é?
A quick fix is to disable SABnzbd's extra check in Config->Switches, "check unpack result".

Hum, ok but it was working properly with the older version of Sabnzbd. It's only since the upgrade to 0.7.2 and 0.7.3 that jobs started to fail. The older version was a 0.6.x from what i remember.
I tried to disable the unpack check, i will tell you if it changes anything.
I'm assuming it will correct the problem only for files that do not need repair, correct?

B3nson wrote: I'm assuming it will correct the problem only for files that do not need repair, correct?

Yes, but make that: "repaired and/or verified correctly".

That it worked correctly with 0.6.x is unlikely.
At least for the basic problem of a file system using 8bit ASCII instead of UTF-8,
combined with an OS that doesn't reports things properly to Python.
Which OS and file system are you using?

HFS, default Mac OS X Lion install.

Ok, so an NZB just finished with the "check unpack result" unchecked. The result is that sabnzbd does not report it as failed, but it is not unpacked. I have to unpack it manually.

OK, just plain old HFS on plain OSX Lion.
In that case, none of my file system comments apply.
I'll let you know when I've analyzed the material you sent.