It looks like currently most OS installers insist on putting /boot on a non-RAID partition (or the kind of RAID1 partition that "looks like" a non-RAID partition), even the installers that support RAID5 and GRUB2.
I'm guessing this limitation is a historical relic leftover from Grub1. My understanding is that Grub1 doesn't know anything about RAID and so can't boot off any kind of RAID array -- except for RAID arrays that "look like" a non-RAID array.
Is this a limitation of Grub2, or of the OS installers?
I've heard rumors that Grub2 is "able to support /boot on RAID-0, RAID-1 or RAID-5, metadata 0.90, 1.0, 1.1 or 1.2".
Does Grub2 really support putting /boot on a software RAID1 partition with 1.2 metadata?
Does Grub2 really support putting /boot on a software RAID5 partition?
An ideal answer would link to a tutorial that explains how to move a /boot partition (on a non-RAID partition) to a RAID5 partition.
By "looks like" a non-RAID partition, I mean either
- when Grub1 reads only one hard drive of a software RAID1 array with a ext3 or ext4 filesystem and ignores the RAID metadata 0.90 or 1.0 at the end of the partition, it looks just like the a non-RAID ext2 file system that Grub1 can handle. Or
- Not a software or fake-RAID, but a full hardware raid that looks like a normal non-RAID disk.