I am trying to install Proxmox on my HP Proliant DL360p Gen8. I could only get the iso to run through the iLO's Virtual Media. I have removed all storage except for the 500GB SSD that is housed in a case and coverts the SATA to USB. I have tested this with another OS and the drive will boot. I did a default install to the SSD. It goes through the whole install and does the reboot. I have the BIOS set to boot to the internal USB port first then Hard drive. The system doesn't see the boot on the drive and just cycles trying to find something to boot from. I then boot to the ISO again and tried the Rescue Boot option, but it it also says it cannot find the boot disk.
I have seen other posts that referenced HP servers, but they are configured differently than how I have mine.
I am not using ZFS or using HBA mode on the RAID controller.
I plan to eventually switch the SSD enclosure for a SATA to mSATA cable and connect it to the internal SATA port the CD/DVD drive would have used.
The BIOS is the most current for this server.
I have used Gparted Live to access the SSD. It has the three partitions that are associated with this version of Proxmox, so one of them contains the BIOS/Grub and another the EFI. From what I have read this generation of this server doesn't support UEFI only Legacy. I am thinking that this could be the issue. Is there a way to covert the EFI to legacy boot?
I have seen other posts that referenced HP servers, but they are configured differently than how I have mine.
I am not using ZFS or using HBA mode on the RAID controller.
I plan to eventually switch the SSD enclosure for a SATA to mSATA cable and connect it to the internal SATA port the CD/DVD drive would have used.
The BIOS is the most current for this server.
I have used Gparted Live to access the SSD. It has the three partitions that are associated with this version of Proxmox, so one of them contains the BIOS/Grub and another the EFI. From what I have read this generation of this server doesn't support UEFI only Legacy. I am thinking that this could be the issue. Is there a way to covert the EFI to legacy boot?