1832542 Members
5964 Online
110043 Solutions
New Discussion

Disk Error....

 
Jaikishan_1
Advisor

Disk Error....

Dear Experts,
Event data from monitor:

Event Time..........: Fri Sep 7 15:35:20 2001
Severity............: MINORWARNING
Monitor.............: disk_em
Event #.............: 102026
System..............: sigdev

Summary:
Disk at hardware path 8/16/5.6.0 :


Description of Error:

Message in ll_msg (set: 15 msg: 0) did not exist in catalog.
Catalog type is MONITOR_INFO
Catalog version is A.01.00
Module name is disk_em
Message set number is 15
Message number is 0
Message size is 88
Message parameter 1:
Message parameter size = 28
Message parameter is a literal
Literal text is Read Defect Data

Probable Cause / Recommended Action:

Message in ll_msg (set: 16 msg: 0) did not exist in catalog.
Catalog type is MONITOR_INFO
Catalog version is A.01.00
Module name is disk_em
Message set number is 16
Message number is 0
Message size is 60

Additional Event Data:
System IP Address...: 10.102.21.5
Event Id............: 0x3b989be100000000
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/803
OS Version......................: B.11.00
STM Version.....................: A.24.00
EMS Version.....................: A.03.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#102026

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...: 8/16/5.6.0
Device Class...........: Disk
Inquiry Vendor ID......: SEAGATE
Inquiry Product ID.....: ST34520N
Firmware Version.......: 1498
Serial Number..........: AYZA8H1P

Product/Device Identification Information:

Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: SEAGATE ST34520N
SCSI Target ID....: 0x06
SCSI LUN..........: 0x00

Hardware Status: (not present in log record).

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 01 00 0C 00 00 0E 00 00 00 00 1C 00 00 00
0x0010: 00 00 00 00 00 10

SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x01
Information Field Valid : FALSE
Information Field : 0x000C0000
Additional Sense Length : 14
Command Specific : 0x00000000
Additional Sense Code : 0x1C
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00

Sense Key 0x01, RECOVERED ERROR, indicates that the last command
completed successfully with some recovery action performed by the
device.

The combination of Additional Sense Code and Sense Qualifier (0x1C00)
indicates: Defect list not found.


Any Kind of Help will be Appreciated.
Jai

 

 

P.S. This thread has been moved from Disk to HP-UX > sysadmin. - Hp forum moderator

Don`t Give Up........
3 REPLIES 3
Thierry Poels_1
Honored Contributor

Re: Disk Error....

hi,

"Recoverable read error"
If this didn't happen more than once, I wouldn't worry about it. If you get this error serveral times (state should change from MINOR to MAJOR or CRITICAL ERROR), get the disk replaced asap.

good luck,
Thierry.
All unix flavours are exactly the same . . . . . . . . . . for end users anyway.
Santosh Nair_1
Honored Contributor

Re: Disk Error....

"Recoverable read error "...this just means that the device was unsuccessful when it tried to read data on the first try. If this develops into a trend, i.e. happens multiple times, I would have HP come in and replace the disk because it points to the disk going bad.

-Santosh
Life is what's happening while you're busy making other plans
Varghese Mathew
Trusted Contributor

Re: Disk Error....

Hi Jaikishan,

As the guys have already suggested it canbe ignored if that was happened only once. But if it get repeated then you may need to get the fauly disk replaced by HP.

You can check for more details if you are using a disk array using commands
#arraydsp -i -> which will give you the serial number of array and then type in
#arraydsp -a - this will give all the states of the disk array

Hope this helps..

Cheers !!!
Varghese Mathew
Cheers !!!