SABnzbd Forums

I suspect that I have a parameter set up improperly somewhere, but I can't seem to find it.  What happened is that I downloaded a giant nzb, which was itself broken into a set of smaller pieces that were individually RARed and PARed.  It appears that the PAR repair failed on five of the twenty pieces, so post processing was aborted.  Then I can see a directory get created in my Complete directory, and Sabnzbd logs that it's cleaning up.

It looks like all fifteen pieces that were OK did not get UNRARed.  This I would expect.  However, all but two of the pieces that passed the QuickCheck got deleted, and all of the pieces that failed verification got deleted.  They're nowhere to be found.  They're not in the Incomplete or the Complete folders.  It's like they vanished, I suspect in the "clean up" process that was in the log.

Do you guys have any idea what may have happened?  I don't want this to happen again.  Do I have a setting wrong somewhere?  It seems suspicious that a few of the pieces somehow remained intact, but the rest were lost.  Sabnzbd's been working fine for a few weeks on this machine without any problems before this happened. I attached the relevant portion of the log.

The hard drive is just over 2x the size of the nzb being downloaded.  Maybe I ran out of hard drive space?  Does Sabnzbd copy files to the incomplete directory instead of move?

Thanks!

Details:
Version = 0.5.6
OS = UnRaid 0.4.7 (Slackware Linux)
Install type = Python source
Skin = Plush
Firewall = None
IPV6 = No
Reproducible = Not sure, that's what I'm trying to avoid

Disk full would mean trouble here.
I advise to upgrade to release 0.6.0 beta 4, which handles this much better.

Ok.  Given the lack of any type of error message saying what happened, I figured it was probably something like there not being enough room to copy and extract, so that fails, and then Sabnzbd deletes all the RARs thinking everything was fine.

I'll try upgrading to the beta.  Thanks for taking a look!