I'm seeing the same behavior. Changing nvme0n1p3_crypt to nvme1n1p3_crypt in /etc/crypttab (in the hope of aligning the naming convention with the underlying NVME device files) and running:
# dmsetup rename nvme0n1p3_crypt nvme1n1p3_crypt # update-initramfs -c -t -k all # update-grub # reboot will flip things around. The NVME device and its partitions will now be nvme0n1pX on the next reboot while the LUKS device will be on nvme1n1p3_crypt. Each time I rename the LUKS device the underlying devices will flip around as well and never end up having the same naming convention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854355 Title: LUKS partition on LVM has wrong device name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854355/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
