Event 100091 - disk error

Luke Morgan — Wed, 06 Apr 2005 08:52:31 GMT

I have seen the following error message in roots email a few times and it's worrying me.
The disk is part of a mirrored pair in a fibre channel array.
The database residing on the disk seems ok.
In short, everything seems to be ok.
The cases mentioned, concerning poweroffs and hardware resets, have not happened to my knowledge.
This leaves the remaining suggestion that the driver is wrong.
However, it is not the only 73gb disk in the array and there is a few days between instances of the emailed error report.
I'm wondering what else I can do to check this error out and see what the problem is.
Any pointers would be much appreciated.

Cheers

Luke

=====

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

Notification Time: Tue Mar 29 04:55:58 2005

triton2 sent Event Monitor notification information:

/storage/events/disks/default/0_12_0_0.8.0.255.0.13.0
is >= 3.
Its current value is MAJORWARNING(3).

Event data from monitor:

Event Time..........: Tue Mar 29 04:55:58 2005
Severity............: MAJORWARNING
Monitor.............: disk_em
Event #.............: 100091
System..............: triton2

Summary:
Disk at hardware path 0/12/0/0.8.0.255.0.13.0 : Software configuration
error

Description of Error:

The device is in a condition where it requires action on the part of the
device driver or a human operator.

Probable Cause / Recommended Action:

The device has been reset by a Bus Device Reset message, a hard reset
condition, or a power-on reset.

If this is the case, no action is necessary.

Alternatively, a removable medium has been loaded or replaced.

If this is the case, no action is necessary.

Alternatively, the mode parameters, microcode, or inquiry data for the
device have been changed.

If this is the case, no action is necessary.

Alternatively, the installed version of the device driver does not match
that of the installed version of HP-UX. Install the correct version of the
driver.

Additional Event Data:
System IP Address...: *********
Event Id............: 0x4248d1ce00000000
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):
0x4248d1cd00000000
Additional System Data:
System Model Number.............: 9000/800/L1500-7x
OS Version......................: B.11.11
STM Version.....................: A.43.00
EMS Version.....................: A.04.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091

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...: 0/12/0/0.8.0.255.0.13.0
Device Class...........: Disk
Inquiry Vendor ID......: HP 73.4G
Inquiry Product ID.....: ST373453FC
Firmware Version.......: HP03
Serial Number..........: 3HW039MN

Product/Device Identification Information:

Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: HP73.4GST373453FC
SCSI Target ID....: 0x0D
SCSI LUN..........: 0x00

I/O Log Event Data:

Driver Status Code..................: 0x0000000B
Length of Logged Hardware Status....: 22 bytes.
Offset to Logged Manager Information: 24 bytes.
Length of Logged Manager Information: 34 bytes.

Hardware Status:

Raw H/W Status:
0x0000: 00 00 00 02 F0 00 06 00 00 B5 8E 0A 00 00 00 00
0x0010: 29 02 CC 00 00 00

SCSI Status...: CHECK CONDITION (0x02)
Indicates that a contingent allegiance condition has occurred. Any
error, exception, or abnormal condition that causes sense data to be
set will produce the CHECK CONDITION status.

SCSI Sense Data:

Undecoded Sense Data:
0x0000: F0 00 06 00 00 B5 8E 0A 00 00 00 00 29 02 CC 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 : 0x06
Information Field Valid : TRUE
Information Field : 0x0000B58E
Additional Sense Length : 10
Command Specific : 0x00000000
Additional Sense Code : 0x29
Additional Sense Qualifier : 0x02
Field Replaceable Unit : 0xCC
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00

Sense Key 0x06, UNIT ATTENTION, indicates that the target has been
reset by a BUS DEVICE RESET message, a hard reset condition, or by a
power-on reset. If not a reset, then one of the following may have
occurred.
1. A removable medium may have been changed.
2. The mode parameters in effect for this initiator have been
changed by another initiator.
3. The version or level of microcode has been changed.
4. Tagged commands queued for this initiator were cleared by
another initiator.
5. INQUIRY data has been changed.
6. The mode parameters in effect for this initiator have been
restored from non-volatile memory.
7. A change in the condition of a synchronized spindle.
8. Any other event that requires the attention of the initiator.

SCSI Command Data Block:

Command Data Block Contents:
0x0000: 2A 00 00 00 1D 76 00 00 08 00

Command Data Block Fields (10-byte fmt):
Command Operation Code...(0x2A)..: WRITE
Logical Unit Number..............: 0
DPO Bit..........................: 0
FUA Bit..........................: 0
Relative Address Bit.............: 0
Logical Block Address............: 7542 (0x00001D76)
Transfer Length..................: 8 (0x0008)

Manager-Specific Data Fields:
Request ID.............: 0x061941F8
Data Residue...........: 0x00001000
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x06
Target ID..............: 0x0D
LUN ID.................: 0x00
Sense Data Length......: 0x12
Q Tag..................: 0xDB
Retry Count............: 0

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

Re: Event 100091 - disk error

Kent Ostby — Wed, 06 Apr 2005 10:19:58 GMT

This is one of those events that could be serious or could be something to ignore.

Are you seeing any other SCSI errors in (for instance) dmesg output ?

If so, this could be a problem with the SCSI card or disk.

If this is a removable media device (like a library) then you can pretty safely ignore this.

This message is a catch all for EMS whenever it gets an unrecognizable code from the sense data.

Re: Event 100091 - disk error

Luke Morgan — Thu, 07 Apr 2005 05:51:27 GMT

Thank you for your reply.
The disk in question is a 74Gb disk, part of a mirrored array.
It is in a volume group, directly mirrored with another similar disk.
I cannot see any other errors, and all seems well.
But the error states CRITICAL sometimes and MAJOR WARNING on others.
It is this that makes me feel a little uneasy.

Re: Event 100091 - disk error

Florian Heigl (new acc) — Thu, 07 Apr 2005 07:20:35 GMT

At first I'd guess Your disk firmware or FC drivers are outdated, but I can't tell for sure, I'd have to ask HP myself.

the critical point should really be Disk at hardware path 0/12/0/0.8.0.255.0.13.0 : Software configuration
error
- this is no plain hardware issue, I'd think :)

Re: Event 100091 - disk error

Luke Morgan — Thu, 07 Apr 2005 10:42:28 GMT

That makes sense.
How can I check the firmware per disk as I have another similar
disk and it doesn't seem to have the same trouble.

topic Re: Event 100091 - disk error in Operating System - HP-UX

Event 100091 - disk error

Re: Event 100091 - disk error

Re: Event 100091 - disk error

Re: Event 100091 - disk error

Re: Event 100091 - disk error