RSS

HpCISSs2 event 129 hanging Windows server

27 Jan

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.

Advertisements
 
8 Comments

Posted by on January 27, 2010 in Windows

 

Tags:

8 responses to “HpCISSs2 event 129 hanging Windows server

  1. David Needham

    March 26, 2010 at 6:31 pm

    Did the swap out solve your issues?

    I have a very similar issue right now.

     
  2. Clarke

    August 2, 2010 at 5:05 am

    Thanks for this. Same thing on our server, we had 9000+Hard read errors on a 500GB Disk. The HP tech said if it had been a 60GB HD then the Disk would have been marked as failed already, but because it was a 500Gb disk the read errors would have to reach 90000+ before the RAID Array would mark it as dead. But he has replaced the Disk for me, and it will hopefully arrive tomorrow.

     
    • saltwetfish

      August 2, 2010 at 6:47 am

      Thanks for the comments Clark… never knew error could go up by so much before it reports error!

       
  3. Murugan

    November 4, 2010 at 4:39 am

    I am alos experiencing the same problme, if you have any solution pls. share it with me.

     
    • saltwetfish

      November 4, 2010 at 6:52 pm

      Hi Murugan,

      I believe the article already have the solution. Check any errors in your hard disks…

       
  4. Jeremy

    February 20, 2013 at 7:56 am

    Thank you so much Kelvin. This article led us right to the cause of extreme slowness in our SBS 2008 installation. It did not hang, it was simply unresponsive. In our proliant, the 8 disks in the RAID are in a solid “cube”, and as we only have the single cpu proliant, there were no front fans, and therefore no air circulation through the disks. The disk that it could not recover, but was not a hard failure either was the 3rd one down in the stack of 8. i.e. in the hot-spot just above centre. This is the second time that disk has failed, first time hard fail, with a light, and this time not easy to find. Except for your post. Many thanks.

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: