new kernel installed but not visible while booting

ronajon

Member
Jan 3, 2021
3
0
6
123
i've updated my proxmox to the latest 8.1.3 version, and kernel 6.5.11-4 installed with that upgrade.
after rebooting i noticed that the kernel-version in the summary screen still was 6.2.16-3.

i rebooted the system again, and in the linux boot screen, the only kernel visible was 6.2.16-3, while i have more kernels installed

Code:
nfs-kernel-server/stable,now 1:2.6.2-4 amd64 [installed]
proxmox-default-kernel/stable,now 1.0.1 all [installed,automatic]
proxmox-kernel-6.2.16-18-pve/stable,now 6.2.16-18 amd64 [installed]
proxmox-kernel-6.2.16-19-pve/stable,now 6.2.16-19 amd64 [installed,automatic]
proxmox-kernel-6.2/stable,now 6.2.16-19 all [installed,automatic]
proxmox-kernel-6.5.11-4-pve-signed/stable,now 6.5.11-4 amd64 [installed,automatic]
proxmox-kernel-6.5/stable,now 6.5.11-4 all [installed,automatic]
proxmox-kernel-helper/stable,now 8.0.9 all [installed]
pve-kernel-6.2.16-3-pve/stable,now 6.2.16-3 amd64 [installed]
pve-kernel-6.2/stable,now 8.0.5 all [installed]

the default kernel entry in grub.cfg points to 6.5.11-4
Code:
menuentry 'Proxmox VE GNU/Linux' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-44a79db9-256c-4ddd-a237-0ec22d1eb400' {
    load_video
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_gpt
    insmod lvm
    insmod ext2
    set root='lvmid/NLUfF0-BHTM-Ulb8-CkI1-TVyC-eiyP-hHxSHv/HqtWP7-mKl0-uc9o-fCc9-R6NC-FQyD-wH1rfo'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint='lvmid/NLUfF0-BHTM-Ulb8-CkI1-TVyC-eiyP-hHxSHv/HqtWP7-mKl0-uc9o-fCc9-R6NC-FQyD-wH1rfo'  44a79db9-256c-4ddd-a237-0ec22d1eb400
    else
      search --no-floppy --fs-uuid --set=root 44a79db9-256c-4ddd-a237-0ec22d1eb400
    fi
    echo    'Loading Linux 6.5.11-4-pve ...'
    linux    /boot/vmlinuz-6.5.11-4-pve root=/dev/mapper/pve-root ro  quiet intel_iommu=off intremap=off
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-6.5.11-4-pve

the partition the system boots from is sdd

Code:
root@kellingin:/boot# fdisk -l /dev/sdd
Disk /dev/sdd: 29.3 GiB, 31457280000 bytes, 61440000 sectors
Disk model: PHILIPS        
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xea908e52

Device     Boot Start    End Sectors  Size Id Type
/dev/sdd1  *     2048 264191  262144  128M 83 Linux

i already tried update-grub /dev/sdd several times, but the latest kernel is not visible after a reboot

when installing a new kernel, there are some messages about missing EFI partitions ?

Code:
root@kellingin:/boot# apt install proxmox-kernel-6.5.11-3-pve
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  proxmox-kernel-6.5.11-3-pve
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 99.6 MB of archives.
After this operation, 558 MB of additional disk space will be used.
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.5.11-3-pve amd64 6.5.11-3 [99.6 MB]
Fetched 99.6 MB in 4s (26.2 MB/s)                      
Selecting previously unselected package proxmox-kernel-6.5.11-3-pve.
(Reading database ... 71336 files and directories currently installed.)
Preparing to unpack .../proxmox-kernel-6.5.11-3-pve_6.5.11-3_amd64.deb ...
Unpacking proxmox-kernel-6.5.11-3-pve (6.5.11-3) ...
Setting up proxmox-kernel-6.5.11-3-pve (6.5.11-3) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.5.11-3-pve /boot/vmlinuz-6.5.11-3-pve
update-initramfs: Generating /boot/initrd.img-6.5.11-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
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.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.5.11-3-pve /boot/vmlinuz-6.5.11-3-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.5.11-3-pve /boot/vmlinuz-6.5.11-3-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-systemd-boot 6.5.11-3-pve /boot/vmlinuz-6.5.11-3-pve
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.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.5.11-3-pve /boot/vmlinuz-6.5.11-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.5.11-4-pve
Found initrd image: /boot/initrd.img-6.5.11-4-pve
Found linux image: /boot/vmlinuz-6.5.11-3-pve
Found initrd image: /boot/initrd.img-6.5.11-3-pve
Found linux image: /boot/vmlinuz-6.2.16-19-pve
Found initrd image: /boot/initrd.img-6.2.16-19-pve
Found linux image: /boot/vmlinuz-6.2.16-18-pve
Found initrd image: /boot/initrd.img-6.2.16-18-pve
Found linux image: /boot/vmlinuz-6.2.16-3-pve
Found initrd image: /boot/initrd.img-6.2.16-3-pve
Found memtest86+x64 image: /boot/memtest86+x64.bin
done
 
Last edited:
are you booting using EFI? do you have your ESP mounted?
 
i'm booting EFI, not sure if i have ESP mounted ?

i'm booting from /dev/sdf, grub is installed on /dev/sdd

fdisk -l /dev/sdd
Code:
Disk /dev/sdd: 29.3 GiB, 31457280000 bytes, 61440000 sectors
Disk model: PHILIPS         
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xea908e52

Device     Boot Start    End Sectors  Size Id Type
/dev/sdd1  *     2048 264191  262144  128M 83 Linux

fdisk -l /dev/sdf
Code:
Disk /dev/sdf: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Seagate BarraCud
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AC7B7B54-9EDD-4169-9F57-22666269155E

Device       Start       End   Sectors   Size Type
/dev/sdf1       34      2047      2014  1007K BIOS boot
/dev/sdf2     2048   2099199   2097152     1G EFI System
/dev/sdf3  2099200 488397134 486297935 231.9G Linux LVM


i also have another system (similar hardware to the one above, HP Microserver Gen8 )
also has grub on /dev/sdd and boots from /dev/sde

fdisk -l /dev/sdd
Code:
Disk /dev/sdd: 14.54 GiB, 15610576896 bytes, 30489408 sectors
Disk model: DataTraveler 2.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98E8F751-4F90-477C-854C-8EF59A9EAE56

Device     Start    End Sectors  Size Type
/dev/sdd1   2048 249855  247808  121M BIOS boot

fdisk -l /dev/sde
Code:
Disk /dev/sde: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: CT250BX100SSD1 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8F2A8AB0-62D1-4451-8977-357AB858CF1B

Device       Start       End   Sectors   Size Type
/dev/sde1       34      2047      2014  1007K BIOS boot
/dev/sde2     2048   1050623   1048576   512M EFI System
/dev/sde3  1050624 488397134 487346511 232.4G Linux LVM

i noticed that in the system which does not update the kernel correct, the DiskType is DOS, and on the system where the kernel is updated, the DiskType in GPT?
 
issue solved. the problem was not MBR / GPT but the size of /boot

after rebooting from rescue CD, resized the /boot partition to 1GB and the latest partition was selected on boot
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!