Quantcast
Channel: All ProLiant Servers (ML,DL,SL) posts
Viewing all articles
Browse latest Browse all 30225

Re: ML 350 G5: Internal SAS Enclosure Device Failure (Bay 1, Box 1, Port 2I, Slot 0)

$
0
0
The older log messages from January of this year sound like a drive failed on Jan 7 and was replaced on Jan 23.

That's probably unrelated to the event you had this morning where the server was responding to pings but nothing else. Since the IML didn't show any events from today, it was probably a software error.

I don't know how SLES prioritizes net activity over everything else, but if there was something using 100% CPU or otherwise taking extra system resources, it may have been responding to pings, just barely, but nothing else was able to get in.

I've had that happen with Windows too where some misbehaving software used all the memory and started paging heavily... the system interrupts were so bad that nothing else could happen... couldn't login, even locallly.

I was surprised the HP ASR didn't kick in, so it must have just been able to send/receive heartbeats and avoid an ASR reboot.

So, it can happen... I don't know if that's what it was in your case, but that would be my first guess. Check your OS and software logs to see what might have been running at the time and go from there.

Viewing all articles
Browse latest Browse all 30225

Trending Articles