filesystem mount failures during boot halt boot with a blank screen
Bug #1152274 reported by
Seth Forshee
This bug report is a duplicate of:
Bug #1096079: boot fails when a kernel filesystem can't be mounted (e.g., due to a dangling symlink).
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mountall (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
A recent kernel bug caused mounting of efivarfs to fail in some cases. When this happened the boot simply stopped with a blank screen, providing no information as to what went wrong. This obviously isn't optimal. If we're unable to continue booting we should at minimum display a message to the user providing the reason.
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in mountall (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
"medium" because it's an unlikely event that a supported kernel filesystem will fail to mount - this is the only time I've heard of this happening in the past 4 years of mountall. But yes, we should spit something to the console when this happens, so the user can at least understand *what* has happened, given that starting plymouth splash to display an error prompt is a chicken-and-egg problem.