HP DL380 with MR408i

randy144

New Member
Jul 25, 2025
4
0
1
Trying to set up Proxmox 8.4 (or 8.3) on an HP DL380. Have one box up and running but on the second box the drive config is not working. Have the boot drive set to two 2.4 SAS in Raid1 on the hardware controller. Everything works fine, boots sees the storage correctly and if that is the only drive configured it shows as SDA. Configure additional drives in RAID5 on the same machine. Proxmox sees the drives but will not set GPT (throws errors). When the RAID5 is added Proxmox sees that array as SDA and moves the boot to SDB. I think that is the issue but have no idea how to fix it. I am basically a newbie. Sorry.
 
Forgot to mention that the first DL380 is working great! Configured exactly the same and the 2.4T boot drive shows as SDA and the RAID5 drive shows as SDB.
 
Some time ago I added also a second array to HPE Proliant. To be honest, I did not probably even remember that Proxmox has those disk tools in gui. I think I went straight to command line and did fdisk /dev/sdX (add your newly created raid device here) and added a partition with all defaults. Maybe that initializes the drive in a way that it can be then managed also via gui.
 
Last edited:
Friends don’t let friends use RAID5 :-)

The order of the boot disks presented to the OS with a UEFI system is configured in the UEFI, you can change the order there. Compare the configurations and make adjustments after both RAID have been setup. A better way would be to let ZFS handle both the boot mirror and the disks (RAIDZ2 or mirrors) rather than rely on a proprietary RAID.
 
Thanks. I have tried fdisk and gdisk and have gotten no where. I think the problem is that Proxmox is somehow confusing SDA and SDB because there was a message about an MBR partition (not even sure where that came from). Blew away that by creating a new partition but Proxmox wants to create a 2TB partition in fdisk but even that doesn't work as the RAID5 drive will still not add GPT. The RAID5 is 12TB in size and is listed like that in the GUI.
 
The sda/sdb is defined by the Linux kernel and some other tools, it has nothing to do with Proxmox, a just means the first enumerated disk, b the second, c the third etc. It is there for legacy purposes.

If the order changes, the system should still boot but you need to be aware of the change and a good practice is to use disk uuid instead of the enumeration in eg fstab.

Basically don’t use the /dev/sda alias, use /dev/disk/by-uuid or something similar.

Enumeration happens by your UEFI/firmware/RAID controller, if you want to change the enumeration, that is where to change it.
 
Last edited:
Also, to be clear, Proxmox boots fine with the RAID5 drive added. It simply moves the boot drive to SDB sets the 12TB partition as SDA with no GPT. In the working Proxmox server (identical config) the boot drive is SDA and the 12TB drive is SDB.