In this question I asked how to prevent a media failure from halting the system boot process. However, I got two suggestions for
What is the difference between the two?
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.Sign up to join this community
nofail allows the boot sequence to continue even if the drive fails to mount.
This is what
fstab(5) says about
The mountall(8) program that mounts filesystem during boot also recognises additional options that the ordinary mount(8) tool does not. These are:
bootwaitwhich can be applied to remote filesystems mounted outside of /usr or /var, without which mountall(8) would not hold up the boot for these;
nobootwaitwhich can be applied to non-remote filesystems to explicitly instruct mountall(8) not to hold up the boot for them;
optionalwhich causes the entry to be ignored if the filesystem type is not known at boot time; and
showthroughwhich permits a mountpoint to be mounted before its parent mountpoint (this latter should be used carefully, as it can cause boot hangs).
fstab(5) has this to say about
nofaildo not report errors for this device if it does not exist.
Since this old question has a high Google rating, I'll mention that since "nobootwait" doesn't work with systemd, the correct method is to set a short timeout of, say, 9 seconds with "x-systemd.device-timeout".
/dev/sda2 /mnt/other auto defaults,nofail,x-systemd.device-timeout=9 0 2
(Edit: I've increased the timeout from 3s to 9s because it seems that Ubuntu occasionally does a quick filesystem-check on bootup that can last longer than 3s.)
As mentioned by Stéphane, nobootwait is limited to ubuntu+derivatives.
Nofail will keep trying to mount the drive as cjm pointed out, however, the boot process will continue after the mount reaches timeout. If you don't expect the drive to be there regularly as to warrant the extra 90 seconds or so bootup when it's absent, don't automount it in fstab.
(P.S. I put this as cjm's answer sounds as if the system will ultimately fail to boot).
This article seems to explain the difference well
mountall tries to automount all entries from fstab that have the defaults or auto mount options. It will halt the boot process if such entries cannot be mounted, except when the mount option nobootwait is given.
fsck tries to do a filesystem check on all entries from fstab that have the sixth field set to 1 or 2. Non-critical drives typically have this field set to 2. It will halt the boot process if such filesystems cannot be checked, except when the mount option nofail is given.
Disclaimer: I am not a fstab expert and cannot guarantee/verify the above information to be true. All credits belong to the author of that article.