-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi David: Um, I'm sure you already checked this but just in case: your BIOS couldn't still be booting from the RAID, could it? If so, then GRUB is looking at the /boot/grub stuff on the RAID rather than what's on your new IDE boot drive... Cheers, - Darrell On Monday 16 February 2004 00:02, David Liontooth wrote:
Greetings --
I just moved my SuSE 9 from a RAID volume to an IDE drive, using cp -a as Andrew adviced; this worked fine.
I modified /boot/grub/menu.lst to load the new IDE /boot and /root partitions. So far so good -- everything is working fine.
Then the anomaly: I boot into the original RAID volume and issue
grub-install /dev/hda
I get this receipt:
(fd0) /dev/fd0 (hd0) /dev/hda (hd1) /dev/hdc (hd2) /dev/sda (hd3) /dev/sdb
Then I boot into the new IDE drive and issue the same "grub-install /dev/hda" and get the same values (except no floppy):
(hd0) /dev/hda (hd1) /dev/hdc (hd2) /dev/sda (hd3) /dev/sdb
I edit menu.lst to reflect these values and reboot.
Misery: grub doesn't find the menu, and boots into the grub shell. I query,
geometry (hd0)
and get the first RAID volume. The values are in effect as follows:
(hd0) /dev/sda (hd1) /dev/sdb (hd2) /dev/hda (hd3) /dev/hdc
And grub sticks to its guns. There seems to be no way to convince it to change its device map, in spite of what it claims to be doing once the OS is booted.
How can I overwrite the device map that grub actually uses? Issuing grub-install seems to just create device maps that are not used, and grub takes on multiple personalities.
Cheers, David
- -- sused@mucus.com "Perfect! ....what am I doing?" -- Washu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQFAMQuheo6c0kw6mZ0RAnaFAKDwT77OZCMugTLJsHW7WB3Rl4kzYACeKdyB IJbefR0Rt0vVJVx34fVQd6Y= =4D3f -----END PGP SIGNATURE-----