HP ML370 G2 thinks its a G3

[deanw83]

Hi, I've inherited the above server which is stamped as a HP ML370 G2 on the case. However, the BIOS reports that it is a G3. Is it possible that it may have been flashed with the wrong BIOS at some point in its life? I’m not currently able to use this server, as during installation of windows (before setup even loads - Windows Server 2003) I get a BSOD with an NMI Memory Parity error. I tried to downgrade the BIOS to a G2, but as it now thinks it’s a G3 it won’t allow me to install a G2 BIOS?? This has really puzzled me, as if it won’t allow me to install a G2 BIOS, surely it should have worked the other way round and not allowed a G3 BIOS to be installed in the first place? Help!

Many thanks,

Dean

[Matti_Kurkela]

The ML370 G2 and G3 models use different chipsets, so a wrong BIOS would most likely cause at least some of the hardware components to work erratically or not at all.

A more likely explanation is that someone has put a wrong faceplate to the server, perhaps when doing a rack/tower configuration change.

The external parts of the G2 and G3 models are identical, so I would expect the removable rack/tower faceplates be interchangeable.

See the Quickspecs ( http://www.hp.com/go/quickspecs ) to conclusively identify the models by hardware features (e.g. the CPU type, the presence/absence of the CPU air duct, etc.).

ML370 G2:
http://h18006.www1.hp.com/products/quickspecs/10901_div/10901_div.HTML

ML370 G3:
http://h18006.www1.hp.com/products/quickspecs/11450_div/11450_div.HTML

MK

[Pieter 't Hart]

- Faceplate could be wrong as allready mentioned
- other option is the Mobo has been replaced by g3 model.
- >>> NMI Memory Parity error <<<
could just point to a memory error?

checks to verify model :
- Start from the partnumber on the MoBo and search wich model this belongs to.
this is the most conclusive check.
- you can also look for a systemmodel+serial number inside the case, and enter this at the waranty check site.

chardware checks :
- start system with minimal configuration (remove as much components as possible) with only HP original components if possible.
- you can test the system with the HP diagnostics utility
http://www.hp.com/servers/diags