Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
16GB HP Microserver
Hi,
Please see http://www.experts-exchange.com/Software/VMWare/Q_27939687.html
My Microserver sees 16GB, then after reboot not anymore, then again ....
All 3 have the same symptom.
Please advise.
J.
Please see http://www.experts-exchange.com/Software/VMWare/Q_27939687.html
My Microserver sees 16GB, then after reboot not anymore, then again ....
All 3 have the same symptom.
Please advise.
J.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
what I have noticed with your Microserver, is it has labels attached to your drive caddies, stating Non-Hot Plug, I assume you did not stick these there, so I'm wondering if there are different revisions/models of servers.
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.
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.
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
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.
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.
I knew that but hanccocka has same config and no problems so I m trying to figure out the difference.
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....
What would you do if whatever workaround you implement suddenly decides to stop working....
>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.
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.
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. :-)
Premium Content
You need an Expert Office subscription to comment.Start Free Trial