I’m always trying to install FCOS in a full raid1 configuration on a Bare metal system.
I’ll try to be as clear as possible on my actual progress
Booting from live usb iso
Added new user / added user to sudo group and allow sshd password login for better access via ssh (optional )
Create a raid array on full device sudo mdadm --create /dev/md127 --level=1 --metadata=0.90 --raid-devices=2 /dev/sda /dev/sdb
run sudo coreos-installer install /dev/md127 --ignition /tmp/config.ign
run manually that is done after first reboot : growpart /dev/md127 4
mount 4th partition (/root) in /tmp/md4 and run : sudo xfs_growfs /tmp/md4
mount 1st partition (/boot) in /tmp/md1 and update /tmp/md1/grub2/grub.cfg by adding in top of file : ok, it’s hardcoded, will try to list all boot labeled devices an choose one with priority on raid later …
insmod mdraid1x
insmod mdraid09
set pager=1
search --label boot --set boot
#set root=$boot
set root=(md/md127,gpt1)
create /tmp/md4/ostree/deploy/fedora-coreos/deploy/{some very long ID :p}/etc/mdadm.conf with the result of sudo mdadm --detail --scan
A this point everything looks right but FCOS still booting on 1 drive, e.g. /dev/sda and mdmonitor.service return me an error …
Can you help me to “hack” the end of the process please ?
I need help to tell (as my knowledge is not enough) initramfs ? dracut ? something else ? how to find and use md127p4 as root … it’s just here, already used by grub … So near and yet so far !
I’m not an expert at all but if I well understand thinks, you should handle some ignitions parts like raid in coreos-installer and not after some kind of “hardware” decision like partitioning by running ignition after hdd setup is done …
I think the problem is probably that your /etc/mdadm.conf isn’t in the initramfs. You might have to add some kernel args to make the raid array get assembled early on. AFAIK we haven’t paved this path just yet so (as you know) you’re operating a bit blind .
Right. It looks like he is doing a raid1 on the entire disk (not just for the root filesystem), though. I don’t know if we have any plans to address that, do we?
Just come back to my installation process, but in a different way …
I have a spare PC so i decide to install FCOS on it, via pxe, on one hdd, everything is ok for that…
But my question stay actual
On the PC with raid1 Hdd, I want to run a “diskless” pxe FCOS with this ignition file :
now my concern is about Raid1 on entire disk, it looks like FCOS try to create partitions on “/dev/md/MediaRaid” before creating “/dev/md/MediaRaid” raid device … and fail booting with error :
I don’t remember exactly how I did it, but, for the first boot you can remove --assume-clean and UUID mdadm options and wait for the full build of the raid array
–assume-clean is to prevent the full process of check/build/rebuild/ … at each reboot (remember I’m on a diskless (live PXE) environment)
–UUID … ?? … perhaps because a new uuid was set after reboots, can’t say ^^
Perhaps you will have to change wipe_filesystem to true for the initialization … can’t remember