Was your /boot near full? That's a recurring issue I've had when using the disk encryption like you have. The kernel keeps growing, and if I forget to do apt autoremove after each kernel upgraded, then /boot soon fills up...
post
your explanation of events is confusing to me.
so you rebooted after you clicked on the upgrade button and got left in grub. so you then pressed alt+crtl+del and then it booted normally?
Yes that's right. Me in Gnome software: reboot and apply updates button.
It: Reboots to grub prompt
Me: C-A-delete
It: reboots, this time does normal grub (I have zeroed menu delays so it just gets on) boot, which is evidenced by being asked for luks password.
Me: enters crypt pass
It: reports updating... Gets to 100% reboots. This boot was normal.
Nb. on this instance, after applying the updates, it booted normally and fine. But another time it refused to boot at all after applying updates; I had to use a live CD and reinstall grub and regenerate the initramfs images. This is using LUKS + LVM, with /boot an unencrypted partition + /boot/efi on a separate partition, then the rest is under LUKS + LVM.
I've only generally had problems like this when doing a dist-upgrade or going from stable to testing/unstable and also when the boot/efi partition lives in the middle of the disk vs. beginning. To me, it sounds like you had an ephemeral issue. Maybe your hardware behaves differently under a warm reboot scenario vs. cold boot. If you end up in a grub shell it is likely because it couldn't access something when it needed to.
all 7 comments