[Touch-packages] [Bug 1854355] Re: LUKS partition on LVM has wrong device name

2020-05-18 Thread Thomas Bouve
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

[Touch-packages] [Bug 1854355] Re: LUKS partition on LVM has wrong device name

2020-05-18 Thread Launchpad Bug Tracker
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.

[Touch-packages] [Bug 1854355] Re: LUKS partition on LVM has wrong device name

2020-01-29 Thread Gutsy Li
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

[Touch-packages] [Bug 1854355] Re: LUKS partition on LVM has wrong device name

2020-01-29 Thread Gutsy Li
** 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.