I'm having some issues with the Grub configuration files being written
out by drakboot which seem to be caused by my FakeRAID and was wondering
if anyone else had gone through this.
My setup:
* Five SATA HDDs: sda, sdb, sdc, sdd, sde
* The boot device is sda
* My Mageia install's root partition is sdc5
* sdd and sde are FakeRAIDed with the onboard ICH9 controller and show
up as mapper/isw_jbhbdjgei_Data
/boot/grub/device.map gets written out like this:
(hd0) /dev/sda
(hd1) /dev/mapper/isw_jbhbdjgei_Data
(hd2) /dev/sdb
(hd3) /dev/sdc
So everything pertaining to sdc in Grub configs uses hd3. However, when
booting, Grub doesn't recognize the FakeRAID device and can't find
anything that it's looking for on hd3 (it considers sdc to be hd2).
I am currently working around this by removing the generated hd1 from
device.map, renumbering everything accordingly in device.map and
menu.lst, and re-running grub-install /dev/sda after each time something
messes with it (e.g., running drakboot or a new kernel gets installed).
I guess the real quesiton is how /should/ the Mageia bootloader code be
handling this sort of situation?
Thanks,
-Michael
