Your message dated Sat, 21 Jun 2025 11:52:18 +0200 with message-id <20250621095218.escprapzhya4ukyw@shell.thinkmo.de> and subject line Re: Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade has caused the Debian Bug report #1108089, regarding grub-efi-amd64,linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1108089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108089 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: 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>
- Date: Fri, 20 Jun 2025 13:49:18 +0100
- Message-id: <[🔎] aFVYzrDZZqlO6p7Z@zephyr.silentflame.com>
Package: grub-efi-amd64,linux-image-amd64 Severity: important Dear maintainers, I had kernel 6.12.27 running. I just upgraded to kernel 6.12.32. My system then did not boot by itself because the grub config still contained entries for 6.12.31, which had been autoremoved. I could recover by booting the old 6.12.27 and then doing a manual 'update-grub'. I see this in my /var/log/apt/term.log: Log started: 2025-06-20 13:29:34 (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 618410 files and directories currently installed.) Preparing to unpack .../initramfs-tools_0.148.2_all.deb ... Unpacking initramfs-tools (0.148.2) over (0.147) ... Preparing to unpack .../initramfs-tools-core_0.148.2_all.deb ... Unpacking initramfs-tools-core (0.148.2) over (0.147) ... Selecting previously unselected package initramfs-tools-bin. Preparing to unpack .../initramfs-tools-bin_0.148.2_amd64.deb ... Unpacking initramfs-tools-bin (0.148.2) ... Selecting previously unselected package linux-image-6.12.32-amd64. Preparing to unpack .../linux-image-6.12.32-amd64_6.12.32-1_amd64.deb ... Unpacking linux-image-6.12.32-amd64 (6.12.32-1) ... Preparing to unpack .../linux-image-amd64_6.12.32-1_amd64.deb ... Unpacking linux-image-amd64 (6.12.32-1) over (6.12.31-1) ... Setting up initramfs-tools-bin (0.148.2) ... Setting up initramfs-tools-core (0.148.2) ... Setting up initramfs-tools (0.148.2) ... update-initramfs: deferring update (trigger activated) Setting up linux-image-6.12.32-amd64 (6.12.32-1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.12.31-amd64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.12.31-amd64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.12.32-amd64 I: /initrd.img is now a symlink to boot/initrd.img-6.12.32-amd64 /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.12.32-amd64 I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vg_zephyr-lv_zephyr_swap) I: Set the RESUME variable to override this. Setting up linux-image-amd64 (6.12.32-1) ... Processing triggers for man-db (2.13.1-1) ... Processing triggers for initramfs-tools (0.148.2) ... update-initramfs: /boot/initrd.img-6.12.32-amd64 has already been updated since Fri 20 Jun 2025 13:29:37 BST. Log ended: 2025-06-20 13:29:52 -- Sean WhittonAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: Sean Whitton <spwhitton@spwhitton.name>, 1108089-done@bugs.debian.org
- Cc: Felix Zielcke <fzielcke@z-51.de>
- Subject: Re: Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade
- From: Bastian Blank <waldi@debian.org>
- Date: Sat, 21 Jun 2025 11:52:18 +0200
- Message-id: <20250621095218.escprapzhya4ukyw@shell.thinkmo.de>
- Mail-followup-to: Bastian Blank <waldi@debian.org>, Sean Whitton <spwhitton@spwhitton.name>, 1108089-done@bugs.debian.org, Felix Zielcke <fzielcke@z-51.de>
- In-reply-to: <[🔎] 87zfe2o5bh.fsf@zephyr.silentflame.com>
- References: <[🔎] aFVYzrDZZqlO6p7Z@zephyr.silentflame.com> <[🔎] c91339356ecf944446d6c2af58b7cffdd915e86d.camel@z-51.de> <[🔎] aFVYzrDZZqlO6p7Z@zephyr.silentflame.com> <[🔎] 87zfe2o5bh.fsf@zephyr.silentflame.com>
Hi Sean Please trim your emails to useful length. On Fri, Jun 20, 2025 at 03:28:34PM +0100, Sean Whitton wrote: > On Fri 20 Jun 2025 at 03:15pm +02, Felix Zielcke wrote: > > Do you have /etc/kernel/postinst.d/zz-update-grub? > > It should be installed by grub2-common. > I have /etc/kernel/postinst.d/zz-update-grub.dpkg-dist only. > Reinstalling grub2-common does not fix the problem. This means the file was removed somehow. dpkg does not restore removed conffiles if not forced, so a plain reinstall will not help. After trixie we will move those files away, so this should then be fixed for good then. Anyway, there is no bug in either grub or linux, just normal conffile handling. Closing. Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, "Day of the Dove", stardate unknown
--- End Message ---