search for: initramdr

...> > So: > 1. *Is* there space for grub2 to install the bootloader under where the > mdadm starts? To the best of my knowledge: no. To have mdadm started (md devices created) you already need kernel loaded, at this stage you don't have it, you will have it in memory after you load initramdrive, so initramdrive is useless on md devices which do not exist yet at the moment you load initramdrive. > Or do I have to partition the disks (/dev/sda1 100%, ditto > /dev/sdb1, then > create the RAID 1 with the partitions, and *then* grub2-install? Not necessarily, you...

Let me see if I can, um, reboot this thread.... I made a RAID 1 of two raw disks, /dev/sda and /dev/sdb, *not* /dev/sdax /dev/sdbx. Then I installed CentOS 7 on the RAID, with /boot, /, and swap being partitions on the RAID. My problem is that grub2-install absolutely and resolutely refuses to install on /dev/sda or /dev/sdb. I've currently got it up in a half-assed rescue mode, and have

So, it installed happily. Then wouldn't boot. No problem, I'll bring it up with pxe, then chroot and grub2-install. Um, nope. I edited the device map from hd0 and hd1 being the RAID to /dev/sda and /dev/sdb, then ran grup2-install. It now tells me can't identify the filesystem on hd0, and can't perform a safety check, and gives up. What am I missing? Google is not giving me any