Dl360g4 w. 4gb memory, am I getting the runaround here?

[wijnands]

I got several DL360g4 servers with 4gb memory. All memory modules are installed correctly according to insight diagnostics. However windows only sees 3,5gb. Logged a support call and got http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=397634&prodTypeId=15351&prodSeriesId=397634&objectID=PSD_EL041214_CW01
To me the explanation in the article sounds unlikely.

However, my servers are on bios P52 dated 12/02/2004, which, according to the article, should be new enough that I shouldn't be seeing this problem. I'm going to enable /PAE and see what happens.

I also heard from a collegue that he has strange memory problems on a DL360 with 6gb memory. HP won't take a call on that because there's kingston memory in that server.

Does anyone have any views on this?

[Matthew J Warrick]

Enable PAE... the Intel Chipset limitation is accurate. I encountered it quite often at a previous customer site.

What exactly is "strange memory problems"? If your friend wants to test his RAM he can always use this: http://www.memtest86.com/. It's a pretty comprehensive test suite. I've used it a lot at home when tweaking memory timings on custom built systems.

[Steven Clementi]

That is the fix you are looking for. It's been asked about many times here in the forums.

To edit your boot.ini file, right click "My Computer" and select properties. Select the "Advanced" tab and click the Settings button in the Startup and Recovery section. Click the edit button in the System Startup section and add /PAE to the line that specifies your OS.

Save, close and reboot.

You should see 4GB after reboot.

What version of windows are you running?

Steven

[Prashant (I am Back)]

You already have a solution for your self in the link mentioned in your post.

CUSTOMER ADVISORY
Document ID: EL041214_CW01
Version: 3
Not All Physical Memory May Be Reported By The Operating System On Certain HP ProLiant Servers
PAE will do it without any issues.

Prashant S.