Proxmox 8.3 Installation Issue on ProLiant DL380 Gen9

nhtossyi

New Member
Feb 21, 2025
6
0
1
Hello,
I am trying to install Proxmox 8.3 on a ProLiant DL380 Gen9. I created a USB installation media using Rufus and successfully installed the OS, but after rebooting, the OS did not start, and the installer appeared again.

In the One-time Boot menu, there was an option for Proxmox, so I selected it, but the System Utilities screen appeared immediately, and the OS did not boot.

How can I boot the installed Proxmox?

ProLiant configuration:​

  • CPU: Xeon E5-2630 v3 × 1
  • Memory: 16GB
  • Storage: 4 × 2TB SSD (RAID10)
This text was created using a translation tool...
 
Hello nhtossyi! Most probably the boot order in the BIOS is set to boot from the USB stick first, so the installer starts again. In your case it is probably the easiest if you simply unplug the USB stick from the system - if the installation was successful, Proxmox VE should then start correctly.
 
What is configured in the boot order menu of the BIOS?

At this point, it probably either means that booting from the disk is disabled for whatever reason, or the installation has failed. But checking the boot order is important, just to be sure.

In the One-time Boot menu, there was an option for Proxmox, so I selected it, but the System Utilities screen appeared immediately, and the OS did not boot.
I thought that the "option for Proxmox" was the USB stick with the Proxmox VE installer. So you tried to boot from the disk (while the USB stick was unplugged), but it failed?
 
The current boot options are as follows:

  • proxmox
  • Generic USB Boot
  • Embedded FlexibleLOM 1: Port 1: HP Ethernet 1Gb 4-port 331 FLR Adapter - NIC (PXE IPv4)
  • Embedded LOM: Port 1: HP Ethernet 1Gb 4-port 331 FLR Adapter - NIC (PXE IPv4)
  • Embedded FlexibleLOM 1: Port 1: HP Ethernet 1Gb 4-port 331 FLR Adapter - NIC (PXE IPv6)
  • Embedded LOM: Port 1: HP Ethernet 1Gb 4-port 331 FLR Adapter - NIC (PXE IPv6)
  • Front USB 2: (USB with the installer)
I selected proxmox, thinking that it was the boot option for the installed OS.
 
What is configured in the boot order menu of the BIOS?

At this point, it probably either means that booting from the disk is disabled for whatever reason, or the installation has failed. But checking the boot order is important, just to be sure.


I thought that the "option for Proxmox" was the USB stick with the Proxmox VE installer. So you tried to boot from the disk (while the USB stick was unplugged), but it failed?
Yes, I tried operating with the USB removed, but it failed.
(I have deleted the posts that were not translated.)
 
Alright, thanks for the information. Yes, proxmox is the correct option to select when booting. Being the first in the boot order list means that it should theoretically boot correctly. Don't you see any other error or anything?

Could you please give us some information about:
  1. What filesystem did you select during the installation?
  2. Are you using hardware RAID? This is especially important if you use ZFS, because the documentation states that
ZFS on top of any hardware RAID is not supported and can result in dataloss.
 
Alright, thanks for the information. Yes, proxmox is the correct option to select when booting. Being the first in the boot order list means that it should theoretically boot correctly. Don't you see any other error or anything?

Could you please give us some information about:
  1. What filesystem did you select during the installation?
  2. Are you using hardware RAID? This is especially important if you use ZFS, because the documentation states that
Thank you for your response.

No errors are displayed, but if the USB is inserted when the server starts, the installer launches. If the USB is removed, the system attempts to boot from the LAN or DVD drive. However, since there is nothing available, the UEFI page is eventually displayed.

From there, I tried selecting Proxmox to boot, but it did not work. The file system selected during installation was EXT4.

Additionally, I am using four SSDs configured in a RAID 10 hardware array.
 
Could you please check if:
  1. It makes any difference whether 'Legacy boot' or CSM is enabled or disabled in the BIOS.
  2. If disabling Secure Boot in the BIOS improves the situation (note: while Proxmox VE supports Secure Boot, it can be worth trying to disable it and see if it helps).
  3. If it works to install and boot the latest version of Debian. It would be interesting for testing whether it improves the situation, but if it works, you can also install Proxmox VE on Debian - see the docs and the wiki page.
 
Could you please check if:
  1. It makes any difference whether 'Legacy boot' or CSM is enabled or disabled in the BIOS.
  2. If disabling Secure Boot in the BIOS improves the situation (note: while Proxmox VE supports Secure Boot, it can be worth trying to disable it and see if it helps).
  3. If it works to install and boot the latest version of Debian. It would be interesting for testing whether it improves the situation, but if it works, you can also install Proxmox VE on Debian - see the docs and the wiki page.
Currently, I am attempting to boot with Legacy Boot disabled.

Secure Boot was originally disabled. I tried enabling it and booting, but the result was the same.

Additionally, I attempted to install Debian, but I encountered the exact same situation.

Is it likely that this is an issue on the ProLiant side?