Comment 8 for bug 139337

My Fiesty->Gutsy Upgrade wouldn't let me back in after the screensaver kicked in. I had to hard shutdown my machine. Here's an email I just sent to some of my friends (the irony that I've all typed up for you already. LOL)

   1. I booted with the Xubuntu 7.10 alternate CD started rescue mode. No sense going back.
   2. I chose my / partition for the shell and manually mounted all my Logical Disks to there respective mount points (/usr, so forth.) which used /dev/mapper/vg_pool-lv_usr convention
   3. I ran `apt-get upgrade` which after a while told me to run ` dpkg --configure -a`. That completed the Upgrade.
   4. When it rebooted, it still gave me the error about not finding or cannot e2fsck the LVM devices
   5. I checked the /etc/fstab which had them as /dev/mapper/vg_pool-lv_usr (and so forth). When I `ls /dev/mapper` their names had changed to /dev/mapper/lvm2|vg_pool|lv_usr (dashes were now vertical pipes with an extra bit of stuff in the front. What the ??? )
   6. Backed up my fstab and made the corrections with nano editor (no vi available)
   7. It's alive. ... Well, mostly. I have to manually drop back a kernel version to my old version. I guess I still need to do that upgrade from 2.6.16 to 2.6.20. Hopefully, I won't kill it again. I'll be doing it in single user mode.

   So apparently, there was some changes to LVM from the "volume groups - logical volumes" to "disk mgmt | vg | lv". That makes sense so enterprise and other folks can start mixing legacy and future LVM revisions.

UPDATE: I booted the machine with the previous kernel 2.6.16, did an `init 1` for single user. I then re-ran `apt-get upgrade` followed by ` dpkg --configure -a` again. Guess there was some more configuring to do. At the very end it generated the /boot/initrd.img-2.6.22-14-generic. Now I can boot just fine. Now I need to figure out why my X.org is consuming 100% - 135% utilization on my dual core.

Hope this helps you out. Mark S.