Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #88078 > unrolled thread
| Started by | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| First post | 2025-06-20 15:00 +0200 |
| Last post | 2025-06-21 12:50 +0200 |
| Articles | 14 — 5 participants |
Back to article view | Back to linux.debian.kernel
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
| From | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| Date | 2025-06-20 15:00 +0200 |
| Subject | Bug#1108089: grub-efi-amd64,linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <KZJvz-bTDX-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
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 Whitton
[toc] | [next] | [standalone]
| From | Felix Zielcke <fzielcke@z-51.de> |
|---|---|
| Date | 2025-06-20 15:30 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <KZJYB-bU68-1@gated-at.bofh.it> |
| In reply to | #88078 |
Am Freitag, dem 20.06.2025 um 13:49 +0100 schrieb Sean Whitton: > 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: > [...] Hi Sean, strange that update-grub isn't at all run. Do you have /etc/kernel/postinst.d/zz-update-grub? It should be installed by grub2-common.
[toc] | [prev] | [next] | [standalone]
| From | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| Date | 2025-06-20 16:40 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <KZL4l-bUJQ-13@gated-at.bofh.it> |
| In reply to | #88080 |
[Multipart message — attachments visible in raw view] — view raw
Hello, On Fri 20 Jun 2025 at 03:15pm +02, Felix Zielcke wrote: > Am Freitag, dem 20.06.2025 um 13:49 +0100 schrieb Sean Whitton: >> 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: >> > [...] > > Hi Sean, > > strange that update-grub isn't at all run. > > 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. -- Sean Whitton
[toc] | [prev] | [next] | [standalone]
| From | Felix Zielcke <fzielcke@z-51.de> |
|---|---|
| Date | 2025-06-20 18:10 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <KZMtr-bVNw-7@gated-at.bofh.it> |
| In reply to | #88085 |
Am Freitag, dem 20.06.2025 um 15:28 +0100 schrieb Sean Whitton: > Hello, > > [...] > > I have /etc/kernel/postinst.d/zz-update-grub.dpkg-dist only. > > Reinstalling grub2-common does not fix the problem. This is very strange. zz-update-grub is just a normal dpkg conffile. We don't do anything special with it. And according to our git, it wast last changed 2021. I guess to fix that with dpkg you would need to completely purge the package and then reinstall. But please make a backup of /etc/default/grub Or you could check if the dpkg-dist is the correct one and just rename that. Also check /etc/kernel/postrm.d/ Looks like there it's also missing or with the .dpkg-dist extension.
[toc] | [prev] | [next] | [standalone]
| From | Colin Watson <cjwatson@debian.org> |
|---|---|
| Date | 2025-06-20 18:20 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <KZMD7-bVQN-1@gated-at.bofh.it> |
| In reply to | #88087 |
On Fri, Jun 20, 2025 at 06:04:26PM +0200, Felix Zielcke wrote: >Am Freitag, dem 20.06.2025 um 15:28 +0100 schrieb Sean Whitton: >> I have /etc/kernel/postinst.d/zz-update-grub.dpkg-dist only. >> >> Reinstalling grub2-common does not fix the problem. > >This is very strange. >zz-update-grub is just a normal dpkg conffile. We don't do anything >special with it. >And according to our git, it wast last changed 2021. > >I guess to fix that with dpkg you would need to completely purge the >package and then reinstall. dpkg doesn't reinstall removed conffiles by default (it interprets that as a deliberate user change), but you can override that using --force-confmiss. -- Colin Watson (he/him) [cjwatson@debian.org]
[toc] | [prev] | [next] | [standalone]
| From | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| Date | 2025-06-21 12:40 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <L03ND-c6Pm-1@gated-at.bofh.it> |
| In reply to | #88087 |
[Multipart message — attachments visible in raw view] — view raw
control: reopen -1 Hello, I definitely did not remove the file myself. Therefore, it is a bug somewhere that it got deleted by something about the package upgrade. One thing that seems notable to me is that the apt log I posted has a message about an initrd image having "already been updated". I have not seen this message before. HTH. -- Sean Whitton
[toc] | [prev] | [next] | [standalone]
| From | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| Date | 2025-06-21 12:40 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <L03ND-c6Pm-3@gated-at.bofh.it> |
| In reply to | #88087 |
[Multipart message — attachments visible in raw view] — view raw
Hello, On Fri 20 Jun 2025 at 06:04pm +02, Felix Zielcke wrote: > Also check /etc/kernel/postrm.d/ > Looks like there it's also missing or with the .dpkg-dist extension. Yes, in that directory too it is there but only with a .dpkg-dist extension. -- Sean Whitton
[toc] | [prev] | [next] | [standalone]
| From | Bastian Blank <waldi@debian.org> |
|---|---|
| Date | 2025-06-21 14:00 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <L0533-c7xu-1@gated-at.bofh.it> |
| In reply to | #88101 |
On Sat, Jun 21, 2025 at 11:38:46AM +0100, Sean Whitton wrote:
> On Fri 20 Jun 2025 at 06:04pm +02, Felix Zielcke wrote:
> > Also check /etc/kernel/postrm.d/
> > Looks like there it's also missing or with the .dpkg-dist extension.
> Yes, in that directory too it is there but only with a .dpkg-dist
> extension.
Neither maintainer scripts of linux nor grub2 contain code that could
remove just /etc/kernel/post{inst,rm}.d/zz-upgrade-grub, which is what
you claim you see. Please provide evidence instead of paraphrasing.
Aka:
- dpkg -s grub2-common
- ls -alR /etc
- grep -r /etc/kernel /var/lib/dpkg/info
- zgrep /etc/kernel /var/log/apt/*
Also code search does not find anything else targeting the
zz-upgrade-grub files specifically.
Bastian
--
No one can guarantee the actions of another.
-- Spock, "Day of the Dove", stardate unknown
[toc] | [prev] | [next] | [standalone]
| From | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| Date | 2025-06-22 18:30 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <L0vJT-coCE-1@gated-at.bofh.it> |
| In reply to | #88106 |
[Multipart message — attachments visible in raw view] — view raw
Hello,
On Sat 21 Jun 2025 at 01:46pm +02, Bastian Blank wrote:
> On Sat, Jun 21, 2025 at 11:38:46AM +0100, Sean Whitton wrote:
>> On Fri 20 Jun 2025 at 06:04pm +02, Felix Zielcke wrote:
>> > Also check /etc/kernel/postrm.d/
>> > Looks like there it's also missing or with the .dpkg-dist extension.
>> Yes, in that directory too it is there but only with a .dpkg-dist
>> extension.
>
> Neither maintainer scripts of linux nor grub2 contain code that could
> remove just /etc/kernel/post{inst,rm}.d/zz-upgrade-grub, which is what
> you claim you see. Please provide evidence instead of paraphrasing.
Okay.
> Aka:
> - dpkg -s grub2-common
--8<---------------cut here---------------start------------->8---
Package: grub2-common
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 1404
Maintainer: GRUB Maintainers <pkg-grub-devel@alioth-lists.debian.net>
Architecture: amd64
Multi-Arch: foreign
Source: grub2
Version: 2.12-8
Replaces: grub, grub-cloud-amd64 (<< 0.0.4), grub-common (<< 1.99-1), grub-coreboot (<< 2.02+dfsg1-7), grub-doc (<< 0.97-32), grub-efi-amd64 (<< 2.02+dfsg1-7), grub-efi-arm (<< 2.02+dfsg1-7), grub-efi-arm64 (<< 2.02+dfsg1-7), grub-efi-ia32 (<< 2.02+dfsg1-7), grub-efi-ia64 (<< 2.02+dfsg1-7), grub-ieee1275 (<< 2.02+dfsg1-7), grub-legacy, grub-legacy-doc (<< 0.97-59), grub-pc (<< 2.02+dfsg1-7), grub-uboot (<< 2.02+dfsg1-7), grub-xen (<< 2.02+dfsg1-7), grub-yeeloong (<< 2.02+dfsg1-7)
Depends: grub-common (= 2.12-8), dpkg (>= 1.15.4), libc6 (>= 2.38), libdevmapper1.02.1 (>= 2:1.02.197), libefiboot1t64 (>= 38), libefivar1t64 (>= 38), liblzma5 (>= 5.1.1alpha+20120614)
Breaks: grub (<< 0.97-54), grub-cloud-amd64 (<< 0.0.4), grub-coreboot (<< 2.02+dfsg1-7), grub-doc (<< 0.97-32), grub-efi-amd64 (<< 2.02+dfsg1-7), grub-efi-arm (<< 2.02+dfsg1-7), grub-efi-arm64 (<< 2.02+dfsg1-7), grub-efi-ia32 (<< 2.02+dfsg1-7), grub-efi-ia64 (<< 2.02+dfsg1-7), grub-ieee1275 (<< 2.02+dfsg1-7), grub-legacy (<< 0.97-83~), grub-legacy-doc (<< 0.97-59), grub-pc (<< 2.02+dfsg1-7), grub-uboot (<< 2.02+dfsg1-7), grub-xen (<< 2.02+dfsg1-7), grub-yeeloong (<< 2.02+dfsg1-7), shim (<< 0.9+1474479173.6c180c6-0ubuntu1~)
Conffiles:
/etc/kernel/postinst.d/zz-update-grub 5a98abefbfe97dbed36db7899251e433
/etc/kernel/postrm.d/zz-update-grub 5a98abefbfe97dbed36db7899251e433
Description: GRand Unified Bootloader (common files for version 2)
This package contains common files shared by the distinct flavours of GRUB.
The files in this package are specific to GRUB 2, and would break GRUB
Legacy if installed on the same system.
Homepage: https://www.gnu.org/software/grub/
--8<---------------cut here---------------end--------------->8---
> - ls -alR /etc
Hmm, that feels like something of a privacy breach.
Could you narrow it down?
> - grep -r /etc/kernel /var/lib/dpkg/info
--8<---------------cut here---------------start------------->8---
/var/lib/dpkg/info/initramfs-tools.conffiles:/etc/kernel/postinst.d/initramfs-tools
/var/lib/dpkg/info/initramfs-tools.conffiles:/etc/kernel/postrm.d/initramfs-tools
/var/lib/dpkg/info/unattended-upgrades.conffiles:/etc/kernel/postinst.d/unattended-upgrades
/var/lib/dpkg/info/initramfs-tools.list:/etc/kernel
/var/lib/dpkg/info/initramfs-tools.list:/etc/kernel/postinst.d
/var/lib/dpkg/info/initramfs-tools.list:/etc/kernel/postinst.d/initramfs-tools
/var/lib/dpkg/info/initramfs-tools.list:/etc/kernel/postrm.d
/var/lib/dpkg/info/initramfs-tools.list:/etc/kernel/postrm.d/initramfs-tools
/var/lib/dpkg/info/linux-image-6.12.31-amd64.postrm:if [ -d /etc/kernel/postrm.d ]; then
/var/lib/dpkg/info/linux-image-6.12.31-amd64.postrm: --arg=$image_path /etc/kernel/postrm.d
/var/lib/dpkg/info/apt.list:/etc/kernel
/var/lib/dpkg/info/apt.list:/etc/kernel/postinst.d
/var/lib/dpkg/info/grub2-common.conffiles:/etc/kernel/postinst.d/zz-update-grub
/var/lib/dpkg/info/grub2-common.conffiles:/etc/kernel/postrm.d/zz-update-grub
/var/lib/dpkg/info/grub-efi-amd64.postinst: if egrep -q '^[[:space:]]*post(inst|rm)_hook[[:space:]]*=[[:space:]]*(/sbin/|/usr/sbin/)?update-grub' /etc/kernel-img.conf 2>/dev/null; then
/var/lib/dpkg/info/grub-efi-amd64.postinst: echo 'Removing update-grub hooks from /etc/kernel-img.conf in favour of' >&2
/var/lib/dpkg/info/grub-efi-amd64.postinst: echo '/etc/kernel/ hooks.' >&2
/var/lib/dpkg/info/grub-efi-amd64.postinst: sed -ri /etc/kernel-img.conf -e '\%^[[:space:]]*post(inst|rm)_hook[[:space:]]*=[[:space:]]*(/sbin/|/usr/sbin/)?update-grub%d'
/var/lib/dpkg/info/grub-efi-amd64.preinst: test -h /etc/kernel/postrm.d/zz-update-grub; then
/var/lib/dpkg/info/grub-efi-amd64.preinst: rm -f /etc/kernel/postrm.d/zz-update-grub
/var/lib/dpkg/info/grub2-common.list:/etc/kernel
/var/lib/dpkg/info/grub2-common.list:/etc/kernel/postinst.d
/var/lib/dpkg/info/grub2-common.list:/etc/kernel/postinst.d/zz-update-grub
/var/lib/dpkg/info/grub2-common.list:/etc/kernel/postrm.d
/var/lib/dpkg/info/grub2-common.list:/etc/kernel/postrm.d/zz-update-grub
/var/lib/dpkg/info/systemd.list:/etc/kernel
/var/lib/dpkg/info/systemd.list:/etc/kernel/install.d
/var/lib/dpkg/info/intel-microcode.list:/etc/kernel
/var/lib/dpkg/info/intel-microcode.list:/etc/kernel/preinst.d
/var/lib/dpkg/info/intel-microcode.list:/etc/kernel/preinst.d/intel-microcode
/var/lib/dpkg/info/unattended-upgrades.list:/etc/kernel
/var/lib/dpkg/info/unattended-upgrades.list:/etc/kernel/postinst.d
/var/lib/dpkg/info/unattended-upgrades.list:/etc/kernel/postinst.d/unattended-upgrades
/var/lib/dpkg/info/extlinux.postinst:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/extlinux.postinst:dpkg-maintscript-helper rm_conffile /etc/kernel/postrm.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/extlinux.postrm:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/extlinux.postrm:dpkg-maintscript-helper rm_conffile /etc/kernel/postrm.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/extlinux.preinst:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/extlinux.preinst:dpkg-maintscript-helper rm_conffile /etc/kernel/postrm.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/extlinux.prerm:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/extlinux.prerm:dpkg-maintscript-helper rm_conffile /etc/kernel/postrm.d/zz-extlinux 3:6.04\~git20171011.af7e95c3\+dfsg1-3 extlinux -- "$@"
/var/lib/dpkg/info/intel-microcode.conffiles:/etc/kernel/preinst.d/intel-microcode
/var/lib/dpkg/info/linux-image-6.12.27-amd64.postinst:if [ -d /etc/kernel/postinst.d ]; then
/var/lib/dpkg/info/linux-image-6.12.27-amd64.postinst: --arg=$image_path /etc/kernel/postinst.d
/var/lib/dpkg/info/linux-image-6.12.27-amd64.postrm:if [ -d /etc/kernel/postrm.d ]; then
/var/lib/dpkg/info/linux-image-6.12.27-amd64.postrm: --arg=$image_path /etc/kernel/postrm.d
/var/lib/dpkg/info/linux-image-6.12.27-amd64.preinst:if [ -d /etc/kernel/preinst.d ]; then
/var/lib/dpkg/info/linux-image-6.12.27-amd64.preinst: --arg=$image_path /etc/kernel/preinst.d
/var/lib/dpkg/info/linux-image-6.12.27-amd64.prerm:if [ -d /etc/kernel/prerm.d ]; then
/var/lib/dpkg/info/linux-image-6.12.27-amd64.prerm: --arg=$image_path /etc/kernel/prerm.d
/var/lib/dpkg/info/apt.postinst:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/apt-auto-removal 2.4.5\~ -- "$@"
/var/lib/dpkg/info/apt.postrm:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/apt-auto-removal 2.4.5\~ -- "$@"
/var/lib/dpkg/info/apt.preinst:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/apt-auto-removal 2.4.5\~ -- "$@"
/var/lib/dpkg/info/apt.prerm:dpkg-maintscript-helper rm_conffile /etc/kernel/postinst.d/apt-auto-removal 2.4.5\~ -- "$@"
--8<---------------cut here---------------end--------------->8---
> - zgrep /etc/kernel /var/log/apt/*
This did not produce any useful output:
--8<---------------cut here---------------start------------->8---
/var/log/apt/term.log:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.10.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.10.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.11.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.11.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.12.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.12.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.1.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.1.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.1.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.2.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.2.gz:Installing new version of config file /etc/kernel/postinst.d/initramfs-tools ...
/var/log/apt/term.log.2.gz:Installing new version of config file /etc/kernel/postrm.d/initramfs-tools ...
/var/log/apt/term.log.2.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.2.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.2.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.3.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.3.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.4.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.4.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.6.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.6.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.8.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.8.gz:/etc/kernel/postrm.d/initramfs-tools:
/var/log/apt/term.log.9.gz:/etc/kernel/postinst.d/initramfs-tools:
/var/log/apt/term.log.9.gz:/etc/kernel/postrm.d/initramfs-tools:
--8<---------------cut here---------------end--------------->8---
--
Sean Whitton
[toc] | [prev] | [next] | [standalone]
| From | Bastian Blank <waldi@debian.org> |
|---|---|
| Date | 2025-06-24 23:40 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <L1jwZ-cU4A-1@gated-at.bofh.it> |
| In reply to | #88116 |
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. > > - 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. > > - grep -r /etc/kernel /var/lib/dpkg/info So there seems to be nothing else installed that could remove those files as part of maintainer scripts at least. > > - 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. 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' Bastian -- You're dead, Jim. -- McCoy, "The Tholian Web", stardate unknown
[toc] | [prev] | [next] | [standalone]
| From | Sean Whitton <spwhitton@spwhitton.name> |
|---|---|
| Date | 2025-06-25 12:00 +0200 |
| Subject | Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <L1v57-d1Wb-1@gated-at.bofh.it> |
| In reply to | #88128 |
[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
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-06-21 12:10 +0200 |
| Subject | Bug#1108089: marked as done (grub-efi-amd64,linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade) |
| Message-ID | <L03kB-c6AH-1@gated-at.bofh.it> |
| In reply to | #88078 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-06-21 12:40 +0200 |
| Subject | Processed: Re: Bug#1108089: grub-efi-amd64, linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade |
| Message-ID | <L03ND-c6Pm-11@gated-at.bofh.it> |
| In reply to | #88078 |
Processing control commands:
> reopen -1
Bug #1108089 {Done: Bastian Blank <waldi@debian.org>} [grub-efi-amd64,linux-image-amd64] grub-efi-amd64,linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade
Bug reopened
Ignoring request to alter fixed versions of bug #1108089 to the same values previously set
--
1108089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108089
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2025-06-21 12:50 +0200 |
| Subject | Bug#1108089: marked as done (grub-efi-amd64,linux-image-amd64: system fails to boot because grub config not updated after latest kernel upgrade) |
| Message-ID | <L03Xj-c6SJ-1@gated-at.bofh.it> |
| In reply to | #88078 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sat, 21 Jun 2025 12:45:32 +0200 with message-id <20250621104532.6aqtxaipxxbh3yyt@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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web