I had this problem today when I upgraded an old Redhat 9 system. This was already using LVM for all the file systems except /boot. I wanted to keep as much of my data file systems but have a clean Ubuntu server install so just reformatted the main install locations (/ /var /tmp /usr) but left everything in lvm as this was recognized by Ubuntu installer and would requiring changing the partitioning.
When I rebooted the startup hung and eventually I was dropped into the debian busybox (first time for me to see that so I wasn't sure what was going on). Anyway, did some net search and found this bug report and some others elsewhere. Not wanting to do any major changes to the system if possible, I booted into recovery off the CD and mounted the root (and noted that recovery was able to load the LVMs fine just as the installer had been). As given by the previous poster, I investigated vgconvert and then examined the volume meta data version (either vgdisplay, pvscan) and saw this was the old version 1. To convert to version 2 on my three volume groups, I did: vgconvert -M2 vg01 vg02 vg03 This was the *ONLY* thing I did so I know this is what fixed the problem. I now do not need to do the manual interventions given above. I'm guessing that the boot-time volume manager in Feisty only is recognizing LVM version 2 VGs for some reason. -- [feisty] mounting LVM root broken https://bugs.launchpad.net/bugs/83832 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
