HBA QL2300 - EventID 11

[inf-adm-winsrv]

Hi,

We have encountered this event (describe in subject) ONLY ONE time on our Exchange Server Cluster. The HBA is physically attached to virtual tape for backup.

"The driver detected a controller error on \Device\RaidPort2."

0000: 0010000f 00660001 00000000 c004000b
0010: 00030000 00000000 00000000 00000000
0020: 00000000 00000000 00000000 00000000
0030: 00000000 c004000b

1. Server Model : HP DL 385 G1
2. HBA model (OEM part number if applicable) HP AB429
3. HBA bios 1.09
4. HBA driver 9.1.3.16
5. Full OS details : WINDOWS 2003 ENTERPRISE SP1 32 Bits
6. Switch/Sanbox Vendor/model/firmware version : Brocade DS500 Fabric OS Version 5.3.0a
7. Storage Array Vendor/model EMC Cx500
8. Sansurfer Version 5.0.1 build 31

Any idea on what happended ?

Thanks for any technical and precise reply !

LMZ

[Rob Leadbeater]

Hi,

I'll take a guess that this is due to an event of some form that happened on your CX-500.

Can you take a look at the EMC box and see if there are any issues there ?

Cheers,

Rob

[inf-adm-winsrv]

Hi,

Thanks for your response, but the Faulting HBA is not physically connected to the CX-500 !It's connected to a Tape Robot pilot by TiNA.

LMZ

[Rob Leadbeater]

Hi,

If the server just has one HBA, how is it connected ??

Your list of kit implies that the HBA is connected to the Brocade switch, to which the virtual tape is also connected...

Cheers,

Rob

[John Kufrovich]

LMZ

Is there qlogic event id 129 around this event?

jk

[inf-adm-winsrv]

The faulting HBA is connected to a Brocade DS5000. The DS500 does not log any event when the error appear.

I 've already search an event 129 (but i've not one). Suppose you want redirect me to this technical document (i've ever seen) :

http://kb.qlogic.com/KanisaPlatform/Publishing/88/917832_f.SAL_Public.html

I 've open a Qlogic case that is closed because they said "Your HBA card is an HP OEM Qlogic, so contact HP support".

i'm disapointed !

LMZ

[John Kufrovich]

LMZ,

Have you thought about asking EMC.

This particular event is an IO/Controller Error. Most likely a timeout condition.

If this was my problem, I would verify that I'm using the the lastest MS storport driver before contacting the vendor.

Then if the problem is still occurring, I would begin suspecting a faulty drive in a LUN on the Array.

jk