Les Mikesell wrote: > On Sun, Mar 10, 2013 at 10:45 PM, Frank Cox <theatre at melvilletheatre.com> > wrote: >> >> The most maddening part of this is that all of the files and the >> filesystems appear to be present -- I can boot off of a rescue CD and mount the >> whole works under /mnt/sysimage and browse to my hearts content. I just can't boot >> the damn thing. >> >> How is a name like /dev/mapper/vg_ws195-lv_root rd_NO_LUKS determined? >> If I knew how to read or find out what the actual name of the root directory >> was on the problem machines, I could compare it to what's in the grub.conf >> file. > > I don't have any idea how to debug LVM stuff. But if you can boot in > rescue mode just on general principles I would chroot into > /mnt/sysimage, rebuild the initrd and reinstall grub. rd_NO_LUKS says that there are no encrypted filesystems. We *strongly* prefer to label our filesystems. Finally, if you can see it running via linux rescue, I'd go with Les' thought: boot that way, chroot to /mnt/sysimage, and first do a grub-install. If that doesn't solve it, then try the rebuild of initrd. Oh, and check /mnt/sysimage/etc/fstab mark