Public bug reported:
Binary package hint: util-linux
I noticed /proc/mdstat reported the root raid as inactive (although the
system seemed to run fine!).
Looking further it seemed like during boot the system has unlocked and mounted
the rootfs using (only) one raid_member located on an external usb disk
directly. ("dmsetup deps" pointed to it for mdX_crypt)
I guess since the usb raid_member was busy then, the system was not able to
start the raid, and so it remained inactive.
Which part of the system is involved in setting up the root and could
have messed things up here?
Calling "sudo blkid" reported what actually is an USB
"linux_raid_member" as TYPE="crypto_LUKS".
I found the following in the util-linux changelog:
* Always return encrypted block devices as the first detected encryption
system (ie. LUKS, since that's the only one) rather than probing for
additional metadata and returning an ambivalent result. LP: #428435.
might that cause the precedence of reporing luks over raid_member for the usb
disk?
I did not notice this happening with non-usb disks, and also it did not
happen at first. (might happen related to a recent update or when the
mountall/cryptsetup times out?) How to get more details?
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
blkid reports root raid_member (on usb) as luks, which is booted while raid
remains "inactive"
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
