Folder paths not sticking - reset on reboot

Support for the Debian/Ubuntu package, created by JCFP.
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • 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.
Post Reply
dbznokia
Newbie
Newbie
Posts: 11
Joined: July 13th, 2011, 7:04 am

Folder paths not sticking - reset on reboot

Post by dbznokia »

Hi guys,

I'm running latest desktop version of Ubuntu with SABnzbd. I have the OS and app installed on a SSD drive. I also have a data drive (\media\DATA) in the same machine which is a 7200RPM HDD. The problem I have is that everytime I reboot the machine, SABnzbd reverts to default folder paths which is a problem as the OS drive is only a 32Gb drive. The path to the DATA volume doesn't seem to stick.

I've read here that it could be related to the software running before the HDD is mounted but I thought that would only be an issue for remote mounts? Would that also be the case for a locally mounted drive? If it is, how can I add a delay to the automated start of SABnzbd?

thanks for your time. ???
User avatar
jcfp
Release Testers
Release Testers
Posts: 1004
Joined: February 7th, 2008, 12:45 pm

Re: Folder paths not sticking - reset on reboot

Post by jcfp »

dbznokia wrote:I've read here that it could be related to the software running before the HDD is mounted but I thought that would only be an issue for remote mounts? Would that also be the case for a locally mounted drive? If it is, how can I add a delay to the automated start of SABnzbd?
No need to delay anything, just make sure the drive gets mounted (i.e. add it to /etc/fstab if necessary; google knows how).
Post Reply