The apparent cause seems to be lvm2 (2.02.133-1ubuntu8). From the
Changelog (https://launchpad.net/ubuntu/xenial/+source/lvm2/+changelog)
lvm2 (2.02.133-1ubuntu8) xenial; urgency=medium
* Drop debian/85-lvm2.rules. This is redundant now, VGs are already
auto-assembled via lvmetad and 69-lvm-metad.rules. This gets rid of using
watershed, which causes deadlocks due to blocking udev rule processing.
(LP: #1560710)
* debian/rules: Put back initramfs-tools script to ensure that the root and
resume devices are activated (lvmetad is not yet running in the initrd).
* debian/rules: Put back activation systemd generator, to assemble LVs in
case the admin disabled lvmetad.
* Make debian/initramfs-tools/lvm2/scripts/init-premount/lvm2 executable and
remove spurious chmod +x Ubuntu delta in debian/rules.
-- Martin Pitt <[email protected]> Wed, 30 Mar 2016 10:56:49
+0200
The initramfs-tools script does not activate all of the logical volumes and its
detection is lacking in certain edge cases like mine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573982
Title:
LVM boot problem - volumes not activated after upgrade to Xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
