Hi. 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!
[Not] Creating Volumes when external volumes unmounted.
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: [Not] Creating Volumes when external volumes unmounted.
We're reviewing the way we should handle unmounted drives.
The current way causes too much confusion.
However, we will not fix this for 0.5.0,
because otherwise we'll never release a Final.
The current way causes too much confusion.
However, we will not fix this for 0.5.0,
because otherwise we'll never release a Final.
Re: [Not] Creating Volumes when external volumes unmounted.
Understood. If you want to bounce some ideas around for .5.0.1 let me know.
Thanks for the great work as always.
Thanks for the great work as always.
shypike wrote: We're reviewing the way we should handle unmounted drives.
The current way causes too much confusion.
However, we will not fix this for 0.5.0,
because otherwise we'll never release a Final.