On Tue, Sep 09, 2003 at 02:37:18PM -0400, Cress, Andrew R wrote: > The instructions are oriented to lilo, but the grub equivalent is > scripted in files/mdevt script: > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/scsirastools/s > csirastools/files/mdevt?rev=HEAD&content-type=text/plain A word of caution: One miserable consequence of using GRUB on RAID1 is inadvertent corruption of (a small part of the) RAID-1 /boot partition. Since grub (at least in Red Hat Rawhide) doesn't grok MD, if one sets up a RAID-1 /boot partitiion, say /dev/md1 -> (/dev/sda1,dev/sdb1), then modifications made at the grub prompt modify the filesystem and desynchronizes the RAID1 set. [It seems that simply using 'e' to edit the kernel args has this effect, though I haven't verified it myself.] We see this corruption in MD5 variation in our nightly integrity-verification cron job. Grub has a --read-only option when running the grub shell from Linux; I haven't yet found the time to delve into the code to see whether it is simple to do the same in the stage2 loader, or whether the read-only behavior is purely a function of the device open() when running the grub shell. Trivial workaround is to resync the second drive in the rc scripts; for the typical 50-100MB /boot partition, this takes only a few seconds. Regards, Bill Rugolsky - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
