Event ID 129 source HpCISSs2

[Alfred Nims]

I have installed Windows 2008 sp2 x64 on a blade server and I am constantly receiving this Warning. "Reset to device, \Device
RaidPort0, was issued."

Any suggestions? the other thread I saw mentions server 2003 sp1.

[Erdogan Temur]

Hi Alfred,

Check the below customer advisory with the KB932755 Update

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c01611218

[Alfred Nims]

I have 5 BL460c G5 servers, all with Windows 2008 SP2. They all are using controller driver 6.18.0.64. Two of these servers do not give me any HpCISSs errors but three do. After reading the article you attached are you suggesting I back rev this to what version? Anything else I may look into to find why 2 servers no errors and 3 with?

[Suzanne Harris]

Alfred,
Did you ever find a resolution? I have the same error on ML370 G5 Win2K8, SP2, 64b, Smart Array E200 controllers.

[Alfred Nims]

No resolution as of yet, but it looks to happen when we are running backups mostly. It does not occur all day.

[zzaphoid]

Have had this issue on ML350 G5 servers with onboard E200i controller across the UK, we have a few hundred servers deployed.

Servers are installed with Windows 2003 SP2 latest PSP 8.7 and Firmware disc  9.3 applied

When Array, either RAID1+0 or RAID 5 has high IO load these errors are generated following the system freezing for around 10 seconds

I have traced the issue to the following 146.8GB  2.5" SAS drive models being present in the array! :-

EG0146FARTR

EG0146BARTP

These drives have been flashed to the latest firmware HPDA and HPD1 respectively as of 29/9/11 this has not fixed the issue.

When these model drives are removed and replaced with DG0146FARVU model or similar the problem is resolved, no more freezing and error 129's logged

This fault is repeatable at will on any of our G5 servers by adding one of these model drives into the disc array!

Maybe worth checking for these model drives on your servers

[Justin T Reynolds]

This event is almost exclusively generated by the Windows OS sending down resets to a timed out device.  While the log says the source is "HpCISSs2" it is actually occuring when the storport driver (which sits above the HpCISSs2 driver in the driver stack) sends down a reset to a targeted device.  This event is USUALLY indicitive of a failed hard drive of some sort.  Tape drives are especially known for generating this event when they are beginning to fail.

Summary:  This event is likely an indication that you hard drive is failing.  Attempt to replace the drive to remove the error.  The event is generated because the Windows storport driver is sending down a reset for a I/O request that has taken too long (timed out).

[pyork12]

Check out the HP Advisory below:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03097038&lang=en&cc=us&taskId=115&prodSeriesId=3580609&prodTypeId=15351

In short:

HP Smart Array E200/E200i Controller - FW Version 1.86 combined with any of the below SAS drives

72GB SAS 15K rpm 6 Gb 2.5" SFF Dual-Port Hot-Plug Hard Drive - EH0072FARUA

146GB SAS 10K rpm 6 Gb 2.5" SFF Dual-Port Hot-Plug Hard Drive - EG0146FARTR

146GB SAS 10K rpm 6 Gb 2.5" SFF Dual-Port Hot-Plug Hard Drive - DG0146BARTP

Resolution - Upgraded to FW Version 1.88 or you can just ignore the alert.