0.5.0 Beta1 - Downloads to external drive changes on system startup

[qwerty967]

I'm having a similar issue to this post.

Previously, I've been using 0.4.x for Mac. The download folders were located on an external drive: /Volumes/freeagent/incomplete and /Volumes/freeagent/complete. Everything worked well.

Now, I have switched over to using 0.5.0 Beta1 on Ubuntu using jcfp's PPA, running it as a daemon. I have it set to download to an external drive: /media/freeagent/incomplete and /media/freeagent/complete. The problem is SABnzbd changes the location back to the defaults (downloads/complete and downloads/incomplete) on system startup. I can change it back to the external drive, but it'll happen again on the next system restart.

I've tried a couple things to make sure that it's the external drive that is creating problems. First, I created symbolic links to the external drive, but this exhibits the same behavior described above. Next, I created folders on the internal drive to see if the settings change on reboot, and they don't.

I suspect the problem is that on startup, SABnzbd is started before the external drive is mounted. Since SABnzbd can't find the volume, it changes the settings back to the default locations.

[shypike]

Isn't the solution to make sure the external drive is mounted
before SABnzbd is mounted?
Before people were always complaining that their downloads went
nowhere when their external drive wasn't mounted.

Is it possible to tweak the order in which external mounting
and SABnbzd take place?

[qwerty967]

Thanks for responding shypike. I've solved my issue by using Gnome's autostart to launch SABnzbd instead of running it as a daemon.

[qwerty967]

Grrrr....

Now it won't let me set the directories as /media/freeagent/complete and /media/freeagent/incomplete anymore. I click save and reload the folder settings, it reverts back to downloads/complete and downloads/incomplete.

The post-processing scripts folder setting (/media/freeagent/scripts) is sticking though.

[shypike]

Are you sure the paths exist at that time?
I'll review the code to see if there is an attempt to create the folder despite already existing.

The scripts folder is a bit different, in that SABnzbd never tries to create it.
It will report it's absence.

[qwerty967]

Once again the problem is on my end. I'm getting a "read-only filesystem" error when I try to create a file on the volume. I really regret formatting the drive as HFS+, because Ubuntu is having problems with it. I'm going to reformat it as FAT32. It's going to be quite an undertaking because I have 900+GB of stuff on a 1TB hard drive.