25

I have this line in my fstab:

sshfs#ecarroll@o99:/opt/dealermade/ftp/inc /opt/dealermade/ftp/inc fuse defaults,idmap=user,users 0 0

For whatever reason it didn't work -- that's fine. How do I make it not stop the boot sequence. It prompted me to to hit S to skip or M to manually repair. If it isn't the boot volume, I just want my volumes to fail mounting with nothing more than an entry in logs.

Improve this question

3 Answers 3

Reset to default
14

I'm not familiar with sshfs, but I know the nobootwait option works for local disk partitions. Maybe try:

sshfs#ecarroll@o99:/opt/dealermade/ftp/inc /opt/dealermade/ftp/inc fuse defaults,idmap=user,users,nobootwait 0 0

(A quick google search also shows archlinux uses nofail as per this thread. A little more googling shows that nobootwait might be a non-standard Ubuntu feature... curious to see if it resolves your issue. )

Improve this answer
4
  • nofail did not resolve the issue, nobootwait did. Commented Oct 31, 2012 at 17:52
  • 5
    The difference between nofail, and nobootwait can be found on this question. Commented Oct 31, 2012 at 19:47
  • 1
    For me, nofail worked for an USB drive on Debian 8. My system failed to boot before when it wasn't connected, now it ignores the error. Commented Sep 7, 2015 at 16:37
  • 1
    Note that Ubuntu deprecated nobootwait. Commented Feb 9, 2024 at 17:08
4

nobootwait worked very well for me in Linux Mint until version 18. I miss it.

Using nobootwait could result in writing to your OS drive rather than a mounted drive, but only if you are careless. If you always write to a folder on your mount, then if the mount fails the folder will not exist and the write fails.

Improve this answer
5
  • 10
    You can also mitigate this problem by doing chattr +i /the/mount/point to deny every user (even root) access to the directory if nothing is mounted on it. Commented Jul 3, 2018 at 12:20
  • This is a very interesting comment. But in case you come accross lsattr: Inappropriate ioctl it means that your filesystem does not support it. Commented Nov 14, 2020 at 21:17
  • 1
    @samhocevar just stumbled across this, and noticed your comment. I have tended to do "chmod 000" on my (network) mountpoints for the same reasons, it seems to work, and is very obvious in a full directory listing whether the mount is active. Are there any gotchas with my approach? Commented Nov 23, 2023 at 17:48
  • 1
    @m4r35n357 chmod 000 will not prevent root from accessing the directory; it may not turn out to be a problem, but be aware of that difference. Commented Dec 12, 2023 at 17:32
  • @samhocevar THX for the response. Not a problem for me, as there is nothing in there to access (unless I want trouble!), it is just a nice, simple, filesystem-level indication whether a mount point is in use. Have you tried it? Commented Dec 13, 2023 at 9:40
3

nofail mounts wont prevent the system from booting on failure.

nobootwait was an upstart specific option to prevent upstart from waiting for the device.

Note that since systemd (the replacement for upstart on Ubuntu and most distributions that were using it) mounts fstab entries asynchronously, nofail is enough.

/dev/sdb1 /mnt/ auto nofail 0 2

In the example above, auto means that the file system type will be auto detected. It could be replaced by ext4, btrfs or vfat for example.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.