Old kernel used during boot

patric83 · 2025-10-09T11:38:19+0200

Hi,

A newbie here!

So I've seen that Proxmox has installed new kernels with the latest being 6.14.11-3-pve but when I boot I still get 6.14.8-2-pve
After talking with AI I figured out that I'm booting to Boot0000 proxmox GRUBX64.EFI
And that booting is using /boot/efi/EFI/proxmox/grub.cfg and that file contains only 6.14.8-2-pve and some older kernels not available on my system
Then there is /boot/grub/grub.cfg that contains 6.14.11-3-pve and 6.14.8-2-pve which is correct

So AI suggests this

cp /boot/grub/grub.cfg /boot/efi/EFI/proxmox/grub.cfg
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=proxmox --recheck

Or

grub-mkconfig -o /boot/efi/EFI/proxmox/grub.cfg

But since I'm new to this and I don't fully trust AI I'm asking the experts.

Shouldn't the kernel be added to grub during installation?
Why isn't proxmox grub.cfg updated even though I run update-grub?
Basically, how do I solve my kernel issue and hopefully prevent it in the future?

Thanks!

/Patric

janus57 · 2025-10-09T11:50:11+0200

Hi,

What is the return of these commands :

Code:

uname -a
proxmox-boot-tool status
proxmox-boot-tool kernel list

Best regards,

patric83 · 2025-10-09T11:52:44+0200

Hi,

uname -a

Linux proxmox 6.14.8-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-2 (2025-07-22T10:04Z) x86_64 GNU/Linux

proxmox-boot-tool status

Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
3AC6-EC77 is configured with: uefi (versions: grub.cfg, grubx64.efi), grub (versions: 6.14.11-3-pve, 6.14.8-2-pve)

proxmox-boot-tool kernel list

Manually selected kernels:
None.

Automatically selected kernels:
6.14.11-3-pve
6.14.8-2-pve

I've tried to pin 6.14.11-3-pve but didn't help during boot

/Patric

leesteken · 2025-10-09T11:56:54+0200

Does your system actually boot from the ESP with UUID 3AC6-EC77? Maybe the BIOS is set to boot from another (not recently updated) ESP? What is the output of lsblk -o+UUID ? You might want to correlate that list with the output ls -l /dev/disk/by-id/ to identify the actual drive.

patric83 · 2025-10-09T12:03:59+0200

lsblk -o+UUID

Code:

NAME      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS UUID
sda         8:0    0 465.8G  0 disk             
├─sda1      8:1    0  1007K  0 part             
├─sda2      8:2    0     1G  0 part /boot/efi   3AC6-EC77
└─sda3      8:3    0 464.8G  0 part             gtrKxc-r4cw-rJIK-ApGj-aaui-9B7O-0CP1EU
  ├─pve-swap
  │       252:0    0     8G  0 lvm  [SWAP]      16f64e86-336c-4ed4-9e96-ba1ed3ca0490
  └─pve-root
          252:1    0 456.8G  0 lvm  /           b42a5778-5872-42a3-a503-a50952aeac02
sdb         8:16   0 931.5G  0 disk             
└─sdb1      8:17   0 931.5G  0 part             afY1f9-Jr2V-UIi3-mtzX-WzRQ-ERsJ-ATEVMf
  ├─pve--data-pve--data_tmeta
  │ │     252:2    0   9.3G  0 lvm             
  │ └─pve--data-pve--data-tpool
  │   │   252:4    0 912.8G  0 lvm

ls -l /dev/disk/by-id/

Code:

total 0
lrwxrwxrwx 1 root root  9 Oct  9 11:19 ata-Samsung_SSD_870_EVO_1TB_S75CNX0W709495W -> ../../sdb
lrwxrwxrwx 1 root root 10 Oct  9 11:19 ata-Samsung_SSD_870_EVO_1TB_S75CNX0W709495W-part1 -> ../../sdb1
lrwxrwxrwx 1 root root  9 Oct  9 11:19 ata-Samsung_SSD_870_EVO_500GB_S7EWNJ0W523871H -> ../../sda
lrwxrwxrwx 1 root root 10 Oct  9 11:19 ata-Samsung_SSD_870_EVO_500GB_S7EWNJ0W523871H-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Oct  9 11:19 ata-Samsung_SSD_870_EVO_500GB_S7EWNJ0W523871H-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Oct  9 11:19 ata-Samsung_SSD_870_EVO_500GB_S7EWNJ0W523871H-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 Oct  9 11:19 ata-ST4000VN006-3CW104_WW66F3YX -> ../../sdd
lrwxrwxrwx 1 root root 10 Oct  9 11:19 ata-ST4000VN006-3CW104_WW66F3YX-part1 -> ../../sdd1
lrwxrwxrwx 1 root root  9 Oct  9 11:19 ata-ST4000VN008-2DR166_ZGY46FVL -> ../../sdc
lrwxrwxrwx 1 root root 10 Oct  9 11:19 ata-ST4000VN008-2DR166_ZGY46FVL-part1 -> ../../sdc1
...

