问题原文
原帖链接 · sebt · CC BY-SA 4.0
During boot, with pre-systemd versions of Ubuntu server (eg. 14.04), if a non-critical fstab disk was offline, the system would wait to mount the disk (30s iirc), timeout and continue booting.
Since upgrading through 16.04 to Ubuntu 18.04, thanks to systemd's dependencies I presume, a missing fstab disk stops the boot process resulting in the "Emergency mode... Press Enter for Maintenance" prompt at boot time.
- Is there a way to change this behaviour by default? Ie. simply continue booting or an option to flag disks as non-critical?
- Failing that, is there a straightforward systemctl command to 'continue booting ignoring missing disk' from maintenance?
已采纳解答
原帖链接 · HBruijn · CC BY-SA 4.0
In the /etc/fstab entries for your mounts you can add systemd specific options, including the nofail option will instruct systemd that the boot can continue without waiting for the mount unit and regardless whether the mount point can be mounted successfully.
You can add the options x-systemd.device-timeout and or x-systemd.mount-timeout to customize time-outs.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
