SABnzbd Forums

I'm on Windows 10 Pro 64bit.

The _UNPACK_ directory is going into my Completed Download Folder on my \\NAS\. To make matters worse, sab appears to extract the entire archive into _UNPACK_ (makes sense so far), but then COPIES the files to their destination, which are on the same partition! Why is it copying, why not move? Is this the normal behavior?

The wiki does state "The completed download folder is the default download location for all items..." I'm noticing the "... all items" part in that sentence in regards to why possibly _UNPACK_ is traveling, but then I'm confused by the Temporary Download Folder description of "...store files as they are downloaded. Once the file is complete, it will verify then extract to the Complete Folder. " That makes me think all files should should stay in "incomplete/$nzbname/_ADMIN_/", including _UNPACK_,

The copying instead of moving is puzzling. I haven't been on Windows in some years, but I do remember UNC being problematic from a server perspective, so maybe sab copying is its way of trying to be compatible or paranoid for success.

My 2 relative directories (I see nothing in the switches that should cause these problems).
Temporary Download Folder: Downloads\incomplete
Completed Download Folder: \\NAS\misc\

P.S. It appears that the all reigning henchman of this application is "Categories" :-)

Are you on 1.1.1?
Could you try 1.1.0? Some users reported that only in 1.1.1 they see this problem, while in 1.1.0 it would still do a simple rename instead of move.

You can also disable 'Enable folder rename', does that help?

Sorry, yes I'm on 1.1.1. Didn't have much time before work, but if I manually perform a copy on the nas, it is 2x faster, seems odd. I'll toggle off the folder rename switch when I get home (if it's on). I'll try 1.1.0 with the --new switch on a different host:port and see if that works fine (will have to figure out how to load a nzb via url though). If it does work fine, i might use that (or not and keep the fix in script).

Another user just reported that switching off "Enable folder rename" fixed the problem for him.

Works. Disabling "Enable Folder Rename" did the trick. Thank you.