Err, it happened again, reduncancy in the system is destroyed,
cryptsetup opened a raid member and it got mounted leaving the raid
incomplet/inactive:
md3 : inactive sda7[0](S)
blkid (now again) returns TYPE="crypto_LUKS" for the raid member.
When I run "su cryptsetup isLuks" on raid members or another (active)
real luks md device "echo $?" returns 0. For a vfat partition"echo $?"
returns 234.
I see this Bug set to invalid for cryptsetup, but as cryptsetup is
determining $cryptsource (devices it waits for to appear) on its own,
and isLuks wrongly reports raid members as being luks, I think this this
is valid cryptsetup bug. (Even if I don't understand what triggers the
raid member to be opened and mounted.
** Changed in: cryptsetup (Ubuntu)
Status: Invalid => New
--
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
