Re: linux-image-4.9.0-12-amd64 breaks LUKS root

[David Christensen <dpchrist@holgerdanske.com>]

On 2020-03-14 23:14, David Christensen wrote:
> debian-user:
>
> I have Debian machine:
>
>          2020-03-14 22:57:21 root@po ~
>          # cat /etc/debian_version ; uname -a
>          9.12
>          Linux po 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2 
> (2019-11-11) x86_
> 64 GNU/Linux
>
>
> When I install linux-image-4.9.0-12-amd64:
>
> 2020-03-14 22:58:13 root@po ~
> # time apt-get dist-upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following NEW packages will be installed:
>    linux-image-4.9.0-12-amd64
> The following packages will be upgraded:
>    linux-image-amd64
> 1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 39.3 MB of archives.
> After this operation, 193 MB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://ftp.us.debian.org/debian stretch/main amd64 
> linux-image-4.9.0-12-amd64 amd64 4.9.210-1 [39.3 MB]
> Get:2 http://ftp.us.debian.org/debian stretch/main amd64 
> linux-image-amd64 amd64 4.9+80+deb9u10 [7158 B]
> Fetched 39.3 MB in 12s (3074 kB/s)
> Reading changelogs... Done
> Selecting previously unselected package linux-image-4.9.0-12-amd64.
> (Reading database ... 106060 files and directories currently installed.)
> Preparing to unpack .../linux-image-4.9.0-12-amd64_4.9.210-1_amd64.deb ...
> Unpacking linux-image-4.9.0-12-amd64 (4.9.210-1) ...
> Preparing to unpack .../linux-image-amd64_4.9+80+deb9u10_amd64.deb ...
> Unpacking linux-image-amd64 (4.9+80+deb9u10) over (4.9+80+deb9u9) ...
> Setting up linux-image-4.9.0-12-amd64 (4.9.210-1) ...
> I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.9.0-11-amd64
> I: /initrd.img.old is now a symlink to boot/initrd.img-4.9.0-11-amd64
> I: /vmlinuz is now a symlink to boot/vmlinuz-4.9.0-12-amd64
> I: /initrd.img is now a symlink to boot/initrd.img-4.9.0-12-amd64
> /etc/kernel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-4.9.0-12-amd64
> cryptsetup: WARNING: target sda2_crypt has a random key, skipped
> /etc/kernel/postinst.d/zz-update-grub:
> Generating grub configuration file ...
> Found background image: .background_cache.png
> Found linux image: /boot/vmlinuz-4.9.0-12-amd64
> Found initrd image: /boot/initrd.img-4.9.0-12-amd64
> Found linux image: /boot/vmlinuz-4.9.0-11-amd64
> Found initrd image: /boot/initrd.img-4.9.0-11-amd64
> Found linux image: /boot/vmlinuz-4.9.0-9-amd64
> Found initrd image: /boot/initrd.img-4.9.0-9-amd64
> done
> Setting up linux-image-amd64 (4.9+80+deb9u10) ...
>
> real    0m34.738s
> user    0m9.616s
> sys    0m3.132s
>
>
> And then reboot, it refuses to accept the (correct) LUKS passphrase:
>
> <snip>
> Please unlock disk /dev/disk/by-partuuid/xxxxxxxx-xx (sda3_crypt):
> cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
> Please unlock disk /dev/disk/by-partuuid/xxxxxxxx-xx (sda3_crypt):
> cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
> Please unlock disk /dev/disk/by-partuuid/xxxxxxxx-xx (sda3_crypt):
> cryptsetup (sda3_crypt) : unknown fstype, bad password or options?
> cryptsetup (sda3_crypt) : maximum number of tries exceeded
> cryptsetup: going to sleep for 60 seconds...

I re-imaged that machine and let it run for the past two week.  When I 
upgraded the kernel against today, it failed in the same manner.


Any suggestions?


David