bootx64.efi but not grubx64

Sep 26, 2023
112
12
23
Hello.
i've been trying to do the upgrade from 8-9 and keep running into the fail issue: systemd-boot meta-package installed....remove 'systemd-boot' .
i've checked/installed grub - no issues
ran the efibootmgr -v cmd looking for grubx64 but am not seeing it - only this:

does this mean that for some reason grub isn't in use - and if how, how can i correct this?

full msg at the bottom whenever i ran the pve8to9 --full.

root@pve:~# efibootmgr -v
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0003,0006,0000,0004,0001,0002,0007
Boot0000* proxmox HD(2,GPT,0d6f79f1-4e98-4efe-94ad-6baf8496be5b,0x800,0x200000)/File(\EFI\PROXMOX\SHIMX64.EFI)
Boot0001 Network Card BBS(Network,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0600)..GO..NO..........I.B.A. .G.E. .S.l.o.t. .0.4.0.0. .v.1.4.0.4...................\.,.@.r.d.=.X...............rN.D+..,.\...........B..Gd-.;.A..MQ..L.I.B.A. .G.E. .S.l.o.t. .0.4.0.0. .v.1.4.0.4........BO
Boot0002 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0003* proxmox HD(2,GPT,0d6f79f1-4e98-4efe-94ad-6baf8496be5b,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)
Boot0004* Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........H.G.S.T. .H.U.S.7.2.8.T.8.T.A.L.E.6.L.4...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.A.V.B.G.0.B.L.4. . . . . . . . . . . . ........BO..NO..........H.G.S.T. .H.U.S.7.2.8.T.8.T.A.L.E.6.L.4...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.A.V.B.G.S.2.L.8. . . . . . . . . . . . ........BO..NO..........H.G.S.T. .H.U.S.7.2.8.T.8.T.A.L.E.6.L.4...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.A.V.B.G.0.B.L.W. . . . . . . . . . . . ........BO..NO..........S.a.m.s.u.n.g. .S.S.D. .8.4.0. .S.e.r.i.e.s...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.1.S.H.9.S.N.D.A.8.5.9.2.3.3. .B. . . . ........BO..NO..........H.G.S.T. .H.U.S.7.2.8.T.8.T.A.L.E.6.L.4...................\.,.@.r.d.=.X..........A.................................>..Gd-.;.A..MQ..L.A.V.B.G.V.A.L.M. . . . . . . . . . . . ........BO
Boot0006* UEFI OS HD(2,GPT,0d6f79f1-4e98-4efe-94ad-6baf8496be5b,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0007 USB HDD BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0900)..GO..NO........o.S.e.a.g.a.t.e. .E.x.p.a.n.s.i.o.n. .D.e.s.k. .0.9.0.9...................\.,.@.r.d.=.X..........A.............................&..Gd-.;.A..MQ..L.N.A.8.E.Y.W.6.M........BO


root@pve:~# dpkg -l | grep systemd-boot
ii systemd-boot 252.39-1~deb12u2 amd64 simple UEFI boot manager - tools and services
ii systemd-boot-efi:amd64 252.39-1~deb12u2 amd64 simple UEFI boot manager - EFI binaries
root@pve:~#


full report -
root@pve:~# pve8to9 --full
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-ve package version..
PASS: proxmox-ve package has version >= 8.4-0

Checking running kernel version..
PASS: running kernel '6.8.12-37-pve' is considered suitable for upgrade.

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.
PASS: storage 'localzfs' enabled and active.
PASS: storage 'nocpbr' enabled and active.
PASS: storage 'syn-151' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage re-uses a directory for multiple content types.
INFO: Check for usage of native GlusterFS storage plugin...
PASS: No GlusterFS storage found.
INFO: Checking whether all external RBD storages have the 'keyring' option configured
SKIP: No RBD storage configured.

= VIRTUAL GUEST CHECKS =

INFO: Checking for running guests..
WARN: 1 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
SKIP: not yet upgraded, no need to check the FUSE library version LXCFS uses
INFO: Checking for VirtIO devices that would change their MTU...
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking VM configurations for outdated machine versions
NOTICE: QEMU machine versions older than 6.0 are expected to be dropped during the Proxmox VE 9 release life cycle. For more information, see:
https://pve.proxmox.com/pve-docs/chapter-qm.html#qm_machine_type
and https://pve.proxmox.com/wiki/QEMU_Machine_Version_Upgrade
WARN: VMs with the following IDs have an old machine version configured. The machine version might need to be updated to be able to start the VM in Proxmox VE 9:
212

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvescheduler.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for supported & active NTP service..
PASS: Detected active time synchronisation unit 'chrony.service'
INFO: Checking if the local node's hostname 'pve' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '10.20.30.222' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 >= 2048 RSA)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048 RSA)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs
PASS: no custom roles defined
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
INFO: Checking if the suite for the Debian security repository is correct..
PASS: found no suite mismatch
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information.
INFO: Check for dkms modules...
SKIP: could not get dkms status
INFO: Check for legacy 'filter' or 'group' sections in /etc/pve/notifications.cfg...
PASS: No legacy 'filter' or 'group' sections found!
INFO: Check for legacy 'notification-policy' or 'notification-target' options in /etc/pve/jobs.cfg...
PASS: No legacy 'notification-policy' or 'notification-target' options found!
INFO: Check for LVM autoactivation settings on LVM and LVM-thin storages...
NOTICE: storage 'local-lvm' has guest volumes with autoactivation enabled
NOTICE: Starting with PVE 9, autoactivation will be disabled for new LVM/LVM-thin guest volumes. This system has some volumes that still have autoactivation enabled. All volumes with autoactivations reside on local storage, where this normally does not cause any issues.
You can run the following command to disable autoactivation for existing LVM/LVM-thin guest volumes:

/usr/share/pve-manager/migrations/pve-lvm-disable-autoactivation

INFO: Checking lvm config for thin_check_options...
PASS: Check for correct thin_check_options passed
INFO: Check space requirements for RRD migration...
PASS: Enough free disk space for increased RRD metric granularity requirements, which is roughly 43.42 MiB.
INFO: Checking for IPAM DB files that have not yet been migrated.
PASS: No legacy IPAM DB found.
PASS: No legacy MAC DB found.
INFO: Checking if the legacy sysctl file '/etc/sysctl.conf' needs to be migrated to new '/etc/sysctl.d/' path.
PASS: Legacy file '/etc/sysctl.conf' exists but does not contain any settings.
INFO: Checking if matching CPU microcode package is installed.
PASS: Found matching CPU microcode package 'amd64-microcode' installed.

= SUMMARY =

TOTAL: 46
PASSED: 35
SKIPPED: 5
WARNINGS: 2
FAILURES: 1

ATTENTION: Please check the output for detailed information!
Try to solve the problems one at a time and then run this checklist tool again.