Andrew's bug does have the same symptoms of mine, except for one
unknown: we don't know if he had file system errors.
Andrew, do you know if you have filesystem errors? You can get the fsck
to complete by booting into recovery mode (root shell), finding out
which partition has Linux on it if you don't know ("fdisk -l" lists
partitions) and running "fsck [device name]", eg "fsck /dev/sda1" or
"fsck /dev/sda3" or whatever. (Incidently, if you repair errors and new
errors show up on subsequent boots, this can be a sign of a failing hard
drive.) You can also run fsck from the Live (install) CD if you boot
into it. You cannot run it during normal operation, as the filesystem
must be read-only or unmounted.
--
When fsck fails, the machine reboots and does the check again
https://bugs.launchpad.net/bugs/204097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
