Description of problem: I have a few docked SATA harddrives on my workstation; sometimes I move one out or in. They are specified as not to be checked at boot in /etc/fstab; like this: # Entry for /dev/sdd1 UUID=2906c70d-377b-4e5d-8430-c947ef9e0b13 /data xfs relatime 0 0 Unfortunately for me, systemd (local-fs) behaves as the non-presence of this drive is a catastrophic error and stops booting to go onto maintenance mode. The only option I have is to comment this line in /etc/fstab when the harddrive is not present and reboot (or never add it in fstab) I think when 0 0 are specified, systemd service should be more user friendly and just trigger an error in the logs rather than stopping everything :) Cheers, Chris. Reproducible: Steps to Reproduce:
I think that if you add the nofail option to the fstab line, then the system should boot even when that partition is not available.
Thanks, it works! Never used this option before with initscript, but that's the intended behaviour indeed. I close this bug as invalid then.
Status: NEW => RESOLVEDResolution: (none) => INVALID