Proxmox fails to boot after loading initial ramdisk HPE DL360 Gen11

NCSyFry

Member
Dec 7, 2022
6
2
8
Fails to boot with error:

ASSERT [Mlx] /images/development/mohammedt/uefi_edk2_X64/MdePkg/Library/BaseLib/
CheckSum.c(46): Butter != ((void *) 0)

IMG_4336 Large.jpeg

Proxmox version 8.4.1

After some reboots, same error would result. The server was running firmware ROM version U54 2.44. I upgraded to Firmware version 2.60 and Proxmox booted first try after the cold boot. I'm posting this here for anyone else that may run into this as I couldn't find any info.
 
  • Like
Reactions: uzumo
Also... I ran into this issue again on one of the hosts after a reboot for proxmox updates, it was stuck at same screen and error as above.

I then shut the host down completely, fully shutdown, power it off, let the power drain, and boot it back up, the HPE pre boot BIOS initialization detected some "changes" and it rebooted itself - after which proxmox booted fine. I suspect the previous firmware update didn't fully finish, or detected something it needed to update...

Posting here for reference, as a new google/AI search on this topic only resulted in my own above post suggestions ha!

I'm also wondering if this issue is related to the EFI boot host settings - I bet legacy boot config with the host wouldn't have this issue...
 
Last edited: