I can confirm this bug to be present also in lvm2 (2.02.133-1ubuntu10). I got the affected system (upgraded via do-release-upgrade on 09.08.2016) back up with above mentioned workaround:
Creating /etc/initramfs-tools/scripts/local-top/lvm2 script doing "lvm vgchange -ay". And making it executable. Shouldn't this bug get some priority since it possibly makes a remote- system inaccesible ? -- 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
