On a laptop running Debian Trixie (13), the software center offered some upgrades with a "reboot and upgrade" button.

When it rebooted, I was left in a grub shell.

Ctrl-Alt-Delete caused a normal boot: I was asked for my LUKS passphrase, and then it applied the updates, then it rebooted fine.

But why would it reboot to a grub shell?

all 7 comments

sorted by: hot top controversial new old
[–] 2 points 4 days ago (1 child)

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...

  • source
  • hideshow 1 child comment
  • [–] 1 point 4 days ago (1 child)

    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?

  • source
  • hideshow 1 child comment
  • [–] [S] 1 point 4 days ago

    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.

  • source
  • parent
  • [–] [S] 1 point 4 days ago (2 children)

    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.

  • source
  • hideshow 2 child comments
  • [–] 2 points 4 days ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 1 point 4 days ago

    Efi is 2nd partition (I have 1st is /boot, ext4 then EFI, vfat, then Luks (lvm (swap, root)))

    Does that really affect anything?!

    It's happened twice, but can't test it again until another update is published!

  • source
  • parent