leesteken · 2025-10-09T12:04:53+0200

Please show the output in CODE-tags instead of "quoting" so that people can read the various columns more easily.
Is your BIOS set to boot from ata-SSD_870_EVO_500GB_S7EWNJ0W523871H-part2, which appears to be the only ESP (with the correct UUID that proxmox-boot-tool keeps up to date)?
What is the output of efibootmgr?

patric83 · 2025-10-09T12:09:45+0200

Here's the output

Code:

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,0002
Boot0000* proxmox       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\PROXMOX\GRUBX64.EFI)
Boot0001* UEFI OS       HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0002* Linux Boot Manager    HD(2,GPT,122be07e-eb9a-4a15-a3c7-7f770f86eac4,0x800,0x200000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)

janus57 · 2025-10-09T12:18:22+0200

Hi,

what is the result of :

Code:

bootctl
findmnt /

Best regards,

patric83 · 2025-10-09T12:20:21+0200

Code:

System:
      Firmware: n/a (n/a)
 Firmware Arch: x64
   Secure Boot: disabled
  TPM2 Support: yes
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: GRUB 2.12-9+pmx2
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Load drop-in drivers
               ✗ Support Type #1 sort-key field
               ✗ Support @saved pseudo-entry
               ✗ Support Type #1 devicetree field
               ✗ Enroll SecureBoot keys
               ✗ Retain SHIM protocols
               ✗ Menu can be disabled
               ✗ Multi-Profile UKIs are supported
               ✓ Boot loader set partition information
    Partition: /dev/disk/by-partuuid/122be07e-eb9a-4a15-a3c7-7f770f86eac4

Random Seed:
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot/efi (/dev/disk/by-partuuid/122be07e-eb9a-4a15-a3c7-7f770f86eac4)
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 257.8-1~deb13u2)
               └─/EFI/BOOT/BOOTx64.EFI

Boot Loaders Listed in EFI Variables:
        Title: proxmox
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/122be07e-eb9a-4a15-a3c7-7f770f86eac4
         File: └─/EFI/PROXMOX/GRUBX64.EFI

        Title: UEFI OS
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/122be07e-eb9a-4a15-a3c7-7f770f86eac4
         File: └─/EFI/BOOT/BOOTX64.EFI

        Title: Linux Boot Manager
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/122be07e-eb9a-4a15-a3c7-7f770f86eac4
         File: └─/EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI

Boot Loader Entries:
        $BOOT: /boot/efi (/dev/disk/by-partuuid/122be07e-eb9a-4a15-a3c7-7f770f86eac4)
        token: 49ecd685605a4d7aad36338ab75197c2

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: Memtest86+
           id: memtest.conf
       source: /boot/efi//loader/entries/memtest.conf (on the EFI System Partition)
          efi: /boot/efi//EFI/memtest86+/memtest86+x64.efi

and

Code:

TARGET SOURCE               FSTYPE OPTIONS
/      /dev/mapper/pve-root ext4   rw,relatime,errors=remount-ro

janus57 · 2025-10-09T13:16:26+0200

Hi,

how the proxmox was installed ?

Best regards,

patric83 · 2025-10-09T13:28:03+0200

What do you mean?

/Patric

Search

Search

Old kernel used during boot

patric83

New Member

janus57

Renowned Member

patric83

New Member

leesteken

Distinguished Member

patric83

New Member

leesteken

Distinguished Member

patric83

New Member

janus57

Renowned Member

patric83

New Member

janus57

Renowned Member

patric83

New Member

We value your privacy