SABnzbd Forums

Hello,

I've seen two other threads in this forum regarding problems with unRARing, the first being something Linux related which I do not think is my issue here, and the second was someone who connected a USB drive and had the downloads moving to there. I'm running the latest version of SAB (installed to C:) and everything was great until I changed my drive letters under "Config" --> "Folders" from D: to X: (ran out of space). At first, I had only changed the "Completed Download Folder" to X: and all worked fine, after changing all paths to X: everything stays in "incomplete" in their RAR format.

Any ideas why changing the drive letters would have done this?

Changing the incomplete folder while downloads are in progress could do this. The current code does not move over the contents of the previous incomplete folder, and does not allow splitting the incomplete folder across different locations as unrar would then not work.

It is recommended to only change the incomplete folder when the queue is empty, or nothing in the queue has been downloaded yet.

Fraser,

I had something strange last week with  downloads not succesfully unpacked anymore (http://forums.sabnzbd.org/index.php?topic=1434) with the "Temporary Download Folder" and "Completed Download Folder" were on different drives. Oh no, I hadn't changed the folder during a download.

My hypothesies (but a very, very long shot): SAB doesn't like it when those those directories are on different drives.

My workaround: have those two directories on the same drive.

Can you check if that helps?

The incomplete and complete folders can exist fine on different drives. Infact, I have always had it set like this fir a few years.

All of my directories are on new drive and I've ran a few test downloads after the queue was done (I hadn't changed the settings in the middle of a queue) and cleared most of the cache files -- no change. I'm thinking at this point I backup sabnzbd.ini and reinstall everything.

That seemed to do it... I don't have any idea what would have caused it but thanks for the suggestions.

Fraser wrote: That seemed to do it... I don't have any idea what would have caused it but thanks for the suggestions.

Fraser, *what* seemed to do it?

sander wrote:

Fraser wrote: That seemed to do it... I don't have any idea what would have caused it but thanks for the suggestions.

Fraser, *what* seemed to do it?

fraser wrote:I'm thinking at this point I backup sabnzbd.ini and reinstall everything.

I reinstalled SAB and it started working again, in retrospect I probably could have deleted everything SAB under AppData.