Filesystem - How To Configure Systemd To Ignore Fstab Drive Mount Failures? - Ask Ubuntu
Filesystem - How To Configure Systemd To Ignore Fstab Drive Mount Failures? - Ask Ubuntu
When I have first set up Ubuntu 15.04 (which is first to switch to systemd AFAIK) I was
puzzled by why does it only boot some times and then become unbootable (failing to the
10 systemd shell instead of proceeding to start X). I have chosen upstart boot from the grub
menu and then came to the conclusion it fails to mount my Windows C: drive (which I have
assigned a static mount point) and this is the reason. But the question is not why does it
fail to mount it but why does it fail to boot then (given there are no files needed during the
6 boot process on that drive) and how to overcome this.
I have also configured it to mount my USB hard drive to a static mount point as I want it to
be found in a particular place and I hate it to appear on the Unity panel, needless to say
this makes my system unbootable (unless I use upstart again) when I take my laptop
somewhere without taking the USB drive with me.
Share Improve this question edited Jan 18 '18 at 12Z56 asked Jun 21 '15 at 0Z05
Follow Anwar Ivan
!"
#$% 28 183 299 $&'% 63
# 149 208
1 de 2 15/11/21 13:09
filesystem - How to configure systemd to ignore fstab drive mount failure... https://askubuntu.com/questions/638985/how-to-configure-systemd-to-ig...
3 Try adding the nofail mount option to that drive. – muru Jun 21 '15 at 0Z15
1 Strangely, this results in fuse: unknown option 'nofail' errors if you do mount -a , but it
still works anyway – endolith May 19 '16 at 4Z49
As muru mentioned, add . But also add a low timeout with something like
nofail
x-systemd.device-timeout=2 , because the default timeout seems to be 90 seconds.
18
Example from my fstab:
4 It's worth nothing that if you make changes to /etc/fstab while in emergency mode, they won't be
picked up until you actually reboot. Just exiting emergency mode by closing the shell (as it
suggests: "systemctl default" or "^D" to try again to boot into default mode) will not re-read the
fstab, so the fsck task that was failing before will continue failing. – Derek Lewis May 24 '17 at 2Z29
2 de 2 15/11/21 13:09