Thank you for the suggestion. I ran grub-install /dev/sda and rebooted, but encountered the same hang. I don't have a "grub-setup" program on either of my systems. I was reviewing man pages for grub and did not see additional items/params to use. I'm out of my experience again with grub, as I have never had to manually use it before, so I could easily miss something needed. Is there something more to do to configure MBR with the new drive? I also looked at menu.lst, and all paths use the LV name except "splashimage=" and "root", which use hd(0,0), so I am not sure what to change there. I just noticed the "setup" subcommand of the grub CLI. Perhaps this is what you meant? Possibly this info will help - this is the /dev items and changes I did that caused this mess: - sda1 is /boot. fdisk still shows it as the only one marked bootable. - sda2, sdb1, sdc1, sdd1 are/were in LV. - sdd1 is the new drive. - sdb1 and sdc1 are the two drives I moved PEs to sdd1, and removed them from the LV. -----Original Message----- From: tclug-list-bounces at mn-linux.org [mailto:tclug-list-bounces at mn-linux.org] On Behalf Of Tony Yarusso Sent: Sunday, December 13, 2009 10:16 PM To: tclug-list Subject: Re: [tclug-list] LVM correction help My suspicion is that it's actually the bootloader that's messed up rather than the logical volumes themselves. (most likely) Grub is configured to point to the old drive, and doesn't find anything there. So what you'll need to do if that's the case is to use grub-setup/grub-install to update the Master Boot Record to know about your new drive, and then possibly the menu.lst to know that the system itself moved too if it doesn't figure that out automatically. - Tony Yarusso _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota tclug-list at mn-linux.org http://mailman.mn-linux.org/mailman/listinfo/tclug-list