SABnzbd Forums

I know this wasn't going to make it into 5.0 but hoping I can get it up the food chain for the next release.

I have a MacMini w/ a 1.5TB External USB drive for my storage.

In the rare time that the USB drive, called "media" is not mounted, Sabnzbd creates (as advertised) the directories locally. The problem is that it then macosx refers to the external volume as "media 1" when it's mounted, and then trouble happens because now I have a drive that still mounts as "media" but osx thinks it's "media 1" and sabnzbd starts downloading everything to the internal drive.

On top of having to go into terminal to delete the dirs, etc. to fix this... any suggestions on how to avoid this - other than making sure my external is always booted?

Ideally I'd love it NOT  to create a new volume if it wasn't mounted - as an option.

Thoughts... suggestions... ideas?

Thanks!

The trouble is with coming up with a general solution.
First distinguishing a non-mounted volume from a not-yet-existing folder is not trivial.
When the destination doesn't exist what do we do? Wait?
People might have a load of categories defined with each having their own folder/volume.
So suppose we now pause post-processing when a volume isn't mounted.
What needs to happen to downloading, do we just fill up the temp download folder?
The next question will be: why don't you process jobs that don't need that missing volume?
It soon will get very complicated indeed.

I'm not saying we won't do anything about this, but it's far from trivial.
And slowly drifting away from what SABnzbd was actually supposed to do.

personally, i'd be perfectly happy w/ a "if it's not there, don't create it and stop all" option. it may be drastic but it does solve the bigger problem of (a) creating a non-easily access directory in the Volumes folder that then needs to be cleared, moved, etc. 

i get the complication but it seems that a simple but definitely "all-stop" solution is to just to have an option if it's not there, stop everything. if people didn't want to use this preference, don't select it.

thoughts?

joshua wrote: if people didn't want to use this preference, don't select it.

Like we don't have to many options already...
Having "options" is a no-go here, else it will get even more complicated.
I'll think about it.

yeah, definitely a lot of options. i get that... i love your product and don't want to seem at all ungrateful - this just continues to plague me and trying to find a simple solution.

thanks again for thinking about it.