> > So... why, then, does the Redhat install default to grub, when I am > doing a bootable software raid install? Seems a bit silly to load up a > system that won't work... with no suggestions etc on how to fix it. >
Well, I guess that might be a bug, open a bug in RedHat's Bugzilla, you might get a free T-shirt out of it. But I think that their answer will be that software RAID is intended to be used as a protection against data loss and unscheduled downtime from disk sector failures during runtime, I don't think that software RAID can be used *reliably* for resiliency at boot time because an IDE disk could fail in such a way that the PC BIOS detects the 1st bootable hard disk as present, and having a valid boot sector, but that cannot finish the full boot sequence. For example, let's say that the Head movement arm mechanism breaks so that the upper cylinder range is unreachable, but the MBR, and the /boot partition are reachable while the / partition is not. The PC BIOS would start the boot, the kernel would load and then panic because even though it could find the initrd image it couldn't read the /etc/raidtab file. Having LILO or GRUB installed on both drives is not a guarantee, it will only work in some limited circumstances. Maybe RedHat doesn't offer to set up your box that way is because they don't want to set false expectations that won't be lived up to. If you really want that type of redundancy you may have to go with a hardware RAID solution. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
