In the Debian world, I know how to create an mdadm array, format the file system and mount it. I was doing the same in Antergos while following the Arch wiki and things sort of went off the rails when I got towards the end.
In Debian, to save the array layout, you use: sudo update-initramfs -u
In Antergos/Arch, I guess that step is replaced with mkinitcpio and that mdadm-udev hook. When I got to that spot in the arch Wiki, the commands I was asked to type gave me bash errors so I manually edited the mdadm.conf file and added:
ARRAY /dev/md0 metadata=1.2 name=gene-antergos:0 UUID=0078e14e:6ce6b00e:598d3151:beeb6694
then edited fstab.conf and added:
/dev/md0 /mnt/md0 ext4 defaults,nofail,discard 0 0
My array is mounted at every boot and appears to be running AOK but since I didn’t do anything with mkinitcpio, did I miss some crucial step?
That wiki ( https://wiki.archlinux.org/index.php/RAID#Update_configuration_file ) is easy enough to follow but after the steps about creating the array, it jumps to installing Arch ONTO the array. To a newbie, it seems to go sideways when telling you what to do after the array is created and what you need to do to save the layout.
Looking at the mkinitcpio wiki ( https://wiki.archlinux.org/index.php/mkinitcpio#Installation ) , do I just issue the following command: mkinitcpio -c /etc/mkinitcpio-custom.conf -g /boot/linux-custom.img
… and add that mdadm_udev hook?
Or, since I have the array mounting at boot, is everything “OK” and even though I didn’t use mkinitcpio, just leave it alone?