DL380 Gen 10 Boot errors

[WABAJABA]

We have a DL380 Gen10 that we just started to put together. We had purchased two DL380 Gen 10, for cost and space we decided to put the processors into one unit. We moved eveything over, I was pretty sure the processors where the same model. We got processor error not the same model number.

So I pulled everthing out for the 2nd processor. Moved all 8 sticks of 32G each ram to the one processor. Made sure they where in the proper slots. Rebooted and still get same problem and same errors. I have reset the UID holding it for 5 seconds and did hard reset holding it for 10 seconds. Still get the same errors.

Nothing changes even though I changed the configuration back to orginal. With the exception on 6 additional sticks of ram.

I was going to upload pick of UID errors but it would not allow attaching a pic. UID is blinking 8 times.

[support_s]

System recommended content:

1. HPE ProLiant DL380 Gen10 Server - Option Parts  Moderator [above link is no longer valid, please visit https://support.hpe.com/connect/s/  to find the latest info ]

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Suman_1978]

Hi,

Please post the Error message that you see during POST or in IML log from iLO.
Please configure the processor, DIMM properly, below are some links which has configuration examples.

Here is the QuickSpecs for the server and here is the HPE Memory QuickSpecs and Technical White Papers.

Troubleshooting Guide for HPE ProLiant Gen10 and Gen10 Plus Servers

Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics

[WABAJABA]

Has Memory using 8 sticks and acording to the chart, goes in slots 3-10.

Clock Not Set Unsupported Processor Configuration Detected. All installed processors must be same model. 

Clock Not Set UPI Initialization Error A fatal UPI Initialization error has been detected - System Haulted (Major code 000000DC, Minor Code 00000009)

Clock Not Set Server critical fault input power loss, power supply 1 (03h)

Clock Not Set Server critical fault input power loss, power supply 1 (03h)   power supply 2 (03h)

[WABAJABA]

@Suman_1978 

Found out what the issue was. It does not link the new Ram that I bought for it. 

It will boot up with the orginal two sticks that it has, but will not boot up with the new Ram. i tried it with just two new sticks of ram. Then tried it with another two stick of new ram. 

I am getting a new error. 209 - Unsupported DIMM configuration Detected - Installed Dimm configuration does not support configured AMP Mode. System will operate in Advanced ECC mode.Code 0000003A code 00000000

[Suman_1978]

Hi,

Can you please check if both the processors are of same part number/model.

Also please note that non-HPE memory modules will cause error.

Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics

[WABAJABA]

@Suman_1978 

The new memory was ddr4 2666 not proper for the system.

The processors are the same part numbers. I confirmed it to make sure. So not understanding why that is a problem.

I got the server booting up with the original processor and two sticks of original Ram. Then I shut it down and put the other processor and riser in. Took one of the ram sticks from processor one. Put it in correct slot for processor two. Still got the same error message.

[cid:image001.jpg@01D9B419.316E8910]

[Suman_1978]

Hi,

Were you able to figure out the issue or able to resolve it?

This server comes with 1st or 2nd Generation Intel® Xeon® Scalable Processor Family, depending on that the memory will change.

For Gen10 memory speed table, please go to: https://www.hpe.com/docs/memory-speed-table

Server memory and persistent memory population rules for HPE Gen10 servers with Intel Xeon Scalable processors technical white paper
https://www.hpe.com/psnow/doc/a00017079enw

You may also refer to this post.

If still issue not resolved, please log a case with HPE Support.

Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics

[WABAJABA · Accepted solution]

Yes we finally figured it out.
The server did not like the new memory we purchased.

[cid:image001.jpg@01D9BBF2.A4771E50]