Short story :
do-release-upgrade -d
reboot
Some (all ?) partitions are remounted as read-only
Boot process stuck after complaining about SpeedStep
Reboot with Alt+Sys Magic
Recovery Mode
Root FS is checked (ext3)
Root FS is corrupted and I'm informed that the system will reboot
Recovery Mode again
FS are checked
Corruptions are found in /var and /tmp (both are ext3)
Everything is OK !
Long story :
Sunday afternoon, I upgraded my Gutsy server to Hardy. Apart from errors by apparmor (might have been due to gutsy kernel), everything was normal. After some cleanup (old libs, unused apps, checking .conf files, etc) I decide it was safe to reboot and use the new kernel.
Just before the lights went out, I noticed a line about a partition being mounted as read-only.
During the boot process I saw some errors about SpeedStep (might be my old PIII) and then, nothing happened. After a while I used the Alt+Sys magic keys and rebooted.
This time I chose the "recovery mode". The boot process went farther than before and stopped with fsck analyzing the root partition.
Once it was over, it displayed a message saying that a reboot was going to happen.
Again, I chose the recovery mode. And again fsck reappeared to check my other partitions (/tmp and /var). Like the root, they were corrupted and (easily ?) repaired.
Once at the prompt, I ordered the system to complete the boot process and everything started fine.
As far as I know the only thing I've lost is the locate database (a great loss :)
I'm sure you'll need more than this, so please, ask.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https:/