Hi, >> Okay, so you're saying that it's okay to set up the partitions >> manually and don't worry about the moving /boot, right? > > If you've previously set up a RAID1 /boot (eg with older Fedora when it > worked fine or by hand) Is this because it used to be the case that /boot was created after cyl 63? >> Is there any support for installing grub on a RAIDed /boot? > > If your /boot is RAID1 then you are ok only if your two volumes are > identically laid out so the map files are identical. At that point grub > is as ever utterly RAID unaware but whichever disk you look at you have a > valid copy of the data in the same place and it just works. Yes, I use the installer to create four 500MB partitions then RAID1 them all together for /boot. As someone else just suggested, I'll now run grub2-install on each of the four raw disks. > It's also > possible to have two totally separate partitions one on each disk and set > each up as if it was a real /boot with its own grub install for the disk > etc. That's a great idea. >> I think I'm confused, but what I'm trying to do is recover from a >> failed /dev/sda that contains the only /boot partition. > > An existing failed /dev/sda or trying to set things up so it will > continue to work if /dev/sda fails ? Ideally, if I reboot it remotely and don't have physical access to the box, I'd like it to attempt to boot from the next disk if sda isn't available. The ability to choose another /boot, or store the MBR on the RAID device instead, would also be a cool option. Thanks, Alex -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
