Here is the EMS notification:
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Tue Nov 20 19:24:03 2007
xxxxxx sent Event Monitor notification information:
/storage/events/disks/default/0_9_0_0.11.0 is >= 3.
Its current value is MAJORWARNING(3).
Event data from monitor:
Event Time..........: Tue Nov 20 19:24:03 2007
Severity............: MAJORWARNING
Monitor.............: disk_em
Event #.............: 100091
System..............: xxxxxx
Summary:
Disk at hardware path 0/9/0/0.11.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 t
he
driver.
Additional Event Data:
System IP Address...: xxx.xxx.xxx.xxx
Event Id............: 0x4743c0f300000000
Monitor Version.....: B.01.00
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/L3000-5x
OS Version......................: B.11.11
STM Version.....................: A.28.00
EMS Version.....................: A.03.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091v-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/9/0/0.11.0
Device Class...........: Disk
Inquiry Vendor ID......: HP 36.4G
Inquiry Product ID.....: MAM3367MC
Firmware Version.......: HP00
Serial Number..........: KP006472
Product/Device Identification Information:
Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: HP 36.4GMAM3367MC
SCSI Target ID....: 0x0B
SCSI LUN..........: 0x00
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 00 00 00 00 00 00
Command Data Block Fields (6-byte fmt):
Command Operation Code...(0x00)..: TEST UNIT READY
Logical Unit Number..............: 0
Hardware Status: (not present in log record).
SCSI Sense Data:
Undecoded Sense Data:
0x0000: 70 00 06 00 00 00 00 28 00 00 00 00 5D 43 00 00
0x0010: 00 00 0B 00 00 68 00 01 00 00 00 00 00 00 00 00
0x0020: 00 00 00 23 1C 00 00 00 00 00 00 00 00 00 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 : FALSE
Information Field : 0x00000000
Additional Sense Length : 40
Command Specific : 0x00000000
Additional Sense Code : 0x5D
Additional Sense Qualifier : 0x43
Field Replaceable Unit : 0x00
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.
>---------- End Event Monitoring Service Event Notification ----------<
The is a disk in one of two disk enclosures, so I guess that would be local as opposed to SAN.
The disks from which I removed the logical volumes are physically different disks. The process was as follows:
1. Oracle DBA removed files from file system
2. I use sam to remove the file system (List...File systems, select file system, then Action...Remove)
3. I use sam to remove logical volume (List...Logical volumes, select logical volume, then Action...Remove)
Using stm, I get a 'verify successful' on the disk with the EMS error, but it won't run for 'system'.
