[Bug 531240] Re: breaking raid: root raid_member opened as luks

[ceg]

My current conception: (WARNING)

Both blkid and "cryptsetup isLuks" misreport a raid_member as luks when
checking devices, but blkid correctly reports RAID if the device is set
up (mounted/active) in the system as intended (after
install/update/recover).

On boot what happens depends on the order in which the partitions show up.
In my case boot works ok once or twice before one raid member gets luksOpen'ed directly while the other remains an inactive spare.

This is at least present in all systems that use luks on top of raid
devices. And in those cases is very problematic because on booting
individual raid members get mounted randomly, possibly in between raid
resyncs, leading to raid desyncing and false automatic (rollback)
recoveries with data loss.

Because ubuntu ships a raid monitoring support that was broken, no
notification about raid status changes are shown to users/admins.
#535417

-- 
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to util-linux in ubuntu.