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
wi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
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/bug
I have changed the title of this bug as I have encountered the same
issue on a laptop that only has a single disk so a system having more
than one disk isn't causing this issue.
Details of the other machine
Ubuntu release: Ubuntu Desktop 18.04.2 LTS
Kernel: 5.3.0-26-generic
Storage devices: 2TB H
** Summary changed:
- LUKS partition on LVM with two disks has wrong device name
+ LUKS partition on LVM has wrong device name
--
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/18
4 matches
Mail list logo