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 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 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.

How can this be fixed?

  • 3
    Try adding the nofail mount option to that drive. – muru Jun 21 '15 at 0:15
  • 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 4:49

As muru mentioned, add nofail. But also add a low timeout with something like x-systemd.device-timeout=2, because the default timeout seems to be 90 seconds.

Example from my fstab:

LABEL="test"  /mnt/test  ext4  defaults,nofail,x-systemd.device-timeout=4  0  2
  • 2
    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 2:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.