Think I am finally making some progress
I first found there was a BIOS update available for my server - went from a 2015 version to a 2021 version - thought it couldn't be a bad thing.
I loaded the BIOS update onto a USB as per Lenovo instructions. When I went to boot this, the system recognised it as a UEFI bootable disk - it booted fine and ran the update.
I then tried to boot Proxmox installer again with the updated firmware, however, it still only recognised my USB as Legacy bootable. At this point I figured there MUST be something wrong with my Proxmox USB, created with Rufus. So I tried with Ventoy instead, and was able to boot the installer in UEFI. After install, I rebooted to the BIOS, double checked the boot mode was set to UEFI Only (no possibility of booting Legacy), and sure enough, PVE started right up.
I then got a bit confused double checking if it was certainly using EFI and systemd-boot. I read this thread (
https://forum.proxmox.com/threads/h...x-is-booting-with-grub-or-systemd-boot.67020/), and checked for the existence of "/etc/kernel/pve-efiboot-uuids" - it is not there.
However, the system must be booting in UEFI, as the firmware is set to UEFI only. Also, the bootloader visually appears to be the systemd one, not Grub (it is very plain and black).
Additionally this looks to confirm UEFI is being used:
Code:
root@pve2:/sys/firmware/efi# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
0323-2B2A is configured with: uefi (versions: 6.17.2-1-pve)
0324-3625 is configured with: uefi (versions: 6.17.2-1-pve)
So I think all is good. Thanks for everyone's help.
Now I just need to make 100% sure the boot partitions are automatically sync'ed to both boot disks (so it can still boot if one fails), I think it does, and also sort out this message which I get on the console:
Code:
kvm_intel: L1TF CPU bug present and SMT on, data leak possible.