asked on

16GB HP Microserver

Hi,

Please see https://www.experts-exchange.com/questions/27939687/16-GB-in-HP-Microserver-NL-40-for-esxi-experience.html

My Microserver sees 16GB, then after reboot not anymore, then again ....
All 3 have the same symptom.

Please advise.
J.

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Power OFF the server, rather than warm reboot.

are you using this BIOS

2011.07.29 (A) (25 Aug 2011)

janhoedt

ASKER

I ll check that.

janhoedt

ASKER

This is my version:

janhoedt

ASKER

I checked the version I have with the one you mention, they are exactly the same:

ASKER CERTIFIED SOLUTION

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

janhoedt

ASKER

My other ESX-es/NL 40 (2 of them) don't have these labels attached and have the same problem.
I read somewhere something about the fact that the microserver could not see the 16GB ram because booting to fast ... or something. Might be some bios setting to change or different bios upgrade to do. If only I knew what/which one.

IanTh

have you spoken to hp support it shouldn't miss memory on reboot must be a known issue especially as you have multiple microservers with the same fault

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

@ian... this is an unsupported config, max memory should be 8GB and HP ECC DIMMs!

Steve

sorry mate, he's right.

http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/15351-15351-4237916-4237918-4237917-4248009.html?dnr=1

It's not supposed to accept more than 8 GB.

janhoedt

ASKER

I knew that but hanccocka has same config and no problems so I m trying to figure out the difference.

Steve

if it's not meant to work with more than 8GB, anything you do to get it working is outside of the planned specifications. If it's just a test server with nothing important on it you may get away with it, but dont take the risk if it's a live/critical server.

What would you do if whatever workaround you implement suddenly decides to stop working....

janhoedt

ASKER

>What would you do if whatever workaround you implement suddenly decides to stop >working....

Hanccocka has got it running for months, years ...?
Worst thing that happens is that it shows 8GB instead of 16GB but after (some) reboot(s) it works ok. Fine for me.

Steve

Worst thing that happens is that it shows 8GB instead of 16GB but after (some) reboot(s) it works ok. Fine for me.

Fair enough. If the server dropping to 8GB and needing some reboots doesnt cause you any problems there's no reason not to give it a try.
The problem here is that you are trying to get it to do something it wasnt designed to do. That means there is no guarantee you'll get it working, of that it would keep working in the long term.

Even the smallest difference between the servers you have and the one(s) Hanccocka has got working may prevent you doing this. Firmware, Bios, hardware differences.

Good luck to you. hope you get it working. :-)