Public bug reported:
I recently had an incident with my ext4 filesystem corruping itself and
going read-only. (It does that sometimes, since lucid or so, but that's
a separate bug). I had two of those incidents over the past few days.
The first lost me some data but otherwise seemed to leave the system in
a workable state; the second left me with an unbootable system.
None of the installed kernels (one from Lucid, one from Maverick, and a
2.6.36 mainline one) would boot. It looked as if I was thrown into
busybox, though there were lots of output and no prompt. The output
looked like a list of available devices.
After a manual fsck from a live CD the system boots fine again.
Interestingly the fsck didn't even fix much; there were perhaps a few
dozen lines of output.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Unbootable after filesystem corruption
https://bugs.launchpad.net/bugs/675416
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
