EMS Disk Error.

Philemon_2 — Wed, 20 Feb 2008 18:33:17 GMT

I see the following error reported by EMS Event Notification. You can find ioscan fnC disk output aswell. please advice me what needs to be done.

Thank you
Philemon

# Ioscan fnC disk
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 0 0/0/1/1/0.8.0 sdisk CLAIMED DEVICE HP 73.4GMAX3073NC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
/dev/dsk/c0t8d0s1 /dev/rdsk/c0t8d0s1
/dev/dsk/c0t8d0s2 /dev/rdsk/c0t8d0s2
/dev/dsk/c0t8d0s3 /dev/rdsk/c0t8d0s3

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

Notification Time: Tue Feb 19 13:42:16 2008

elecprd sent Event Monitor notification information:

/storage/events/disks/default/0_0_1_1_0.8.0 is >= 1.
Its current value is SERIOUS(4).

Event data from monitor:

Event Time..........: Tue Feb 19 13:42:16 2008
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100272
System..............: elecprd.it.hughessupply.com

Summary:
Disk at hardware path 0/0/1/1/0.8.0 : Device connectivity or hardware
failure

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. Contact your HP support representative
to have the device checked.

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, contact your HP support
representative to have the adapter checked.

Additional Event Data:
System IP Address...: 11.224.21.52
Event Id............: 0x47bb230800000002
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):
0x47bb22fa00000002
Additional System Data:
System Model Number.............: ia64 hp superdome server SD64B
OS Version......................: B.11.23
STM Version.....................: C.54.00
EMS Version.....................: A.04.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100272

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/0/1/1/0.8.0
Device Class...........: Disk
Inquiry Vendor ID......: HP 73.4G
Inquiry Product ID.....: MAX3073NC
Firmware Version.......: HPC1
Serial Number..........: X1015853 0613

Product/Device Identification Information:

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

I/O Log Event Data:

Driver Status Code..................: 0x00000010
Length of Logged Hardware Status....: 36 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 70 00 02 00 00 00 00 28 00 00 00 00
0x0010: 04 01 00 00 00 00 08 28 00 67 01 01 00 00 00 00
0x0020: 00 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: 70 00 02 00 00 00 00 28 00 00 00 00 04 01 00 00
0x0010: 00 00 08 28 00 67 01 01 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 : FALSE
Information Field : 0x00000000
Additional Sense Length : 40
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 03 38 A1 42 00 00 20 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............: 54042946 (0x0338A142)
Transfer Length..................: 32 (0x0020)

Manager-Specific Data Fields:
Request ID.............: 0x00EFB063
Data Residue...........: 0x00004000
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x00
Target ID..............: 0x08
LUN ID.................: 0x00
Sense Data Length......: 0x20
Q Tag..................: 0xF7
Retry Count............: 1

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

Re: EMS Disk Error.

Paul Sperry — Wed, 20 Feb 2008 18:38:47 GMT

The Description of Error: pretty much sums it up. It's either a scsi, cable, or disk proplem.

Re: EMS Disk Error.

Tim Nelson — Wed, 20 Feb 2008 18:44:31 GMT

If you really wish to be sure then go into diags ( xstm ), select the disk info and/or logtool ( get password from ITRC ). Review the errors.

If there are many unrecoverable errors then disk needs to be replaced or reset counters and monitor for next failure.

I would save yourself some time and just replace the disk.

Re: EMS Disk Error.

Murat SULUHAN — Wed, 20 Feb 2008 19:18:24 GMT

Hi Philemon

Definitely hw problem. If you have spare parts like disk, terminator, cable you can replace it and try to monitor again or best way is open hw ticket to HP

Best Regards
Murat

topic Re: EMS Disk Error. in Operating System - HP-UX

EMS Disk Error.

Re: EMS Disk Error.

Re: EMS Disk Error.

Re: EMS Disk Error.