computer startup in emergency mode when NFS partition is inaccessible
Bug #1972099 reported by
geole0
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| util-linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
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.
What is the correct solution?
Thank you for your reply
Revision history for this message
| Mauricio Faria de Oliveira (mfo) wrote | #1 |
| summary: |
- computer startup crashes when NFS partition is inaccessible + computer startup in emergency mode when NFS partition is inaccessible |
| Changed in util-linux (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
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.