wicked711
asked on
Hardware issue with HP ProLiant DL380G5
Ran into a wierd issue just now, server stopped responding, lost network connectivity (was only this server on the network that went down so i know it's the server), couldn't verify if console was frozen or not.
Went to the server room, and the RAID LEDs were green (which is normal) but they weren't blinking to show HDD activity, just constantly on and not blinking, i also heard a louder than usual "whir" noise from the server, lasted only a minute or two. The sound stopped and the RAID LEDs started blinking like normail again.
Everything working OK at the moment, event logs dont show anything abnormal on the server.
Anyone have any ideas on what this could have been?
Went to the server room, and the RAID LEDs were green (which is normal) but they weren't blinking to show HDD activity, just constantly on and not blinking, i also heard a louder than usual "whir" noise from the server, lasted only a minute or two. The sound stopped and the RAID LEDs started blinking like normail again.
Everything working OK at the moment, event logs dont show anything abnormal on the server.
Anyone have any ideas on what this could have been?
Open the ststems management homepage and look at the integrated management log, it sounds like it locked up and Automatic System Recovery detected this and rebooted it.
ASKER
The server didn't reboot, it came backup as if nothing had happened. I'll check the HP system logs though.
Cheers,
John
Cheers,
John
If you were unable to contact the server, how do you know it didnt reboot?
I have to agree with andyalder by saying is sounds like the server rebooted.
I have to agree with andyalder by saying is sounds like the server rebooted.
ASKER
Connectivity was lost for only a few minutes. It normally takes our server 10 minutes to reboot completely.
I also had some RDP sessions logged in which weren't closed/reset when i relogged back in after the dropout.
I also had some RDP sessions logged in which weren't closed/reset when i relogged back in after the dropout.
Thanks for the info and I now see why it didn't restart. Unfortunately, I can't think of any other explanation for these events other than possibly power settings being active on the server. Maybe hibernate or standby is enabled which would probably produce the same events with a much faster startup time.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The StartSmart software wasn't installed, i'm rebuilding this server anyway. Thanks for the tips.