Old kernel used during boot

patric83 · Oct 9, 2025

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 · Oct 9, 2025

Hi,

What is the return of these commands :

Code:

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

Best regards,

patric83 · Oct 9, 2025

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 · Oct 9, 2025

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 · Oct 9, 2025

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 · Oct 9, 2025

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 · Oct 9, 2025

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 · Oct 9, 2025

Hi,

what is the result of :

Code:

bootctl
findmnt /

Best regards,

patric83 · Oct 9, 2025

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 · Oct 9, 2025

Hi,

how the proxmox was installed ?

Best regards,

patric83 · Oct 9, 2025

What do you mean?

/Patric

janus57 · Sunday at 11:26

Hi,

Does your promos is a new installation using iso ?
Top of debian ?
Upgrade from the previous version ?

For me it's weird to see a mix in your output.

Have you tested these commands and after reboot :

Code:

promos-boot-tool kernel pin 6.14.11-3-pve --next-boot
promos-boot-tool refresh

Best regards,

patric83 · Sunday at 16:12

janus57 said:
Hi,

Does your promos is a new installation using iso ?
Top of debian ?
Upgrade from the previous version ?

For me it's weird to see a mix in your output.

Have you tested these commands and after reboot :

Code:

promos-boot-tool kernel pin 6.14.11-3-pve --next-boot promos-boot-tool refresh

Best regards,

Hi,

Aah ok! I have had Proxmox since v8 and it was installed using iso.

I’ve previously had issues with kernels. Got stuck on grub during boot so I’ve gotten help with that here on the forum so perhaps thats the reason?
But I’ve managed to run the update and get new kernels but not the last few times.

I’ve tried that command but it didn’t help.

If I during boot stop at grub. Then go in grub console. When I exit console I then get to the correct kernel. But thats the only way I’ve managed to do that.
AI mentioned during my own research that during boot it takes /boot/efi/EFI/proxmox/grub.cfg (6.14.8-2-pve) but when going out of grub console it falls back to /boot/grub/grub.cfg (6.14.11-3-pve).

janus57 · Sunday at 23:13

Hi,

And during boot if you choose "Linux Boot Manager" instead of "proxmox" ?

Best regards,

patric83 · Tuesday at 12:25

Hi,

Sorry for the late response...

This is what I get during boot

If I go in to advanced I get this

So "Linux Boot Manager" is not an option for me.

If I go to console then exit I get this

And under advanced this

janus57 · Tuesday at 12:36

Hi,

For me with your screen, you have 2 boot loader (since you have 2 different menus), and some old kernel.

What's the return of this command :

Code:

dpkg -l | grep -Hni '6.8.' && dpkg -l | grep -Hni '6.14.'

Best regards,

patric83 · Tuesday at 12:41

Code:

(standard input):162:ii  less                                 668-1                                amd64        pager program similar to more
(standard input):741:rc  proxmox-kernel-6.8                   6.8.12-13                            all          Latest Proxmox Kernel Image
(standard input):30:ii  btrfs-progs                          6.14-1                               amd64        Checksumming Copy on Write Filesystem utilities
(standard input):82:ii  ethtool                              1:6.14.2-1                           amd64        display or change Ethernet device settings
(standard input):406:ii  liblwp-protocol-https-perl           6.14-1                               all          HTTPS driver for LWP::UserAgent
(standard input):738:ii  proxmox-kernel-6.14                  6.14.11-3                            all          Latest Proxmox Kernel Image
(standard input):739:ii  proxmox-kernel-6.14.11-3-pve-signed  6.14.11-3                            amd64        Proxmox Kernel Image (signed)
(standard input):740:ii  proxmox-kernel-6.14.8-2-pve-signed   6.14.8-2                             amd64        Proxmox Kernel Image (signed)

janus57 · 2025-10-16T17:56:07+0200

Hi,

In your case I don't really see which way is the better.

From what I see you have "grub" and "systemd bootloader", the one your system boot seems to be grub (which are outdated and seems to list kennel that doesn't exist anymore on your system, IF I understand correctly).

On the other "side" you have systemd bootloader, which seems up-to-date and can be manipulated from proxmox-boot-tool.

One of the "easy ways" I see it is to use only "systemd bootloader" here is the step (from : https://forum.proxmox.com/threads/selecting-bootloader-for-new-installation.133338/) :

First : remove(or comment) the `/boot/efi` entry in /etc/fstab (else your system won't come up due to the missing mount)

From all the commands we made you make, in the /etc/fstab you should see Something like : UUID=3AC6-EC77 /boot/efi vfat defaults 0 1
You can delete the line or comment it (begin with #)
umount /boot/efi
proxmox-boot-tool format /dev/sda2 --force
proxmox-boot-tool init /dev/sda2
proxmox-boot-tool refresh
reboot

I have tested this on VM with PVE9 fresh install from iso, and in my test "It just works" (if you don't forget the fstab part which i forget in my first test).

Code:

root@pve:~# bootctl
systemd-boot not installed in ESP.
System:
      Firmware: n/a (n/a)
 Firmware Arch: x64
   Secure Boot: disabled (setup)
  TPM2 Support: no
  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/b45dd4b0-7641-41d5-aa1c-553259d7b251

Random Seed:
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot/efi (/dev/disk/by-partuuid/b45dd4b0-7641-41d5-aa1c-553259d7b251)
         File: ├─/EFI/BOOT/fbx64.efi
               ├─/EFI/BOOT/grubx64.efi
               ├─/EFI/BOOT/mmx64.efi
               └─/EFI/BOOT/BOOTx64.efi

Boot Loaders Listed in EFI Variables:
        Title: proxmox
           ID: 0x0003
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/b45dd4b0-7641-41d5-aa1c-553259d7b251
         File: └─/EFI/proxmox/shimx64.efi

Boot Loader Entries:
        $BOOT: /boot/efi (/dev/disk/by-partuuid/b45dd4b0-7641-41d5-aa1c-553259d7b251)
        token: debian

0 entries, no entry could be determined as default.

Code:

root@pve:~# bootctl
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
System:
      Firmware: UEFI 2.70 (Proxmox distribution of EDK II 1.00)
 Firmware Arch: x64
   Secure Boot: disabled (setup)
  TPM2 Support: no
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 257.8-1~deb13u2
     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/b45dd4b0-7641-41d5-aa1c-553259d7b251
       Loader: └─/EFI/systemd/systemd-bootx64.efi
Current Entry: proxmox-6.14.11-4-pve.conf

Random Seed:
 System Token: set

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0004
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/b45dd4b0-7641-41d5-aa1c-553259d7b251
         File: └─/EFI/systemd/systemd-bootx64.efi

Best regards,

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

janus57

Renowned Member

patric83

New Member

janus57

Renowned Member

patric83

New Member

janus57

Renowned Member

patric83

New Member

janus57

Renowned Member

We value your privacy