Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #88134

Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade

From Sean Whitton <spwhitton@spwhitton.name>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade
Date 2025-06-25 12:00 +0200
Message-ID <L1v57-d1Wb-1@gated-at.bofh.it> (permalink)
References (6 earlier) <L0533-c7xu-1@gated-at.bofh.it> <L0vJT-coCE-1@gated-at.bofh.it> <L1jwZ-cU4A-1@gated-at.bofh.it> <KZJvz-bTDX-1@gated-at.bofh.it> <L1jwZ-cU4A-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hello,

On Tue 24 Jun 2025 at 11:31pm +02, Bastian Blank wrote:

> On Sun, Jun 22, 2025 at 05:25:07PM +0100, Sean Whitton wrote:
>> > - dpkg -s grub2-common
>>  /etc/kernel/postinst.d/zz-update-grub 5a98abefbfe97dbed36db7899251e433
>>  /etc/kernel/postrm.d/zz-update-grub 5a98abefbfe97dbed36db7899251e433
>
> So at least you now have the correct files.

Well, they're not installed at those paths, only the *.dpkg-dist still.

>> > - ls -alR /etc
>> Hmm, that feels like something of a privacy breach.
>> Could you narrow it down?
>
> This was more fishing for possibly other lost conffiles, aka
> "*.dpkg-dist", or other weird stuff.

Okay.  There is also /etc/cryptsetup-initramfs/conf-hook.dpkg-dist.

>> > - zgrep /etc/kernel /var/log/apt/*
>> This did not produce any useful output:
>
> But this shows that those two scripts where missing for a long time, as
> they don't show up in the run-parts output.  With the default logrotate
> config for term.log (rotate monthly and keep 12) this means it is broken
> since a year.
>
> So all the calls of "update-grub" from the linux maintainer scripts have
> been missing.  But something still created new grub configs or you
> would've never booted 6.12.31.  So either there is something else on
> this system that creates grub configs or someone did it by hand.

(This might be a red herring because this machine has barely been used
over the past year.)

> You could try and see if logs contain traces of "update-grub":
>
> - grep "Found linux image" -B 10 /var/log/ -r
> - journalctl --since=2025-04-01 -g 'Found linux image'

There is exactly one trace: when apt upgraded to grub-efi-amd64 2.12-8:

--8<---------------cut here---------------start------------->8---
Setting up grub-efi-amd64 (2.12-8) ...
[...]
Found linux image: /boot/vmlinuz-6.12.31-amd64
Found initrd image: /boot/initrd.img-6.12.31-amd64
Found linux image: /boot/vmlinuz-6.12.27-amd64
Found initrd image: /boot/initrd.img-6.12.27-amd64
--8<---------------cut here---------------end--------------->8---

In the [...] I got prompted about the new /etc/default/grub.

So it seems like the conffile handling that went on during that
/etc/default/grub change might have gone wrong?

-- 
Sean Whitton

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1108089: grub-efi-amd64,linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Sean Whitton <spwhitton@spwhitton.name> - 2025-06-20 15:00 +0200
  Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Felix Zielcke <fzielcke@z-51.de> - 2025-06-20 15:30 +0200
    Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Sean Whitton <spwhitton@spwhitton.name> - 2025-06-20 16:40 +0200
      Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Felix Zielcke <fzielcke@z-51.de> - 2025-06-20 18:10 +0200
        Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Colin Watson <cjwatson@debian.org> - 2025-06-20 18:20 +0200
        Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Sean Whitton <spwhitton@spwhitton.name> - 2025-06-21 12:40 +0200
        Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Sean Whitton <spwhitton@spwhitton.name> - 2025-06-21 12:40 +0200
          Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Bastian Blank <waldi@debian.org> - 2025-06-21 14:00 +0200
            Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Sean Whitton <spwhitton@spwhitton.name> - 2025-06-22 18:30 +0200
              Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Bastian Blank <waldi@debian.org> - 2025-06-24 23:40 +0200
                Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade Sean Whitton <spwhitton@spwhitton.name> - 2025-06-25 12:00 +0200
  Bug#1108089: marked as done (grub-efi-amd64,linux-image-amd64:  system fails to boot because grub config not updated after latest kernel  upgrade) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-21 12:10 +0200
  Processed: Re: Bug#1108089: grub-efi-amd64, linux-image-amd64:  system fails to boot because grub config not updated after latest kernel  upgrade "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-21 12:40 +0200
  Bug#1108089: marked as done (grub-efi-amd64,linux-image-amd64:  system fails to boot because grub config not updated after latest kernel  upgrade) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-06-21 12:50 +0200

csiph-web