Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #66097
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl |
| Date | 2020-01-15 21:30 +0100 |
| Message-ID | <zoXsC-6PP-15@gated-at.bofh.it> (permalink) |
| References | <zoCHv-2Pr-3@gated-at.bofh.it> <zoCHv-2Pr-3@gated-at.bofh.it> <zoMnw-fl-15@gated-at.bofh.it> <zoCHv-2Pr-3@gated-at.bofh.it> <zoMnw-fl-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hi Luc, On Wed, Jan 15, 2020 at 09:22:05AM +0100, Luc Maisonobe wrote: > Here are some additional informations about the problem. > > I rechecked it was not a keyboard layout problem by setting up > an additional luks key, a very short one that used only keys that > were at the same position in both qwerty and azerty. It does > not work, so it's definitely not a keyboard problem. > > The error I get on boot is as follows: > > Caching passphrase for sdb1_crypt:*********************** > [ 15.212421] device-mapper: table: 253:0: crypt: Error allocating > crypto tfm > device-mapper: reload ioctl on failed: No such file or directory > cryptsetup: ERROR: sdb1_crypt: cryptsetup failed, bad password or options? > > Caching passphrase for sdb1_crypt: > > I tried to use a key file instead of a key typed by user just > like I did on the other laptop. I do not want to use this method > for this specific machine for security reasons (it should not be > abel to boot unattended), but tried it temporarily. I regenerated > the initramfs after changing the /etc/crypttab file, but it didn't > work either. When generating initramfs, I got the following warning, > so it may explain why it didn't work. > > cryptsetup: WARNING: Skipping root target sdb1_crypt: uses a key file > > In this case (booting with a key file), the error was different: > > Volume group "vg-ssd" not found > Cannot process volume group vg-ssd > Volume group "vg-hdd" not found > Cannot process volume group vg-hdd > Volume group "vg-hdd" not found > Cannot process volume group vg-hdd > Volume group "vg-hdd" not found > ... > Cannot process volume group vg-hdd > Volume group "vg-hdd" not found > Cannot process volume group vg-hdd > mdadm: error opening /dev/md?*: No such file or directory > Cannot process volume group vg-hdd > Volume group "vg-hdd" not found > > then the boot process drops to initramfs shell. Exploring the filesystem > at this stage, I didn't find the key file. Your issue sounds like #948593. In case yes, we should reassign and merge it with that bug. Regards, Salvatore
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl Luc Maisonobe <luc@apache.org> - 2020-01-14 23:20 +0100
Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl Luc Maisonobe <luc@spaceroots.org> - 2020-01-15 09:40 +0100
Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl Salvatore Bonaccorso <carnil@debian.org> - 2020-01-15 21:30 +0100
Bug#948921: linux-image-5.4.0-2-amd64: decrypting root partition does not work on 5.4.0 (works on 5.3.0) with decrypt_keyctl luc <luc@spaceroots.org> - 2020-01-16 09:30 +0100
csiph-web