New observation: When booting the alternate CD into rescue-mode in a luks on raid system, it asks passphrases for the raid members instead of the md device.
Problem: cryptsetup (not beeing udev but boot script driven, and looking for luks headers on its own?) really needs to be hooked into the event driven startup properly.
The md devices may most of the time get up quickly enough so that the member devices are in use when cryptsetup wants to grab them. But ol'cryptsetup will grab luks on raid members, if mds are not set up at all or a member got marked faulty.
Don't know if blkid is reporting raid_members as luks only after cryptsetup opened them or already before.
New observation: When booting the alternate CD into rescue-mode in a luks on raid system, it asks passphrases for the raid members instead of the md device.
Problem: cryptsetup (not beeing udev but boot script driven, and looking for luks headers on its own?) really needs to be hooked into the event driven startup properly.
The md devices may most of the time get up quickly enough so that the member devices are in use when cryptsetup wants to grab them. But ol'cryptsetup will grab luks on raid members, if mds are not set up at all or a member got marked faulty.
Don't know if blkid is reporting raid_members as luks only after cryptsetup opened them or already before.