I finally got this to work!
I'm not sure why it work, though. I used the --recheck option on
grub-install since I'd moved drives around. This built the following
device.map:
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/sda
(hd2) /dev/sdb
I edited all the entries in grub.conf to match this, and nothing worked.
I *was* able to get gurb to come up but with no splash screen. I changed
the reference to the splash screen and all the entries for FC5 to say
"(hd1,0)" and the root for Vista to "(hd0,0)". And everything now works.
I also added a line at the top that says "boot /dev/sda"
These device assignments seem backwards to me, though. Does grub swap
the device assignments around because it is installed on /dev/sda?
Also, looking at /var/log/messages (now that I can boot FC5 again!) it
looks like the FC5 kernel recognizes the two IDE drives attached to the
Promise 378 controller as *separate* drives assigned as sda and sdb even
though they're configured as RAID-0. This means I can't really use the
array in Linux, but all I wanted was to be able to boot from it.
Would FC6 or F7 do a better job of recognizing the array?
Regards,
Eric
Eric Mader wrote:
A little more information: the Drive that has FC5 is 40G. (I'ts the
master on IDE0) The RAID array is 240G (i.e. two 120G drives). Could the
problem be that grub can't cope with a drive that's that big? The
command "grub-install /dev/sda" completes without any errors.
The first time I ran the restore CD there was also an external USB drive
connected to the system. Does this show up as a SCSI drive too? As far
as I can tell, the system sees /dev/sda and /dev/sdb, even with the
external drive switched off. How can I tell what the two /dev/sdX
devices are?
Also, FWIW, I booted from the Vista install DVD, chose the repair option
and ran "bootsect /nt60 c:" which also seemed to complete without error
but I still got the grub message instead of the Vista boot loader.
Regards,
Eric
