Comment 10 for bug 1825011

I see now, you're attempting to mirror /boot/efi; that's not a support configuration. The general issues are:

1) Firmware that handles EFI does not expect these partitions to be under raid.
2) The raid format may obfuscate the devices from the firmware (it won't see the devices)
3) Given that firmware doesn't know about raid, one needs two entries to handle the case that
either device is bad
4) There are sync issues, in the case that the firmware updates the EFI partition, this data may be lost due to linux raid syncing over the "bad" data on the other disk.

The efibootmgr output looks strange for the target devices:

......A.........................T.H.N.S.F.8.8.0.0.C.A.M.E.................................................................................. ......A.........................T.H.N.S.F.8.8.0.0.C.A.M.E...

This may be related to the raid on the devices, but could also just be something else between firmware and those disks.