From: Bobby (why2shy_ddn@yahoo.com)
Date: Tue Dec 11 2007 - 00:16:16 EST
Hi,
Please check the disk using ioscan, whethwer the disk is claimed
# ioscan -fnC disk
If it is in claimed state then check the Hard Disk with
# diskinfo <path>
Also try to check the disk for any file system error using fsck.
Bye
Sandeep Verma
javier <jgonzalez@conatel.com.uy> wrote:
Hi Admins,
Please take a brief look at the following event message.
Should I replace the involved disk right away ?
All the volume group logical volumes are "available/syncd" and the disk status is also "available".
Thanks in advance for your opinion.
Regards,
Javier
CURRENT MONITOR DATA:
Event Time..........: Thu Nov 29 04:10:17 2007
Severity............: CRITICAL
Monitor.............: disk_em
Event #.............: 100057
System..............: squonk
Summary:
Disk at hardware path 10/12.9.0 : Hardware failure
Description of Error:
The device was unsuccessful in processing the current I/O request due to
an internal target failure. The request may have been processed in a way
which could cause damage to or loss of data.
Probable Cause / Recommended Action:
The device has experienced a hardware failure. Contact your HP support
representative to have the device checked.
Additional Event Data:
System IP Address...: 192.168.2.1
Event Id............: 0x474e81f900000000
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):
0x474e81f800000000
Additional System Data:
System Model Number.............: 9000/800
OS Version......................: B.11.11
STM Version.....................: A.55.00
EMS Version.....................: A.04.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100057
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...: 10/12.9.0
Device Class...........: Disk
Inquiry Vendor ID......: IBM
Inquiry Product ID.....: DGHS09Y
Firmware Version.......: HP08
Serial Number..........: 6816FD1AGA
Product/Device Identification Information:
Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: IBMDGHS09Y
SCSI Target ID....: 0x09
SCSI LUN..........: 0x00
I/O Log Event Data:
Driver Status Code..................: 0x0000007E
Length of Logged Hardware Status....: 36 bytes.
Offset to Logged Manager Information: 36 bytes.
Length of Logged Manager Information: 34 bytes.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 02 70 00 04 00 00 00 00 18 00 00 00 00
0x0010: 44 00 01 00 00 00 00 00 01 3F 00 00 FF FF FF FF
0x0020: FF FF 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 04 00 00 00 00 18 00 00 00 00 44 00 01 00
0x0010: 00 00 00 00 01 3F 00 00 FF FF FF FF FF FF 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 : 0x04
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 24
Command Specific : 0x00000000
Additional Sense Code : 0x44
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x01
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00
Sense Key 0x04, HARDWARE ERROR, indicates that the device detected a
nonrecoverable hardware failure (for example, controller failure,
device failure, parity error, etc.) while performing the command or
during a self test.
The combination of Additional Sense Code and Sense Qualifier (0x4400)
indicates: Internal target failure.
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 28 00 00 0F B1 20 00 00 10 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............: 1028384 (0x000FB120)
Transfer Length..................: 16 (0x0010)
Manager-Specific Data Fields:
Request ID.............: 0x03AEBBE1
Data Residue...........: 0x00000400
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x03
Target ID..............: 0x09
LUN ID.................: 0x00
Sense Data Length......: 0x20
Q Tag..................: 0x6F
Retry Count............: 14
---------------------------------
Este mensaje es privado y confidencial y tiene como único destinatario la persona a la que va dirigida. La responsabilidad de su contenido es del remitente y no de CONATEL. Si usted ha recibido este mensaje por error, tenga presente que le está prohibido revelarlo, copiarlo o distribuirlo, debiendo avisar de inmediato al remitente y borrarlo de su sistema. El error de transmisión no implica renuncia a la privacidad y confidencialidad.
This email is private and confidential and intended solely for the use of the individual to whom it is addressed. The responsibility of its content is the sender's and not CONATEL'S. If you have received this email by mistake please notify the sender immediately and delete it from your system. Its disclosure, copy or distribution is absolutely forbidden. The transmission error does not imply a waiver of privacy and confidentiality.
---------------------------------
CURRENT MONITOR DATA:
Event Time..........: Thu Nov 29 04:10:17 2007
Severity............: CRITICAL
Monitor.............: disk_em
Event #.............: 100057
System..............: squonk
Summary:
Disk at hardware path 10/12.9.0 : Hardware failure
Description of Error:
The device was unsuccessful in processing the current I/O request due to
an internal target failure. The request may have been processed in a way
which could cause damage to or loss of data.
Probable Cause / Recommended Action:
The device has experienced a hardware failure. Contact your HP support
representative to have the device checked.
Additional Event Data:
System IP Address...: 192.168.2.1
Event Id............: 0x474e81f900000000
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):
0x474e81f800000000
Additional System Data:
System Model Number.............: 9000/800
OS Version......................: B.11.11
STM Version.....................: A.55.00
EMS Version.....................: A.04.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100057
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...: 10/12.9.0
Device Class...........: Disk
Inquiry Vendor ID......: IBM
Inquiry Product ID.....: DGHS09Y
Firmware Version.......: HP08
Serial Number..........: 6816FD1AGA
Product/Device Identification Information:
Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: IBMDGHS09Y
SCSI Target ID....: 0x09
SCSI LUN..........: 0x00
I/O Log Event Data:
Driver Status Code..................: 0x0000007E
Length of Logged Hardware Status....: 36 bytes.
Offset to Logged Manager Information: 36 bytes.
Length of Logged Manager Information: 34 bytes.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 02 70 00 04 00 00 00 00 18 00 00 00 00
0x0010: 44 00 01 00 00 00 00 00 01 3F 00 00 FF FF FF FF
0x0020: FF FF 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 04 00 00 00 00 18 00 00 00 00 44 00 01 00
0x0010: 00 00 00 00 01 3F 00 00 FF FF FF FF FF FF 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 : 0x04
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 24
Command Specific : 0x00000000
Additional Sense Code : 0x44
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x01
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00
Sense Key 0x04, HARDWARE ERROR, indicates that the device detected a
nonrecoverable hardware failure (for example, controller failure,
device failure, parity error, etc.) while performing the command or
during a self test.
The combination of Additional Sense Code and Sense Qualifier (0x4400)
indicates: Internal target failure.
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 28 00 00 0F B1 20 00 00 10 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............: 1028384 (0x000FB120)
Transfer Length..................: 16 (0x0010)
Manager-Specific Data Fields:
Request ID.............: 0x03AEBBE1
Data Residue...........: 0x00000400
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x03
Target ID..............: 0x09
LUN ID.................: 0x00
Sense Data Length......: 0x20
Q Tag..................: 0x6F
Retry Count............: 14
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
--
---> 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:58 EDT