Stuck on 5.11.22-3-pve

iprigger

iprigger

Renowned Member
Proxmox Subscriber
Sep 5, 2009
190
41
93
earth!
All,

I have one system that does not want to boot any other kernel than 5.11.22-3-pve

I have installed those two:
ii pve-kernel-5.11.22-3-pve 5.11.22-7 amd64 The Proxmox PVE Kernel Image
ii pve-kernel-5.15.39-1-pve 5.15.39-1 amd64 Proxmox Kernel Image

I have not yet had any chance of booting into 5.15.39-1-pve on that system - however, it works on all the other servers here.

pveversion -v says:
proxmox-ve: 7.2-1 (running kernel: 5.11.22-3-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-6
pve-kernel-helper: 7.2-6
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.11.22-3-pve: 5.11.22-7
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-7
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

update-grup shows no errors (yes, it's legacy boot). But that kernel is simply the only one that is available in grub for boot.

Even the links in /boot are correct.

Any help appreciated. This is driving me nuts.

Tobias
 
Last edited:
LnxBil said:
Could you describe what you mean by


What are the errors displayed?
Click to expand...
No errors, unfortunately.

# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
5.11.22-3-pve
5.15.39-1-pve

It just NEVER boots the 5.15.39-1-pve

and it's not displayed in GRUB

W: This system is booted via proxmox-boot-tool:
W: Executing 'update-grub' directly does not update the correct configs!
W: Running: 'proxmox-boot-tool refresh'

No /etc/kernel/cmdline found - falling back to /proc/cmdline
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "UTF-8",
LC_TERMINAL = "iTerm2",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
WARN: /dev/disk/by-uuid/2025-74B9 does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping
WARN: /dev/disk/by-uuid/2025-D0CE does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping
Found linux image: /boot/vmlinuz-5.15.39-1-pve
Found initrd image: /boot/initrd.img-5.15.39-1-pve
Found linux image: /boot/vmlinuz-5.11.22-3-pve
Found initrd image: /boot/initrd.img-5.11.22-3-pve
Found memtest86+ image: /ROOT/pve-1@/boot/memtest86+.bin
Found memtest86+ multiboot image: /ROOT/pve-1@/boot/memtest86+_multiboot.bin
done

I have NO idea, what's up here...

Tobias
 
iprigger said:
W: This system is booted via proxmox-boot-tool:
W: Executing 'update-grub' directly does not update the correct configs!
W: Running: 'proxmox-boot-tool refresh'
...
WARN: /dev/disk/by-uuid/2025-74B9 does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping
WARN: /dev/disk/by-uuid/2025-D0CE does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping
Click to expand...
Can you show us the contents of /etc/kernel/proxmox-boot-uuids? It looks like the ESP partitions that are in that file are no longer present. And probably the ESP partition that is used to boot from has not been updated and still only contains the old kernel. Can you show us the partitions of your drives with lsblk -o NAME,FSTYPE,SIZE,UUID (ESP partitions are vfat 512M)?
iprigger said:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "UTF-8",
LC_TERMINAL = "iTerm2",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
Click to expand...
As a side note: this can probably be fixed by running dpkg-reconfigure locales and selecting en_US.UTF-8 and maybe you local locale.
 
Last edited:
  • Like
Reactions: t.lamprecht
Hi...

# cat /etc/kernel/proxmox-boot-uuids
2025-74B9
2025-D0CE

and

# lsblk -o NAME,FSTYPE,SIZE,UUID
NAME FSTYPE SIZE UUID
sda 223.6G
|-sda1 1007K
|-sda2 vfat 512M 6DF4-519B
`-sda3 zfs_member 223.1G 11576862949081681133
sdb 223.6G
|-sdb1 1007K
|-sdb2 vfat 512M 6E2E-4A8C
`-sdb3 zfs_member 223.1G 11576862949081681133

That with the LOCALE - I know... but I don't care too much about that one (export LC_ALL=C would solve it)

Tobias

leesteken said:
Can you show us the contents of /etc/kernel/proxmox-boot-uuids? It looks like the ESP partitions that are in that file are no longer present. And probably the ESP partition that is used to boot from has not been updated and still only contains the old kernel. Can you show us the partitions of your drives with lsblk -o NAME,FSTYPE,SIZE,UUID (ESP partitions are vfat 512M)?

As a side note: this can probably be fixed by running dpkg-reconfigure locales and selecting en_US.UTF-8 and maybe you local locale.
Click to expand...
 
iprigger said:
Code: 
# cat /etc/kernel/proxmox-boot-uuids
2025-74B9
2025-D0CE

and

# lsblk -o NAME,FSTYPE,SIZE,UUID
NAME   FSTYPE       SIZE UUID
sda               223.6G
|-sda1             1007K
|-sda2 vfat         512M 6DF4-519B
`-sda3 zfs_member 223.1G 11576862949081681133
sdb               223.6G
|-sdb1             1007K
|-sdb2 vfat         512M 6E2E-4A8C
`-sdb3 zfs_member 223.1G 11576862949081681133
Click to expand...
As you can see there are no ESP partitions (vfat 512M) with UUID 2025-74B9 or 2025-D0CE. There are however ESP partitions with UUID 6DF4-519B and 6E2E-4A8C. I don't know which one is used for booting but I do think it validates my theory. I have no idea how the wrong UUIDs got into that file (maybe copied from another system?).

Please remove those two lines from /etc/kernel/proxmox-boot-uuids, as suggested and then add the existing ESP partitions (/dev/sda2 and /dev/sdb2) using proxmox-boot-tool.
 
  • Like
Reactions: frankd
Hi,

Ok.
leesteken said:
As you can see there are no ESP partitions (vfat 512M) with UUID 2025-74B9 or 2025-D0CE. There are however ESP partitions with UUID 6DF4-519B and 6E2E-4A8C. I don't know which one is used for booting but I do think it validates my theory. I have no idea how the wrong UUIDs got into that file (maybe copied from another system?).

Please remove those two lines from /etc/kernel/proxmox-boot-uuids, as suggested and then add the existing ESP partitions (/dev/sda2 and /dev/sdb2) using proxmox-boot-tool.
Click to expand...

So the steps would be:
- Remote the lines from /etc/kernel/proxmox-boot-uuids (no, that was not copied... probably got mangled during an update?)

What do you mean with "add existing ESP Partitions" using proxmox-boot-tool?

Do you mean:
proxmox-boot-tool format /dev/sda2
proxmox-boot-tool format /dev/sba2

~# lsblk -o +FSTYPE
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT FSTYPE
sda 8:0 1 223.6G 0 disk
|-sda1 8:1 1 1007K 0 part
|-sda2 8:2 1 512M 0 part vfat
`-sda3 8:3 1 223.1G 0 part zfs_member
sdb 8:16 1 223.6G 0 disk
|-sdb1 8:17 1 1007K 0 part
|-sdb2 8:18 1 512M 0 part vfat
`-sdb3 8:19 1 223.1G 0 part zfs_member

Tobias
 
iprigger said:
Hi,

Ok.


So the steps would be:
- Remote the lines from /etc/kernel/proxmox-boot-uuids (no, that was not copied... probably got mangled during an update?)

What do you mean with "add existing ESP Partitions" using proxmox-boot-tool?

Do you mean:
proxmox-boot-tool format /dev/sda2
proxmox-boot-tool format /dev/sba2

~# lsblk -o +FSTYPE
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT FSTYPE
sda 8:0 1 223.6G 0 disk
|-sda1 8:1 1 1007K 0 part
|-sda2 8:2 1 512M 0 part vfat
`-sda3 8:3 1 223.1G 0 part zfs_member
sdb 8:16 1 223.6G 0 disk
|-sdb1 8:17 1 1007K 0 part
|-sdb2 8:18 1 512M 0 part vfat
`-sdb3 8:19 1 223.1G 0 part zfs_member

Tobias
Click to expand...

BTW: Just did the init on /dev/sdb2 and /dev/sda1

# cat /etc/kernel/proxmox-boot-uuids
6DF4-519B
6E2E-4A8C

Looks strange?

Tobias
 
iprigger said:
# cat /etc/kernel/proxmox-boot-uuids
6DF4-519B
6E2E-4A8C

Looks strange?
Click to expand...
Except that you keep mixing sdb2 with sba2 and sda2 with sda1 in your posts, it looks fine. If would have chosen format (--force), then the UUIDs would have changed, but init does not change them. Now your two ESP partitions are properly registered with proxmox-boot-tool. You could do a proxmox-boot-tool refresh and see it everything is OK, just to make sure before you reboot the system to verify that it works.
 
leesteken said:
Except that you keep mixing sdb2 with sba2 and sda2 with sda1 in your posts, it looks fine. If would have chosen format (--force), then the UUIDs would have changed, but init does not change them. Now your two ESP partitions are properly registered with proxmox-boot-tool. You could do a proxmox-boot-tool refresh and see it everything is OK, just to make sure before you reboot the system to verify that it works.
Click to expand...
Hi,

yes, sorry:

/dev/sda2 and /dev/sdb2 (tired from one hell of a week...)
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back