Public bug reported: LUKS root volume fails to unlock with kernel 7.0.0-28-generic, but works with 7.0.0-27-generic. After upgrading from 7.0.0-27.27 to 7.0.0-28.28, the Plymouth LUKS prompt rejects the correct passphrase with: cryptsetup: ERROR: dm_crypt-0: cryptsetup failed, bad password or options? The same passphrase and the same LUKS2 volume work correctly when booting 7.0.0-27-generic and when opening the volume from an Ubuntu Live system using cryptsetup. I recreated the initramfs for 7.0.0-28-generic: sudo update-initramfs -c -k 7.0.0-28-generic sudo update-grub Both commands completed without errors, but the issue persists. Affected kernel: 7.0.0-28-generic Working kernel: 7.0.0-27-generic LUKS device: /dev/nvme0n1p3 LUKS version: LUKS2 The crypttab UUID matches the actual LUKS UUID. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: gpad 4459 F.... wireplumber /dev/snd/controlC1: gpad 4459 F.... wireplumber /dev/snd/controlC0: gpad 4459 F.... wireplumber /dev/snd/seq: gpad 4436 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 18 12:01:56 2026 InstallationDate: Installed on 2025-08-20 (332 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: SANTECH PCX0DX ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-04 (44 days ago) dmi.bios.date: 05/20/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03TSAS dmi.board.asset.tag: Tag 12345 dmi.board.name: PCX0DX dmi.board.vendor: SANTECH dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SANTECH dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03TSAS:bd05/20/2020:br7.3:efr7.2:svnSANTECH:pnPCX0DX:pvrNotApplicable:rvnSANTECH:rnPCX0DX:rvrNotApplicable:cvnSANTECH:ct10:cvrN/A:skuNotApplicable:pfaNotApplicable: dmi.product.family: Not Applicable dmi.product.name: PCX0DX dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SANTECH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161181 Title: [Regression] LUKS root passphrase rejected on kernel 7.0.0-28, works on 7.0.0-27 Status in linux package in Ubuntu: New Bug description: LUKS root volume fails to unlock with kernel 7.0.0-28-generic, but works with 7.0.0-27-generic. After upgrading from 7.0.0-27.27 to 7.0.0-28.28, the Plymouth LUKS prompt rejects the correct passphrase with: cryptsetup: ERROR: dm_crypt-0: cryptsetup failed, bad password or options? The same passphrase and the same LUKS2 volume work correctly when booting 7.0.0-27-generic and when opening the volume from an Ubuntu Live system using cryptsetup. I recreated the initramfs for 7.0.0-28-generic: sudo update-initramfs -c -k 7.0.0-28-generic sudo update-grub Both commands completed without errors, but the issue persists. Affected kernel: 7.0.0-28-generic Working kernel: 7.0.0-27-generic LUKS device: /dev/nvme0n1p3 LUKS version: LUKS2 The crypttab UUID matches the actual LUKS UUID. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: gpad 4459 F.... wireplumber /dev/snd/controlC1: gpad 4459 F.... wireplumber /dev/snd/controlC0: gpad 4459 F.... wireplumber /dev/snd/seq: gpad 4436 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 18 12:01:56 2026 InstallationDate: Installed on 2025-08-20 (332 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: SANTECH PCX0DX ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-04 (44 days ago) dmi.bios.date: 05/20/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03TSAS dmi.board.asset.tag: Tag 12345 dmi.board.name: PCX0DX dmi.board.vendor: SANTECH dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SANTECH dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03TSAS:bd05/20/2020:br7.3:efr7.2:svnSANTECH:pnPCX0DX:pvrNotApplicable:rvnSANTECH:rnPCX0DX:rvrNotApplicable:cvnSANTECH:ct10:cvrN/A:skuNotApplicable:pfaNotApplicable: dmi.product.family: Not Applicable dmi.product.name: PCX0DX dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: SANTECH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161181/+subscriptions
Комментариев нет:
Отправить комментарий