/storage/events/disks/default/3_0_4_1_0.2.0.239.0.0.1

[Matthew Ghofrani]

Can you guys tell If I am missing a driver patch. My fibers are reporting these errors almost 3 to 4 times a day. I am including the fcmsutil out put plus the error log.
@@@@@@@@@@@@@@@@@@@@
# fcmsutil /dev/td0

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x020400
N_Port Node World Wide Name = 0x50060b0000225803
N_Port Port World Wide Name = 0x50060b0000225802
Driver state = ONLINE
Hardware Path is = 3/0/2/1/0
Number of Assisted IOs = 1846
Number of Active Login Sessions = 2
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 (AR1204) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Oct 11 2004, 14:45:41

@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Fri Oct 12 12:50:24 2007

drtruman sent Event Monitor notification information:

/storage/events/disks/default/3_0_4_1_0.2.0.239.0.0.1
is >= 3.
Its current value is SERIOUS(4).



Event data from monitor:

Event Time..........: Fri Oct 12 12:50:24 2007
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100776
System..............: drtruman.bidmc.harvard.edu

Summary:
Disk at hardware path 3/0/4/1/0.2.0.239.0.0.1 : Software configuration
error


Description of Error:

The device was unsuccessful in processing the current request message
because the message contained an invalid field in the command data block.
The request was not processed.

Probable Cause / Recommended Action:

The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.

Additional Event Data:
System IP Address...: 10.85.1.22
Event Id............: 0x470fa5d000000000
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/S16K-A
OS Version......................: B.11.11
STM Version.....................: A.41.00
EMS Version.....................: A.04.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100776

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path...: 3/0/4/1/0.2.0.239.0.0.1
Device Class...........: Disk
Inquiry Vendor ID......: DGC
Inquiry Product ID.....: CX3-80WDR5
Firmware Version.......: HP03
Serial Number..........: APM00071300336

Product/Device Identification Information:

Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: DGC CX3-80WDR5
SCSI Target ID....: 0x00
SCSI LUN..........: 0x01

SCSI Command Data Block:

Command Data Block Contents:
0x0000: 1A 00 1C 00 FF 00

Command Data Block Fields (6-byte fmt):
Command Operation Code...(0x1A)..: MODE SENSE
Logical Unit Number..............: 0
DBD Bit..........................: 0
Page Control Bits................: 0
Page Code Bits...................: 28
Allocation Length................: 255 (0xFF)

Hardware Status: (not present in log record).

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
0x0010: 00 00

SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x05
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 10
Command Specific : 0x00000000
Additional Sense Code : 0x24
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00

Sense Key 0x05, ILLEGAL REQUEST, indicates that there was an illegal
parameter in the command data block or in the additional parameters
supplied as data for some commands (FORMAT UNIT, SEARCH DATA, etc.).
This sense key may also indicate that an invalid IDENTIFY message was
received.

The combination of Additional Sense Code and Sense Qualifier (0x2400)
indicates: Invalid field in cdb.


>---------- End Event Monitoring Service Event Notification ----------<
@@@@@@@@@@@@@@@@@@@@@@@@@@

Thanks for your inputs

[Steven E. Protter]

Shalom,

if other disks are successfully presented to the system without error, I doubt its a drive issue.

Possible causes:
1) An old disk was removed on the SAN but the system still has pointers to it. rmsf the device files in that case.
2) A disk array is being detected as a disk but its not really a disk. No easy fix there other than general system patching and presenting a LUN to the system that is a real disk preventing the ghost connection.

SEP

[Matthew Ghofrani]

Thanks. I have removed the devices and will do reboot in a few days.