Small update. After several tests, I found that if I duplicate the encrypted block device configuration line in /etc/crypttab, the upgrade is successful.
I.e., in my case: nvme0n1p3_crypt UUID=c9ffc13a-cad1-49a2-83eb-fb9002b3ebff none luks changes to nvme0n1p3_crypt UUID=c9ffc13a-cad1-49a2-83eb-fb9002b3ebff none luks nvme0n1p3_crypt UUID=c9ffc13a-cad1-49a2-83eb-fb9002b3ebff none luks I haven't tested if simply updating the timestamp on the file also does the trick. Note: if doing this after the upgrade, it requires to re-generate initramfs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1887964 Title: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume group is no longer found. During boot the console shows Volume group "vg01" not found Cannot process volume group vg01 Gave up waiting for suspend/resume device ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell! Attached dist-upgrade logs and console output. Tried the "vgck --updatemetadata vg01" recommended on this bug report: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
