*** This bug is a duplicate of bug 133765 *** https://bugs.launchpad.net/bugs/133765
I had a very similar problem, although I think I was able to resolve it more completely. I saw this on two of my three systems. Both affected systems were x86 (one SATA one PATA) which were originally installed from the Kubuntu Dapper Drake alternate installation CD. I upgraded them to edgy when it came out. After Gutsy came out I upgraded to Feisty (no problems) and then Gutsy. In my case the boot problem happened after the real root filesystem was mounted. The hang appeared to be the evms startup code repeatedly probing my CD-ROM for startable md devices. I did get a console, but I couldn't do much with it because my /usr is a separate filesystem. It was easier to boot the feisty kernel, modify /etc/evms.conf to disable all devices (exclude = [ * ] in a couple of places) and then reboot, at which point the gutsy kernel came up fine. Putting a valid CD into the CD-ROM drive might also have worked, but I didn't try that. Also note that all three of my gutsy upgrades failed because smartmontools failed after it was upgraded. I opened a separate bug on this issue -- but this means that I ended up completing the installation manually with dpkg-reconfigure and apt-get dist-upgrade. My third system (which did not experience the evms.conf problem) was an x86_64 system, and may have been installed from the DVD image instead of the alternate install CD. This system has no /etc/evms.conf at all and never encountered this particular problem. -- System fails to boot after upgrading to gutsy https://bugs.launchpad.net/bugs/151814 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs