ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Hardware problem-server DL385

sunset_root
Occasional Visitor

Hardware problem-server DL385

Hello. I speak in English not well, sorry. I have the following problem with the server DL385 (2xDualCore Opteron 280 2.4 Ghz, 4Gb RAM (2x1Gb 4x512Gb) 3 x 36 Gb SCSI): the server turns on, runs for a while, but then an error and it stops. In the USB-port is nothing connected, only ethernet cord and keyboard. The figure shows errors that are displayed before stopping the system.
http://s45.radikal.ru/i107/1011/fc/d249c826929f.jpg
http://i021.radikal.ru/1011/b0/5d58cdacc59c.jpg
http://s009.radikal.ru/i308/1011/94/691844e1fab8.jpg
Thanks.
5 REPLIES
sunset_root
Occasional Visitor

Re: Hardware problem-server DL385

By the way, sometimes before stopping the system on the keyboard flash 2 lights (Caps Lock & Scroll Lock).
ess
Super Advisor

Re: Hardware problem-server DL385

Hi
not image are available.
but you must test the hardware your server step1: check the cpu one be one.
setp2: check the ram .
setp3: insert all hard drive and boot again your system.
sunset_root
Occasional Visitor

Re: Hardware problem-server DL385

Images sometimes not displayed, you simply need to update - the server is temporarily unavailable.
I changed the processors in some places, leaving only one working, changed the memory strip, changing hard drives. Without result.
Pete2010
Frequent Advisor

Re: Hardware problem-server DL385

Boot with the HP Smart start CD a& run diagnostics. Also, remove any thing attached to the servers USB ports.
SMR
Valued Contributor

Re: Hardware problem-server DL385

First error (MCE on bank 4) seems related to RAM or even a bad dimm slot. Basically Machine check exceptions coming from bank 4 are errors reported by the northbridge. The address however, is strangely large compared to the amount of ram your system has.

You can try using AMD MCAT to better decode the MCE... I would rule out the memory dimms as the problem (it seems you already did) if that does not show you the culprit, Im afraid the system board might be the issue here.

Good luck!