So you'd have to go out of your way to provide a custom mdadm.conf everytime you run mkinitcpio (and then hope the udev rules run a 2nd time?). Or just customize the hook altogether.
Is it worth it, though? What's the issue with assembling the raid1 early?
]]>I only added to mkinitcpio.conf: MODULES=(md_mod raid456)
because the boot partition is not needed during boot.
However, the missing module raid1 causes during initramfs:
md: personality for level 1 is not loaded!
and leaves a faulty /dev/md127 md device. It prevents the assembly at the later stage, when the raid1 module becomes available. So to assemble it I have to stop it first:
mdadm --stop /dev/md127
mdadm --assemble --scan
Is adding raid1 to mkinitcpio.conf the only solution? Or can I somehow make mdraid ignore this array in initramfs?
For instance, use --homehost=noautoassembly and then add this array explicitly to /etc/mdadm.conf
]]>