I have a Dell T440 that is running production workloads with
CPU : 64 x Intel(R) Xeon(R) Silver 4216 CPU @ 2.10GHz (2 Sockets)
Ram: 16 x 16GB DDR4 ECC Dual rank 2400MT/s (256GB total)
Kernel Version: Linux 6.14.8-2-pve (2025-07-22T10:04Z)
Boot Mode: EFI
Manager Version: pve-manager/9.0.6/49c767b70aeb6648
Repository Status: Proxmox VE updates, Production-ready Enterprise repository enabled
Bios: (2.24.0)
iDrac Firmware: (7.00.00.174) latest is (7.00.00.182)
PCIE nic: Intel(R) Ethernet Converged Network Adapter X550-T2
PCIe HBA: DELL HBA330 (0J7TNV)
I ran the
After getting the failure for the systemd-boot I ran the following to install the efi and boot-tools and remove the systemd-boot per the recommendations
After that from the web interface i click the reboot. Proxmox seemed to shutdown cleanly but the system never came back up. after roughly 30 min of waiting i login to the idrac and forced a cold boot and the system came back up. I did more testing I am able to shutdown and the systems responds correctly and shutsdown. I am able to power the systems up and it responds correctly and all the VM's seem to run just fine. But when I using the reboot proxmox shuts down but the systems never resets and starts back up I have to login to the idrac and force the restart. Any ideas as to what the issue might be?
CPU : 64 x Intel(R) Xeon(R) Silver 4216 CPU @ 2.10GHz (2 Sockets)
Ram: 16 x 16GB DDR4 ECC Dual rank 2400MT/s (256GB total)
Kernel Version: Linux 6.14.8-2-pve (2025-07-22T10:04Z)
Boot Mode: EFI
Manager Version: pve-manager/9.0.6/49c767b70aeb6648
Repository Status: Proxmox VE updates, Production-ready Enterprise repository enabled
Bios: (2.24.0)
iDrac Firmware: (7.00.00.174) latest is (7.00.00.182)
PCIE nic: Intel(R) Ethernet Converged Network Adapter X550-T2
PCIe HBA: DELL HBA330 (0J7TNV)
I ran the
pve8to9 --full before the upgrade. The only warnings were to migrate or stop the running VM'a and to update the intel microcode. I updated the microcode using/adding the "non-free-firmware" repos. After rebooting I stopped all of the running VM's and preformed a backup of each to my PBS. I then followed the pve8to9 instructions. After preforming the apt update and apt upgrade I ran the pve8to9 again and received the following log with 3 warnings (storage and old kernel) and 1 failure (systemd-boot).
Code:
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
PASS: all packages up-to-date
Checking proxmox-ve package version..
PASS: already upgraded to Proxmox VE 9
Checking running kernel version..
WARN: a suitable kernel (proxmox-kernel-6.14) is installed, but an unsuitable (6.8.12-13-pve) is booted, missing reboot?!
= CHECKING CLUSTER HEALTH/SETTINGS =
SKIP: standalone node.
= CHECKING HYPER-CONVERGED CEPH STATUS =
SKIP: no hyper-converged ceph setup detected!
= CHECKING CONFIGURED STORAGES =
storage 'VMBackups' is not online
PASS: storage 'FAST10' enabled and active.
PASS: storage 'PBS' enabled and active.
WARN: storage 'VMBackups' enabled but not active!
PASS: storage 'local' enabled and active.
PASS: storage 'local-zfs' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
WARN: activating 'VMBackups' failed - storage 'VMBackups' is not online
PASS: no storage re-uses a directory for multiple content types.
storage 'VMBackups' is not online
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 =
SKIP: Skipping check for running guests - already upgraded.
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
PASS: systems seems to be upgraded and LXCFS is running with FUSE 3 library
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
PASS: All VM machine versions are recent enough
= 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 'SERVERNAME' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '10.20.20.10' 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)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 >= 2048)
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: none of the 1 custom roles need handling
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 issues on upgrades of boot-related packages. Install 'systemd-boot-efi' and 'systemd-boot-tools' explicitly and remove 'systemd-boot'
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!
storage 'VMBackups' is not online
INFO: Check for LVM autoactivation settings on LVM and LVM-thin storages...
PASS: No problematic volumes found.
INFO: Checking lvm config for thin_check_options...
PASS: Check for correct thin_check_options passed
INFO: Check post RRD metrics data format migration situation...
PASS: No old RRD metric files found, normally this means all have been migrated.
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' is not present.
INFO: Checking if matching CPU microcode package is installed.
PASS: Found matching CPU microcode package 'intel-microcode' installed.
SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter
= SUMMARY =
TOTAL: 46
PASSED: 36
SKIPPED: 6
WARNINGS: 3
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.After getting the failure for the systemd-boot I ran the following to install the efi and boot-tools and remove the systemd-boot per the recommendations
Code:
apt install systemd-boot-efi systemd-boot-tools
apt remove systemd-boot
proxmox-boot-tool refreshAfter that from the web interface i click the reboot. Proxmox seemed to shutdown cleanly but the system never came back up. after roughly 30 min of waiting i login to the idrac and forced a cold boot and the system came back up. I did more testing I am able to shutdown and the systems responds correctly and shutsdown. I am able to power the systems up and it responds correctly and all the VM's seem to run just fine. But when I using the reboot proxmox shuts down but the systems never resets and starts back up I have to login to the idrac and force the restart. Any ideas as to what the issue might be?
Code:
root@SERVERNAME:~# cat /proc/cmdline initrd=\EFI\proxmox\6.14.8-2-pve\initrd.img-6.14.8-2-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs