The UUID of the filesystem created on a raid mirror is of course present and identical on any member devices of the raid mirror mirror.
The raid member device (superblocks) are probably also all taged with (another) UUID of the raid device they assemble, plus the device ID. Mdadm seems to handle that correctly, its something else that wants to mount the filesystem directly from a member device instead of (waiting for) the raid device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/531240 Title: silently breaking raid: root raid_members opened as luks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
