I got a ticket post mortem on a HP proliant box running Windows server 2003. The report was that the server was unresponsive and had to be rebooted.
A quick check of the eventlog show a lot of warning event 129 from HpCISSs2 source. There is not much description on the event other than \Device\RaidPort0. So obviously this does not help.
Next I fired up HP Websim to check on the hardware status and looks green.
However, the fact that the server reported unresponsive when event 129 (even though its only warning) was firing does relate it to the server hang.
I checked around the net, there was not much resolution. In fact one of the solution from HP is that this event can be ignored! Sure, if its not doing anything else to the server. There are also suggestions that this issue can be caused by network card’s offload and TOE settings, but the server has neither turned on.
Read somewhere that event is a result of the array controller not able to communicate with the hard drive(s). Having had my last experience with RAID issues, I had a look at the stats for each hard disk from HP websim even though all are reporting green and sure enough I found 1 hard disk with 32 hard read errors. I don’t know if this is definitely the cause of the issue, but I take no chances and have call for a swap out to be done.