SABnzbd Forums

I'm going NUTS!

I installed a new LaCie NAS on my LAN the other day, mounted it, assigned its share as my destination folder for downloads, and all was well. The format was as follows:

/Volumes/openshare/

Where openshare is the drive's open directory (read/write) which appears under my root when mounted.

Now a few days later, it's simply stopped working. SAB seems unable to write to the drive, refusing to acknowledge it when I try and re-enter and save the folder configuration. I have tried mounting the drive as SMB and AFP, neither worked. There seems there is nothing I can do to get SAB to recognise the damn drive as a vable destination folder.

So, I need your help. Either

a) a way to force SAB to recognise it or
b) a script to automatically move any completed downloads into the appropriate destinations on the NAS based on their type. I know there is something along these lines in the forum but I could not get it to work with OSX.

Please help! I bought the drive SPECIFICALLY to use as a media storage for SAB/PLEX, and now it's all messed up.

Thanks in advance!

UPDATE: I fixed it - looked at Volumes root under Terminal and there were a whole bunch of folders not shown in Finder, including one called openshare. the REAL openshare (i.e. the one on the NAS) was renamed openshare-1, which is why SAB could not find it. A bit of rm -R on the bogus folders and the problem is solved.

Still, if there were a way to ensure SAB didn't create the folder if the share is accidentally not mounted (which is what I'm guessing caused the whole mess), or to use a script to move the files to the NAS after download (thus avoiding the problem) it would be a lot better. As it stands I'm just gonna have to watch out that SAB never starts unless the share is mounted!

SABnzbd is completely dependent on the operating system.
If a non-mounted drive still results in the successful creation of folders,
how is SABnzbd supposed to know that anything is wrong?
I wouldn't know a sufficiently general way to check this issue.

To protect from this you probably need a small shell script that
checks conditions and then starts SABnzbd.

I suggest you set the "Temporary Download Folder" to a location on the internal disk
and the "Completed Download Folder" on the external disk.
Unpacking is from the internal disk to the external disk, which will be faster.

That's exactly how it's set up. Temp internal, completed external.

I really need to find a crash course in shell scripts...