Request a quote — built to order from tested, warrantied stock.
The HPE ProLiant DL380 Gen11 is a refurbished 2U Rack server (Gen11) for the 4th Gen Intel Xeon Scalable, 5th Gen Intel Xeon Scalable, DDR5 · up to 8192 GB · 32 DIMM slots · up to 5600 MT/s · 8 channels per CPU · ECC. Drive layouts: 8SFF (SAS/SATA/NVMe); 24SFF (SAS/SATA/NVMe); 8LFF; 12LFF; 12EDSFF (NVMe). Every unit is tested, warrantied and shipped from Canada; configure it online with parts that are checked for compatibility.
Best for: storage, virtualization, database.
| Form factor | 2U Rack |
|---|---|
| Generation | Gen11 |
| CPU | 2 socket(s) · 4th Gen Intel Xeon Scalable, 5th Gen Intel Xeon Scalable · LGA4677 · up to 64 cores per CPU · max 385 W TDP |
| Memory | DDR5 · up to 8192 GB · 32 DIMM slots · up to 5600 MT/s · 8 channels per CPU · ECC |
| Drive bays | 8SFF (SAS/SATA/NVMe); 24SFF (SAS/SATA/NVMe); 8LFF; 12LFF; 12EDSFF (NVMe) |
| Storage controllers | Intel VROC SATA for HPE ProLiant Gen11, Intel VROC NVMe for HPE ProLiant Gen11, HPE Smart Array E208e-p SR Gen10 Controller, HPE MR416i-p Gen11 Controller, HPE MR416i-o Gen11 Controller, HPE MR216i-p Gen11 Controller |
| PCIe | Gen 5.0 · 8 slots · 8× x16 |
| Networking | OCP 3.0 slot |
| GPU | up to 6 GPUs · 3 double-width |
| Power | 1800W Titanium, 2200W Titanium, 1600W Platinum, 1000W Titanium, 800W Platinum · redundant · hot-swap |
| Management | iLO 6 · iLO 6 Standard |
| Cooling | ASHRAE A4 · hot-swap fans |
Real parts from our catalog for this chassis, priced from live market listings and vendor offers:
Chassis pricing is quoted by our team; component prices come from live market listings and vendor offers and are refreshed nightly. Lines without market evidence are quoted by our team.
To fix the 'Base System Device' issue, download and install the Intel chipset driver from the HPE Support Center for your ProLiant DL380 Gen11. Alternatively, you can use the HPE Service Pack for ProLiant (SPP) to automatically install the necessary drivers. After installation, reboot the server and check Device Manager to ensure the devices are correctly identified. [community thread]
After updating the SPP, check the BIOS or UEFI settings as they may have been altered. Resetting to default settings could resolve the issue. Additionally, if using iLO for remote management, ensure it is functioning properly and can access the server's console. [community thread]
Ensure that your server is updated with the latest HPE Service Pack for Proliant (SPP), as this can resolve drive detection issues. You can download the latest SPP from the HPE support website. [community thread]
The HPE Part Number P67095-B21, which features the Intel Xeon Gold 6530 processor, supports a maximum memory speed of 4800 MT/s. Although it is compatible with PC5-5600B and PC5-5200B memory modules, these will operate at the lower speed of 4800 MT/s due to the processor's limitations. [community thread]
To reduce noise, consider updating the System ROM to version 2.44 and ensuring all firmware and drivers are current with the latest SPP. Additionally, rearranging drives to increase spacing can help lower fan speeds, and adjusting the minimum fan speed settings in the iLO interface may also be beneficial. If noise remains a concern, using SATA SSDs can significantly decrease operational noise. [community thread]
The freezing issue is likely due to a mismatch between hardware, firmware, and drivers. To resolve this, ensure all firmware is updated to the latest versions, install the HPE SUSE Linux Driver Pack for SLES 15 SP7, and check system logs for any lockup errors. Additionally, apply any necessary SUSE kernel patches for SP7. [community thread]
This issue may be caused by post-deployment scripts, Group Policies, or security software interfering with Firefox. To troubleshoot, check for any scripts or policies that could be terminating the application, review Firefox's compatibility with Windows Server 2025, and examine deployment logs for errors. Additionally, consider disabling antivirus temporarily or testing a manual launch of Firefox after deployment. [community thread]
This issue is related to the Windows Secure Boot Database. To fix it, reboot the server and access System Utilities by pressing F9, then navigate to Server Security in the BIOS/Platform Configuration. Look for options to apply or restore the Secure Boot Database, apply the changes, and perform at least two full reboots to ensure synchronization. [community thread]