Proxmox VE 9.1 installs successfully but server cannot find bootable disk (HP Proliant DL380e Gen8)

[TeNux]

Hello,


I am trying to install Proxmox VE 9.1 (proxmox-ve_9.1-1.iso) on an HP Proliant DL380e Gen8 server.


I created a bootable USB installer and started the installation using the Graphical Install option.


During the installation:

• I followed all the installation steps normally.
• For the disk selection, I chose the first disk in rack 1 (2TB).
• The installation process completes without any errors.

At the end of the installation, the server reboots as expected. However, after reboot the server cannot find any bootable disk.


The system displays something similar to:

No bootable device found.

However, when I boot again from the USB installer, the installer detects that Proxmox is already installed on the disk, which confirms that the installation actually completed successfully.

Troubleshooting already attempted​

• Installed directly on the disk (no RAID).
• Created a logical RAID volume using the server RAID controller and installed Proxmox on it.
• Reinstalled Proxmox multiple times.
• Checked disk selection during installation.
• Tried several suggested troubleshooting steps but none solved the issue.

In all cases, the installation finishes correctly, but the server still cannot boot from the disk.

Hardware​

Server: HP Proliant DL380e Gen8
Disk: 2TB drive (first disk in rack 1)
Installation media: USB

Question​

Has anyone encountered this issue before with HP Proliant Gen8 servers?


Could it be related to:

• Legacy BIOS vs UEFI mode
• Boot loader installation
• RAID controller configuration
• HP Smart Array settings

Any suggestions on what to check or test would be greatly appreciated.


Thank you!

 

[_gabriel]

iirc, these old box have problem booting off raid controller.
put proxmox ve boot disk to internal sata

 

[SteveITS]

Legacy BIOS vs UEFI mode

I haven't used HP hardware, however, I have experienced where booting the installer in legacy vs UEFI mode affected whether it would boot correctly after. In our case we had mounted the ISO remotely, and both methods were separate choices for the same ISO in the boot menu. If you see both, try the other one.