From: Krajcovic, Jakub (jakub.krajcovic@hp.com)
Date: Fri Apr 30 2004 - 08:23:01 EDT
Hello Unix admins,
I am getting this kind of an error on one of the systems:
</var/opt/resmon/log/event.log - snippet>:
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Fri Apr 30 11:29:51 2004
odyssey1 sent Event Monitor notification information:
/storage/events/disks/default/6_2_0.8.0.110.0.0.3
is >= 1.
Its current value is CRITICAL(5).
Event data from monitor:
Event Time : Fri Apr 30 11:29:51 2004
Hostname : odyssey1.brussels.hp.com IP Address : 15.184.3.250
Event Id : 0x0040921c8f00000000 Monitor : disk_em
Event # : 100272 Event Class : I/O
Severity : CRITICAL
Disk at hardware path 6/2/0.8.0.110.0.0.3 : Device connectivity or
hardware
failure
Associated OS error log entry id(s):
0x40921c8d00000004
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100272
Description of Error:
The device was not ready to process requests when it received a
request
from the device driver because it is in the process of becoming
ready.
Probable Cause / Recommended Action:
The device may have been powered off and may be being powered on.
Alternatively, one or both of the terminators on the SCSI bus may
be
missing. Install the terminators in their proper locations at the
ends of
the SCSI bus.
Alternatively, the SCSI cable may have become detached from the
device.
Re-attach the cable.
Alternatively, the SCSI cable may have failed. Replace it.
Alternatively, the device may be in a state where it could not
process
this, or any, request. Cycle power to the device.
Alternatively, there could be more than one device having the same
address
on the SCSI bus. Make all the addresses on the SCSI bus unique.
Alternatively, the total length of all cable segments on the SCSI
bus
exceeds 25 meters. Replace one or more cable segments until the
total
length is less than this value.
Alternatively, if all of the above fail to correct the problem, the
device
has experienced a hardware failure. Repair or replace it, as
necessary.
Alternatively, if messages corresponding to this condition appear
in the
log for more than one device on the SCSI bus, the device adapter
may be in
a state from which it cannot extract itself. Perform a system
shutdown,
cycle power to the computer and wait for it to reboot.
If, after reboot, messages corresponding to this condition continue
to
appear in the log for this SCSI bus, replace the device adapter.
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
Product/Device Identification Information:
Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: HPA6188A
SCSI Target ID....: 0x00
SCSI LUN..........: 0x03
I/O Log Event Data:
Driver Status Code..................: 0x00000010
Length of Logged Hardware Status....: 34 bytes.
Offset to Logged Manager Information: 40 bytes.
Length of Logged Manager Information: 34 bytes.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 02 F0 00 02 00 00 00 00 0E 00 00 00 00
0x0010: 04 01 00 00 00 00 13 00 14 00 00 00 00 00 00 00
0x0020: 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 02 00 00 00 00 0E 00 00 00 00 04 01 00 00
0x0010: 00 00 13 00 14 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 : 0x02
Information Field Valid : TRUE
Information Field : 0x00000000
Additional Sense Length : 14
Command Specific : 0x00000000
Additional Sense Code : 0x04
Additional Sense Qualifier : 0x01
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00
Sense Key 0x02, NOT READY, indicates that the logical unit
addressed
cannot be accessed. Operator intervention may be required to
correct
this condition.
The combination of Additional Sense Code and Sense Qualifier
(0x0401)
indicates: Logical unit is in process of becoming ready.
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 28 00 00 00 00 10 00 00 04 00
Command Data Block Fields (10-byte fmt):
Command Operation Code...(0x28)..: READ
Logical Unit Number..............: 0
DPO Bit..........................: 0
FUA Bit..........................: 0
Relative Address Bit.............: 0
Logical Block Address............: 16 (0x00000010)
Transfer Length..................: 4 (0x0004)
Manager-Specific Data Fields:
Request ID.............: 0x2336A392
Data Residue...........: 0x00000800
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x23
Target ID..............: 0x00
LUN ID.................: 0x03
Sense Data Length......: 0x1E
Q Tag..................: 0xF3
Retry Count............: 2
*****************************************END************************
Now, can you please help me determine the type of problem? Is this just
a plain hardware problem, eg replace the disk and it's done, or it there
something else to this? I'm confused, because when i do
# ioscan -func disk
i don't get any NO_HW states, and the output from ioscan seems to be ok.
here follows something from syslog:
odyssey1:/root/home/root (root) grep hardware /var/adm/syslog/syslog.log
Apr 30 11:26:50 odyssey1 syslog: CVSDM; MINOR WARNING Event Code=222;
Single Controller.; ; Hardware Address=6/2/0.8.0.255.6.14.0; FRU
Location=M/C1; Vendor ID=HP; Model ID=A6188A; Product S/N=00PR04041718;
Latest information on this event at
http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor.htm#222
Apr 30 11:26:50 odyssey1 syslog: CVSDM; MAJOR WARNING Event Code=224;
Battery Failure in Unknown FRU location.; ; Hardware
Address=6/2/0.8.0.255.6.14.0; Unknown FRU Location; Unknown Vendor ID;
Unknown Model ID; Unknown Product S/N; Latest information on this event
at http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor.htm#224
Apr 30 12:41:55 odyssey1 syslog: CVSDM; MAJOR WARNING Event Code=202;
NVRAM Battery Depletion in M/C2.; ; Hardware
Address=6/2/0.8.0.255.6.14.0; FRU Location=M/C2; Vendor ID=HP; Model
ID=A6188A; Product S/N=00PR04041699; Latest information on this event at
http://docs.hp.com/hpux/content/hardware/ems/RemoteMonitor.htm#202
odyssey1:/root/home/root (root)
Jakub Krajcovic
HP EMEA MSDD UXPS BTV
jakub.krajcovic@hp.com
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:40 EDT