Gen10+ Hardware Validation tool "There Has Been an Error. Please try again"

[Mike Texter]

Hi, 

Trying to run some diags & gather hardware logs on a DL380 Gen10+ via Intelligent Provisioning.  I Recently ran the September 2025 SPP and IP 3.91 updates, and when I go into the Hardware Validation tool, a task i've done literally thousands of times on other models, it shows "There Has Been an Error. Please try again".  Behavior persists after reboot & flea power drain.  Tried before & after running the initial setup wizard, same behavior.  UEFI Firmware 2.50.  No network connections present other than iLO, and no OCP, backplane, PCI riser or controller installed.  

What should I try next?  I'm hearing reports that rolling IP back to 3.90 might work better.  Any input is appreciated.

[Mike Texter]

rolled back to 3.90, same behavior.  Ran system erase via Intelligent Provisioning, same behavior. Cool robot graphic though.  BLURP... BLOOOP ZUURRRP #$@&%*! BRRZZZ!

[Mike Texter]

Am I the only one who still runs the HVT?  Has anyone else succeeded in launching it on a Gen10+ server?  I ended up using the embedded diags from the F9 menus.

[Azr_geek]

Hello @Mike Texter,

Since you’ve already done power-drain and reboot, here are a few checks to make sure something simple isn’t blocking the tool:

1. Ensure version match/compatibility: According to the user guide, for Gen10 servers, the embedded partition for Intelligent Provisioning requires specific iLO/BIOS levels. For example: “Note: Intelligent Provisioning 3.40 and later requires iLO firmware version 2.10 or later.” itpfdoc.hitachi.co.jp+1 Make sure your iLO version is at or above the required version for your IP version.
   
   

2. Check NVRAM / Intelligent Provisioning enablement – In previous examples with Gen10/Gen9, issues with IP stem from NVRAM corruption or IP being disabled in BIOS/Platform Configuration or iLO state. HPE Community+2HPE Community+2 Ensure in the RBSU (BIOS/Platform config) that “Intelligent Provisioning (F10 Prompt)” is enabled. On some servers, IP fails or shows “error” if the embedded Linux partition is corrupted.

3. Check logs / iLO messages – Review the Integrated Management Log (IML) in iLO for underlying HW errors or firmware flash failures. Also, record exactly when the “There has been an error. Please try again” appears (right when the tool launches, right after discovery, etc.). Knowing the precise step helps.

4. Other tool dependencies – Because you mention no backplane/pci/riser/controller installed, ensure the Server isn’t in a weird “unpopulated” state (which isn’t normally a blocker, but sometimes tools expect at least something). Also, check whether any network connection is required for IP to run validation tools (sometimes IP or HVT may expect network connectivity or certain services). Though your description indicates only iLO is up, you might test connecting a network port or assigning an IP to the “Network” interface of IP tool (if applicable).
   
   Regards,
   Azr_geek

[Mike Texter]

Thank you for this, I have an OCP coming soon, and may end up getting a PCIe riser as well, just to rule those out as culprits.  

1. Versions are good, System ROM is U46 v2.50 (08/06/2025) & iLO is 3.15

2. This all looks good

3. No messages indicating a flash failure, the error appears at the end of discovery

4. I will report back after getting more pieces in place.  If the OCP doesn't fix it, I will add a PCIe riser, backplane, controller & cache battery, etc.

Thank you!

[BPSingh]

Greetings!

Could you confirm if this issue started occurring after updating the IP to version 3.91?

Please try reflashing the IP and verify if the issue persists. For testing purposes, you can also downgrade to the previous (n-1) version and check.

https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-6971bdef1d494491&tab=revisionHistory

[Mike Texter]

Negative, the issue was present at 3.90 as well (before I had updated to 3.91, I tested at 3.90 with same behavior).  Still haven't had a chance to try with OCP & risers installed, but will report back asap.