SABnzbd Forums

I am receiving lots of unpacking failed errors.  Pretty much every download is showing an error due to "an expected file was not unpacked" or "CRC error".  Anyone got any suggestions?  I am very new to using sabnzbd+ so I thought it may be something I have configured incorrectly, but I saw anther thread with a similar problem so thought I would take a chance and ask for some help.

I noticed that if I extract the rar files using a 'unrarx' or 'the unarchiver' the extract without a problem it is only form within sabnzbd+

However I have no idea to fix the failed downloads due to CRC errors.

I am running version 0.5.0Beta1 on Mac Snow Leopard, the download folder is on my mac mini hard drive not external.

Many thanks

Ruzsb

"an expected file was not unpacked" can be caused by uploads
done by careless Windows users.
Stop SABnzbd and "fix" it by changing a line in the sabnzbd.ini file.
/home/USERNAME/Library/Application Support/SABnzbd/sabnzbd.ini

Find line and change it to Please upgrade to Beta4, we do not support Beta1 anymore.

CRC errors are another problem.
When unrarx unpacks the files without problems, then that means the rar-files are correct.
This would throw suspicion on the unrar program that's included with our
program. This comes directly from WinRar's site is outside our control.
I have to discuss this with our OSX expert.

Thanks for the reply.  I upgraded and made the change to the ini file.  I am no longer receive the failed errors but now the downloads are not being uncompressed they download fine and are sorted correctly but instead of finding the correctly named .avi file there is a folder containing all of the rar files.

Any other suggestions.

Ruzsb

I think either the rar files are bad or the included unrar program fails.
SABnzbd now no longer checks the results of unrar.
Can you send an example of a problematic NZB file to bugs at sabnzbd.org ?

The rar files are fine because I can manually unrar them.  It just seems that no extraction is taking place - no errors are being returned just no uncompressed file.  Could it have anything to do with the fact that they are being moved to an external hard drive as part of the sorting, or should the extraction take place prior to the sorting?

Thanks

Ruzsb

First extraction is done and after that sorting starts moving files.
The external drive should not be a problem, provided there are no access rights problems.

Have you tried an experiment where you just keep all the files local?
Just to exclude the external drive as a potential cause?

I do not know what the current status is on the unpacking failed problem, but I am having the same problems. It happens with everything I download with Sabnzbd. This problem started with the first beta version I tried of 0.5.0 (beta4). Later on RC3, and now RC6, and the problem is still here.

I am running Sabnzbd on a Win7 Pro x86 machine. I am not using any external drive, Sabnzbd is doing everything on my C-drive. I am using the .INI file from my previous 0.4.12 Sabnzbd folder (which did not have this problem).

If you need any further information on this problem please let me know.

There is no general "unpack" problem.
You need to be more specific. What happens?
Which error/warning message do you get?

The error message is something like: unpacking failed: an expected file was not found

And this message is given for everything I download using Sabnzbd

billy wrote: The error message is something like: unpacking failed: an expected file was not found

And this message is given for everything I download using Sabnzbd

That sounds like a CRC problem. What host are you with, and do you have "Post Process Only Verified Jobs" turned on?

This may well be a case of foreign character problems.
Check in the log which file failed.
Which operating system do you use?

There is a work-around for persistent problems like this.
Special option the INI file "unpack_check=0".
See http://wiki.sabnzbd.org/configure-special

I just checked the error message, it says: "Unpacking failed, an expected file was not unpacked"
Unpacking it manually then works fine, there is nothing wrong with the files (and sometimes there is something wrong, but I can always (manually) recover it using the Par files).

Post-Process Only Verified Jobs is turned ON. I turned it OFF and tested it again, no change in the result. As a Host i am using Eweka.

I tried the special INI option "unpack_check=0", that resulted in no more error messages, but the result is still the same: the files are not unpacked (in the history overview it says: "Unpacked 0 files/folders in 0 seconds").

OS = Win7 Pro x86

Does it do this consistently for every NZB or just for specific ones?

Please send an example NZB to bugs at sabnzbd.org (with a reference to this thread).
Add in your sabnzbd.ini file too (but remove passwords first!).

I have found A solution to this problem: I erased my INI file (which I was still using from previous SABnzbd versions), and let SABnzbd generate a new one. This seemed to be a solution to my problem. Now SABnzbd is unpacking everything as usual.

Thanks for all the help.

I have the same problem, however, my installation of sabnzb is not an upgrade, so deleting the ini file does not help.

Any other ideas?