It seems like my problem may have been a different underlying cause with
similar symptoms.
In my case, the entry in /etc/crypttab didn't match the location of the
encrypted partition. Partition is on sda3, but /etc/crypttab read:
sda6_crypt UUID={uuid} none luks,discard
It appears that when
Searching the web I found and wonder if it is related:
https://unix.stackexchange.com/questions/708445/etc-crypttab-not-updating-in-initramfs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
(Correction: previously it asked to decrypt sda3_crypt, not /dev/sda3.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1986623
Title:
cryptsetup fails to decrypt root partion during
Success?
Based only on the error message, I tried defining tmpData in
/etc/crypttab. Previously, the file consisted of one line:
sda6_crypt UUID={uuid} none luks,discard
I added a second line:
tmpData UUID={uuid} none luks,discard
and re-ran update-initramfs. It still produced the other
I'm getting a bit over my head, but it is seeming like there's a problem
with creating a new initrd.
When I decrypt (using unmkinitramfs) the initrd.img file, I see that the
"good" version has a /main/cryptroot/crypttab file which appears
identical to /etc/crypttab. The "bad" version has an
Correction: It is not the kernel itself I was talking about, above.
It's the initrd.img file associated with the kernel.
Note also that replacing that file with the old version eliminates the
problem (at least until some update changes it again).
--
You received this bug notification because
I am able to reproduce the error when I install the new 5.19.0-32
kernel.
Also, when I install the package "Firmware for Linux kernel drivers," it
modifies the files for the older kernels (5.15.0-60 and 5.15.0-43),
making them have the same problem. The 5.15.0-60 file goes from
111,616,247 bytes
Fresh install worked until I did today's recommended updates, then the
problem recurred. Not sure exactly what was updated; I thought
/var/log/dpkg.log was supposed to be human-readable, but mine isn't.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have an Intel Core i5-4590.
Also just tried a fresh install (Ubuntu 22.04) on a spare hard drive,
and it boots fine using kernel 5.15.0-60-generic. Note that spare is a
traditional hard drive and main drive is an SSD; next I'll try
reinstalling on the SSD.
--
You received this bug
The original poster uses an AMD system. My affected system also uses an
AMD (part of /proc/cpunifo attached). What are other affected systems
using?
** Attachment added: "part of cat /proc/cpunifo"
Having the same issue with an existing installation of kubuntu. When
installing a fresh kubuntu on the same hardware (only difference on a
brand new nvme drive) I have the issue after first boot even with that
fresh Kubuntu 22.04.1 LTS. See https://askubuntu.com/q/1454265/1671849
--
You received
Having same issue, just rebooted and now cannot login to the system,
does not accept the password, was working perfectly fine prior to
reboot.
This is on a box that was recently setup with 22.04LTS with ZFS + encryption
via the install options.
Happy to contribute any additional info needed.
having same issue, not clean ubuntu though
5.15.0-43 linux core boots fine, cryptsetup accepts correct password
5.15.0-46 core accepts no password, correct or not
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected jammy
** Description changed:
During boot, cryptsetup fails to decrypt the root partition in a,
seemingly, non-deterministic fashion. I know that the password is
correct and that the keymap is not a fault either, because I have
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Critical
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
16 matches
Mail list logo
