The symptoms have changed. It's now breaking as follows: After the filesystem has corrupted and gone read-only, the kernel will not boot at all. There's no sign of the purple boot screen. I tried with Ubuntu kernels 2.6.35.22, 2.6.34.24, and a "2.6.36.999" upstream kernel that I was asked to install in the course of diagnosing another bug. Each of them dropped me into a busybox, though I believe the 2.6.34 kernel gave a lot of output and then hung, making it harder to see that I was in a busybox shell.
I booted off an old Lucid beta CD and ran e2fsck -v -f on my root partition. Dozens or perhaps a few hundred messages, mostly fsck counting more free blocks than expected (usually about a dozen more). Now the system will boot from the 2.6.34 kernel; the 2.6.35 and 2.6.36 ones give a message (still in the white-on-black text console, so without ever getting to the purple boot screen) along the lines of udevadm callbacks not being allowed before udev is configured. The system won't budge after that. This is right after the "Starting up ..." message on the text console. -- Unbootable system after fsck failure https://bugs.launchpad.net/bugs/570134 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
