I'd suggest to make "cryptsetup isLuks" check with blikid prior to probing the luks header (and have it report errors), as the next step in finding/fixing the root cause and reestablishing trust in using luks on raid.
-- silently breaking raid: root raid_members opened as luks https://bugs.launchpad.net/bugs/531240 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
