Invalid fstab entry leads to an hanging system rather than a debug command line
Bug #1471258 reported by
Sebastien Bacher
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
While playing with the new desktop iso I had a case of buggy fstab entry, that leads to a system hanging out boot, it should send you to a debug shell or friendly recovery instead
Changed in systemd (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Martin Pitt (pitti) |
Changed in systemd (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Keeping notes: I added "LABEL=mystery /var ext4 defaults 0 0" to /etc/fstab to try and reproduce this.
- On a standard cloud image (server-ish, no graphical plymouth) boot waits for the device to appear for 90s, times out, and I get into the emergency shell. So that works alright.
- On a standard desktop image (graphical plymouth) I see the running dots for 90s, then they stop. I need to switch to Alt+F7 to see the emergency shell, because plymouth does not get stopped. So that's something to fix. Is that the case for you as well? I. e. is it just that the emergency shell doesn't appear by itself but you can switch VT to it? Or do the plymouth dots just go on and on? Where can I download that desktop ISO?