plymouth fsck suggests user skips mounting root FS on failiure
Bug #578184 reported by
Martin Erik Werner
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mountall (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: plymouth
When a filesystem check of the root (/) filesystem fails, interactive plymouth offers the alternative to skip (key s) the mounting of the filesystem.
But in the case of the root filesystem this will obviously always (?) cause boot to fail (as it were, with plymouth locking up at "searching for /tmp").
Because of this, plymouth should not suggest skipping mounting of the root filesystem when fsck fails.
| Changed in plymouth (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Benjamin Kay (benkay) wrote | #1 |
Revision history for this message
| Martin Erik Werner (arand) wrote | #2 |
| description: | updated |
| summary: |
- plymouth fsck suggests user skips mounting root FS + plymouth fsck suggests user skips mounting root FS on failiure |
Revision history for this message
| svaens (svaens) wrote | #3 |
Revision history for this message
| Martin Erik Werner (arand) wrote | #4 |
| affects: | plymouth (Ubuntu) → mountall (Ubuntu) |
Revision history for this message
| anil (rakhianil2003) wrote | #5 |
To post a comment you must log in.
Also, not sure if this should be a separate bug, but the user should never see the message "Serious errors were found while checking the disk drive..." unless fsck actually found serious errors while checking the filesystem. In the case described here, pressing c to cancel a routine fsck should resume normal startup without asking the user any more questions because fsck did not find any errors while checking the filesystem. Only in the very rare case that the user cancels the fsck *and* something is actually wrong with the fs should the user see the "Serious errors..." message. And I agree that, when that happens, naively offering the user the option of not mounting / is probably not the most appropriate course of action.