ProLiant Servers - Netservers
1847507 Members
6668 Online
110265 Solutions
New Discussion

Warning: Considering an HPE Microserver? Proceed with caution—it's a tale of frustration!

 
WiFriendly
Advisor

Warning: Considering an HPE Microserver? Proceed with caution—it's a tale of frustration!

About nine months ago, I purchased two Microserver Gen10 v2 units, and to this day, I’ve been unable to get them to work properly. This journey has cost me three quarters of effort, hundreds of hours, and around $10,000. Despite all this, I have nothing to show for it but frustration.

UNSOLVABLE PROBLEM #1: NVMe Disk Installation Is Impossible

There’s no viable way to install an NVMe disk for the operating system on this machine. Here’s the evidence: cards like QNAP, Lenovo, and any card using ASMedia, Marvell, or similar chips, fail. They lead to BSOD errors under heavy loads, during benchmarks, or when rebooting the system. The issue is well-documented under the error NMI_HARDWARE_ERROR, and I’ve even posted about it on this board.

HPE technical support’s stance? "NVMe isn’t meant for Microservers. Install the OS on an HDD." This response completely ignores the fact that there are only four HDD bays, primarily designed for RAID configurations, leaving no space for the OS. Why would customers need a disk for the OS? Apparently, HPE doesn’t think it’s necessary.

The support team in India neither investigated nor escalated the issue to engineers or development teams. Despite my extensive efforts—including detailed AHS logs, Windows kernel dumps, low-level error screenshots, videos, and dozens of other files—the case was quickly closed. Hours of my time were dismissed in seconds. Although the support team persistently requested my phone number, they never called me.

HPE system case number: 5382013385

UNSOLVABLE PROBLEM #2: Excessive Noise Caused by the HPE Accessory

After countless attempts, I found one controller that supports stable NVMe functionality: the HPE NS204i-p. While it works reliably, installing it causes the server fan to run at 100% speed, making it sound like a jet engine. The fan starts at 20% speed but increases steadily, reaching full speed within 1 hour.

I’ve provided logs, screenshots, and hardware analysis files, yet the advice I received was unhelpful at best. Suggestions included removing the AMS program or replacing my Western Digital (WD) drives with overpriced HPE drives. Neither solution worked. Eventually, I was told to remove the NS204i-p controller entirely, as it’s "not compatible."

Ironically, third-party controllers from Lenovo, QNAP, and Dell don’t cause fan issues. This indicates a deliberate vendor lock-in mechanism, akin to proprietary restrictions in laptops with Wi-Fi cards. The excessive noise isn’t just inconvenient—it also accelerates dust buildup, potentially damaging the hardware within months.

Resolving this issue likely requires BIOS/UEFI or iLO firmware updates. However, like before, HPE guys from India support did not investigate or escalate the problem. My case, filled with logs, screenshots, and analysis, was again dismissed within seconds.

HPE system case number: 5386472125

UNSOLVABLE PROBLEM #3: Dysfunctional RAID5 Performance

I configured a RAID5 array using Intel/HPE VROC, only to discover that write speeds were 50–100 times slower than with standalone HDDs. Write speeds dropped to as low as 0.45 MB/s for small files and peaked at just 20 MB/s for large files. In comparison, the same disks in AHCI or non-RAID VROC mode achieve speeds of 250–450 MB/s.

HPE support initially blamed SMR drives, even though I was using CMR drives. They then suggested configuring parameters like write-cache and battery settings, which are irrelevant for this setup. Despite my requests for clarification, they provided links to guides for hardware RAID controllers—irrelevant, as Microservers don’t support them.

The issue was ultimately resolved by switching to Non-RAID or AHCI mode, which restored write speeds to 220–250 MB/s. No new hardware or drastic changes were needed, just proper testing and troubleshooting. Nevertheless, HPE India support did not investigate or escalate the issue, repeating the same pattern of dismissive behavior.

HPE system case number: 5386472065

There is also a thread on this board that briefly covers issues 2 and 3.

SUMMARY

After nine months, both servers remain non-functional despite substantial investment in time and money. My experience with HPE hardware—and particularly their technical support—has been profoundly disappointing.

  • I’ve incurred significant losses of time and resources.
  • The warranty, which is soon expiring, has proven to be effectively useless.
  • HPE’s approach to customer support and product reliability has eroded my trust in the brand.

I strongly urge others to reconsider engaging with HPE. Their approach to problem-solving resembles that of a typical low-cost vendor: “We sold the problem, and now it’s yours.”

OBSERVATIONS ABOUT HPE TECHNICAL SUPPORT

Based on my experience, HPE India support operates as a facade rather than a true technical assistance team:

  • Competence: Support staff appear to lack relevant training and expertise, offering advice anyone could find online.
  • Accountability: Cases are closed hastily without meaningful investigation or resolution.
  • Communication: Promises to escalate issues are never fulfilled, and there’s no interaction with engineers or testing teams.
  • Access: Support teams don’t have access to hardware, even remotely, leaving them ill-equipped to resolve issues.

This ineffectiveness tarnishes HPE’s reputation and undermines their legacy as a once-great technology company.

To say I’m disappointed is an understatement. HPE seems to be on the same downward trajectory as other once-leading brands, prioritizing short-term gains over long-term quality and customer satisfaction.

Farewell, HPE. Once a leader, now a shadow of its former self.

1 REPLY 1
Sunitha_Mod
Honored Contributor

Re: Warning: Considering an HPE Microserver? Proceed with caution—it's a tale of frustrati

Hi @WiFriendly

We regret the inconvenience caused. The concerned team has been notified and they are looking into the issue as a priority.