[Bug 1972099] Re: computer startup in emergency mode when NFS partition is inaccessible
Mauricio Faria de Oliveira
1972099 at bugs.launchpad.net
Sun May 8 19:32:53 UTC 2022
Thanks for the bug report!
Changing title to indicate actual impact, and reassining to systemd as
the 'nofail' mount option (which you tried) apparently didn't work.
Per systemd.mount(5) man page:
nofail
[..] This means that the boot will continue without waiting
for the mount unit and regardless whether the mount point
can be mounted successfully.
** Summary changed:
- computer startup crashes when NFS partition is inaccessible
+ computer startup in emergency mode when NFS partition is inaccessible
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1972099
Title:
computer startup in emergency mode when NFS partition is inaccessible
Status in systemd package in Ubuntu:
New
Status in util-linux package in Ubuntu:
Invalid
Bug description:
Hello.
When the NFS partition described in the /etc/fstab file is not accessible (The server is down) starting the computer in version 22.04 is impossible.
Message: "you are in emergency mode. After logging, type "journal -xb to view system log
This was not the case in previous versions. The computer waited 90
seconds and booted without the NFS partition.
I tried adding the nofail or nobootwait options but it didn't work.
The line is coded this way:
192.168.0.31:/media/MyDatas /media/NFS defaults,user,auto,_netdev,bg
What is the correct solution?
Thank you for your reply
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972099/+subscriptions
More information about the foundations-bugs
mailing list