Problem with booting UEFI - BIOS A40 version 2.72 and higher

[SupaHotFire]

Hello HPE Community,

I tried upgrading my servers last weekend to the latest BIOS version for my DL385 Gen10 servers (A40). Which is version 2.84, however, everything above version 2.72 results in my servers not booting into my OS (Proxmox 7/Debian11) in UEFI mode. 1 server has an older installation with just BIOS, which booted with the version 2.84 without any problems.

The UEFI installed servers hang on POST code 0034. Waited for 30 mins, but nothing happens. So I reverted back to BIOS version 2.68.

Does the community have the same problem? Or does HPE have any knowledge on why this is happening?

Thank you in advance!

Some infra info:

4x DL385 Gen10
1x installed in BIOS (Works) | Active BIOS: version 2.84 | Bootdisk: Single NVME SSD on LVM
3x installed under UEFI (Does not work) | Active BIOS: version 2.68 | Bootdisk: 2x NVME SSD on ZFS (Mirrored)
All running Proxmox 8 (Debian 12) now, but also not working on the upgraded version.
ILO 5: version 2.97

[Sebasbin]

Hi,

There are no known issue with the latest BIOS version. I would suggest checking the UEFI boot settings and change the boot order correctly.

If the issue persists, log a support case with HPE for further investigation 

[SupaHotFire]

Hello Sebasbin,

The BIOS POST freezes everything, even when F9 is pressed. I think the best option is to open a ticket then.

Thank you for your time.

[Lawl]

@SupaHotFire 

Hello,

Have you ever found what was causing this problem?

I have the exact same issue, although I am using a Microserver Gen 10 Plus.

Thank you!

[Vinky_99]

Good day!

You may give it a try to below instructions:

>> Review the release notes for BIOS versions 2.72 and higher to see if there are any specific changes or known issues related to UEFI booting. Manufacturers often provide detailed information in the release notes about compatibility and any potential issues.

>> Verify that your UEFI settings are configured correctly. Pay attention to settings related to boot order, secure boot, and any other UEFI-specific configurations. Ensure that UEFI boot is enabled and configured properly.

>> If your system has secure boot enabled, try disabling it to see if it resolves the booting issue. Secure Boot can sometimes cause compatibility problems, especially if the installed OS or boot loader is not signed with a trusted key.

>> Check if there is a UEFI firmware update available for your server. Sometimes, updating the UEFI firmware separately from the BIOS can address compatibility issues. Ensure you follow the Support instructions for updating the UEFI firmware.

>> Since you've identified that BIOS version 2.68 works without issues, consider using this version for the time being until a newer version is released that addresses the UEFI boot problem. Keep an eye on future BIOS updates and release notes for potential fixes.

>> If the issue persists and you cannot find a solution, it's recommended to contact HPE support. They may be able to provide specific guidance, assistance, or even a beta firmware version that addresses the problem.

>> If possible, test the BIOS updates on a non-production system first to identify if the issue is specific to your environment or if it's a more widespread problem.

Always be cautious when updating firmware or BIOS on production systems, and make sure to follow the manufacturer's guidelines and best practices. If in doubt, seek assistance from the HPE support.