Public bug reported:
Today my edgy computer failed to boot properly; it dumped in text mode, saying
that one of my partitions was not properly unmounted; then fsck failed, and i
was dumped to a shell with a dire warning about filesystem corruption.
rebooting, the same message came back again, and again a shell.
the only way to get the computer to continue booting was to type in the shell:
fsck -y /dev/hda6
I think this is not intuitive ;-)
99.9999% of users of ubuntu, if they find out how to run fsck at that prompt,
will say YES to every of fsck's suggestions, only a few kernel hackers would
know enough to not follow the defaults in fsck.
so i suggest that instead of dumping the user to a shell, something like
that is displayed:
"Serious filesystem corruption detected; Press <Enter> for automatic
recovery, <F12> for manual recovery (expert mode)"
If the user presses enter, fsck -y is ran on the partition where the
corruption occured. If the user presses F12, he is dumped into a shell
as is the case now. btw, after the fsck -y, all appears fine, and i
think i didn't loose anything.
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
user must run fsck by hand on FS corruption detected at boot
https://launchpad.net/bugs/86583
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
