I recently toke over a role and handled this server dl360 g7. It has 2 power supplies all are ok. 1 degraded fan and others are all green. Installed with VMware esxi and and 3 vm installed. The server will run for few hours (not consistent) sometime 3 to 4 hours sometime its last longer but less than 12 hours it became unresponsive. The health Led turns blinking red but the power remains green. I tried to press and hold the power button to shutdown but it wont, instead the health Led will turns amber for few seconds, fans will speed up a bit then turns to red again and nothing happen. The only way to turn it on is to unplug both power cord and plug it again. Once on, it will continue accessible but after few hours again the problem repeat.I was wondering if the degraded fan causes this instance? Or there is more something bigger problem. Appreciate any help. Thanks
Not responding HP dl360 g7, Blinking RED health, Green Power, 1 Fan degraded
hardwarehphp-proliantilovmware-esxi
Related Solutions
Well, you're trying to troubleshoot a circa 2006-2008 server that's fallen outside of its normal hardware warranty...
Internal health LED means just that. Internal health. Could be RAM, system board, CPU/CPU socket. You're also at the age where the system board battery could use a refresh. Nowhere in your post here did I see any indication of opening the server and reseating the components. Normally, that's the first step.
Now, outside of that, I recommended that you download the bootable HP Firmware DVD and run it on the system in your previous question. Did you do this?
If all else fails, you can call HP and talk to a tech. I don't know if you're in the US, so I won't post a direct number... but you can usually get fairly far in phone troubleshooting... but still, they'll ask you to update your firmware. So please do that first.
Edit:
You said that you received several of these old servers at the same time. Try swapping components or booting with a minimal set of components. One CPU, 1 or 2 DIMMs to start. And work up from there. At a certain point, though, how much is your time worth? This is a server that can be found for < $200US on the used market. If there's a problem with it, get a different one.
Well, this is an older ProLiant DL385 G2 server... 2006/2007 or so...
I'd suspect system board. Due to the age of the system and the fact that it's probably not under contract or support, you'll probably need to go the used parts route to outfit this system. Another thing to try is the motherboard battery. When the system powers off then boots all the way, is the time correct?
Have you run a diagnostic CD/DVD?
You should reference the HP ProLiant DL385 Generation 2 Server Maintenance and Service Guide for parts information if you choose to self-support.
If you intend to troubleshoot this unit, follow the diagnostic flowchart outlined in the HP ProLiant Servers Troubleshooting Guide.
Personally, I would not spend much time troubleshooting a server this far out of production. If you just need something that works quickly and intend to keep this system alive for awhile, buy another DL385 G2 system on eBay. They're under $200US. This ensures that you'll have some parts available for cannibalizing and is a quick fix. Long-term, prepare to move to a more current platform.
I do have two DL385 G2's still in production, though.
Best Answer
A single broken fan should never cause this kind of "critical" (that's what health light = red means) problem. Your server has probably six hot swappable fans that create a wind tunnel through the chassis, so if five are really up then you should be fine IMO.
You need to get a handle on what component is failing/has failed/is getting too hot. Use HP Insight Diagnostics software to look at your hardware in detail whether it is running or turned off.
If using diagnostics does not highlight an obvious problem for you, your HP Proliant also has a non-maskable interrupt function. There's a pair of pins on the server's mobo which, when shorted, will initiate a crash dump for you to review for problem details.
The pin location should be shown on the big label under the top cover of the server, but be sure to carefully read HP's documentation first.