Is it something wrong with the array disk ?

Rambo_1 — Mon, 24 Oct 2005 23:44:41 GMT

Hi,
I ran #dia -R ,and some messages displayed as below, is it somethings wrong with the array or Host?
nn# dia -R |more

DECevent V2.7

******************************** ENTRY 1 ********************************

Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 20.
Timestamp of occurrence 25-OCT-2005 04:33:06
Host name nndx112

System type register x00000016 Alpha 4000/1200 Series
Number of CPUs (mpnum) x00000004
CPU logging event (mperr) x00000000

Event validity 1. O/S claims event is valid
Event severity 5. Low Priority
Entry type 199. CAM SCSI Event Type

------- Unit Info -------
Bus Number 2.
Unit Number x0084 Target = 0.
LUN = 4.
------- CAM Data -------
Class x00 Disk
Subsystem x00 Disk
Number of Packets 10.

------ Packet Type ------ 258. Module Name String

Routine Name cam_disk_unit_atten

------ Packet Type ------ 256. Generic String

Event - Unit Attention

------ Packet Type ------ 262. Info Error String

Error Type Information Message Detected (recovered)

------ Packet Type ------ 257. Device Name String

Device Name DEC HSZ50-AX V57Z

------ Packet Type ------ 256. Generic String

Active CCB at time of error

------ Packet Type ------ 256. Generic String

CCB request completed with an error

------ Packet Type ------ 1. SCSI I/O Request CCB(CCB_SCSIIO)
Packet Revision 76.

CCB Address xFFFFFC0029FB0380
CCB Length x00C0
XPT Function Code x01 Execute requested SCSI I/O
CAM Status x84 CCB Request Completed WITH Error
Autosense Data Valid for Target
Path ID 2.
Target ID 0.
Target LUN 4.
CAM Flags x00000482 SIM Queue Actions are Enabled
Data Direction (10: DATA OUT)
Disable the SIM Queue Frozen State
*pdrv_ptr xFFFFFC0029FB0028
*next_ccb x0000000000000000
*req_map xFFFFFC0030D1CDC0
void (*cam_cbfcnp)() xFFFFFC00005640B0
*data_ptr x00000001A2701000
Data Transfer Length 2048.
*sense_ptr xFFFFFC0029FB0050
Auotsense Byte Length 160.
CDB Length 6.
Scatter/Gather Entry Cnt 0.
SCSI Status x02 Check Condition
Autosense Residue Length x00
Transfer Residue Length x00000800
(CDB) Command & Data Buf

15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
0000: 00000000 00000004 8445080A * ..E.........*

Timeout Value x0000003C
*msg_ptr x0000000000000000
Message Length 0.
Vendor Unique Flags x4000
Tag Queue Actions x20 Tag for Simple Queue

------ Packet Type ------ 256. Generic String

Error, exception, or abnormal condition

------ Packet Type ------ 256. Generic String

UNIT ATTENTION - Medium changed or target
reset

------ Packet Type ------ 768. SCSI Sense Data
Packet Revision 0.

------- HSZ Data -------
Instance Code x0328450A The disk device reported standard SCSI
Sense Data.

Component ID = Device Services.
Event Number = x00000028
Repair Action = x00000045
NR Threshold = x0000000A
Template Type x51 Disk Transfer Error.
Template Flags x00 HCE = 0, Event did not occur during Host
Command Execution.
Ctrl Serial # ZG70523771
Ctrl Software Revision V57Z
RAIDSET State x00 NORMAL. All members present and
reconstructed, IF LUN is configured as a
RAIDSET.

Error Count 1.
Retry Count 0.
Most Recent ASC x0C
Most Recent ASCQ x01
Next Most Recent ASC x00
Next Most Recent ASCQ x00
Device Locator x000102 Port = 2.
Target = 1.
LUN = 0.
Drive Software Revision 3B05
Drive Product Name BB01811C9C
Device Type x00 Direct Access Device.
Sense Data Qualifier x80 Buf Mode = 0, The target shall not
report GOOD Status on write
commands until the data
blocks are actually written
on the medium.
UWEUO = 0, not defined.
MSBD = 0, not defined.
FBW = 0, not defined.
IDSD = 0, Valid Device Sense Data
fields.
DSSD = 1, Device Sense Data fields
supplied by Physical Device.
-- Standard Sense Data --

Error Code xF0 Current Error
Information Bytes are Valid
Segment # x00
Information Byte 3 x01
Byte 2 x28
Byte 1 x9F
Byte 0 x3A
Sense Key x06 Unit Attention
Additional Sense Length x98
CMD Specific Info Byte 3 x00
Byte 2 x00
Byte 1 x00
Byte 0 x00
ASC & ASCQ x0C01 ASC = x000C
ASCQ = x0001
Write Error Recovered with Auto
Reallocation
FRU Code x00
Sense Key Specific Byte 0 x80 Valid Sense Key Data
Byte 1 x00
Byte 2 x01

-- Device Sense Data --

Error Code xF0 Current Error
Information Bytes are Valid
Segment # x00
Information Byte 3 x01
Byte 2 x28
Byte 1 x9F
Byte 0 x3A LBA: x01289F3A
Sense Key x01 Recovered Error
Additional Sense Length x0A
CMD Specific Info Byte 3 x00
Byte 2 x00
Byte 1 x00
Byte 0 x00
ASC & ASCQ x0C01 ASC = x000C
ASCQ = x0001
Write Error Recovered with Auto
Reallocation
FRU Code x00
Sense Key Specific Byte 0 x80 Valid Sense Key Data
Byte 1 x00
Byte 2 x01

******************************** ENTRY 2 ********************************

Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 19.
Timestamp of occurrence 24-OCT-2005 14:57:28
Host name nndx112

System type register x00000016 Alpha 4000/1200 Series
Number of CPUs (mpnum) x00000004
CPU logging event (mperr) x00000001

Event validity 1. O/S claims event is valid
Event severity 5. Low Priority
Entry type 199. CAM SCSI Event Type

------- Unit Info -------
Bus Number 2.
Unit Number x0084 Target = 0.
LUN = 4.
------- CAM Data -------
Class x00 Disk
Subsystem x00 Disk
Number of Packets 10.

------ Packet Type ------ 258. Module Name String

Routine Name cam_disk_unit_atten

------ Packet Type ------ 256. Generic String

Event - Unit Attention

------ Packet Type ------ 262. Info Error String

Error Type Information Message Detected (recovered)

------ Packet Type ------ 257. Device Name String

Device Name DEC HSZ50-AX V57Z

------ Packet Type ------ 256. Generic String

Active CCB at time of error

------ Packet Type ------ 256. Generic String

CCB request completed with an error

------ Packet Type ------ 1. SCSI I/O Request CCB(CCB_SCSIIO)
Packet Revision 76.

CCB Address xFFFFFC007D167100
CCB Length x00C0
XPT Function Code x01 Execute requested SCSI I/O
CAM Status x84 CCB Request Completed WITH Error
Autosense Data Valid for Target
Path ID 2.
Target ID 0.
Target LUN 4.
CAM Flags x00000442 SIM Queue Actions are Enabled
Data Direction (01: DATA IN)
Disable the SIM Queue Frozen State
*pdrv_ptr xFFFFFC007D166DA8
*next_ccb x0000000000000000
*req_map xFFFFFC000AA8A640
void (*cam_cbfcnp)() xFFFFFC00005640B0
*data_ptr x00000001D5E40000
Data Transfer Length 2048.
*sense_ptr xFFFFFC007D166DD0
Auotsense Byte Length 160.
CDB Length 6.
Scatter/Gather Entry Cnt 0.
SCSI Status x02 Check Condition
Autosense Residue Length x00
Transfer Residue Length x00000800
(CDB) Command & Data Buf

15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
0000: 00000000 00000004 04441708 * ..D.........*

Timeout Value x0000003C
*msg_ptr x0000000000000000
Message Length 0.
Vendor Unique Flags x4000
Tag Queue Actions x20 Tag for Simple Queue

------ Packet Type ------ 256. Generic String

Error, exception, or abnormal condition

------ Packet Type ------ 256. Generic String

UNIT ATTENTION - Medium changed or target
reset

------ Packet Type ------ 768. SCSI Sense Data
Packet Revision 0.

------- HSZ Data -------
Instance Code x0328450A The disk device reported standard SCSI
Sense Data.

Component ID = Device Services.
Event Number = x00000028
Repair Action = x00000045
NR Threshold = x0000000A
Template Type x51 Disk Transfer Error.
Template Flags x00 HCE = 0, Event did not occur during Host
Command Execution.
Ctrl Serial # ZG70523771
Ctrl Software Revision V57Z
RAIDSET State x00 NORMAL. All members present and
reconstructed, IF LUN is configured as a
RAIDSET.

Error Count 1.
Retry Count 0.
Most Recent ASC x0C
Most Recent ASCQ x01
Next Most Recent ASC x00
Next Most Recent ASCQ x00
Device Locator x000106 Port = 6.
Target = 1.
LUN = 0.
Drive Software Revision 3B05
Drive Product Name BB01811C9C
Device Type x00 Direct Access Device.
Sense Data Qualifier x80 Buf Mode = 0, The target shall not
report GOOD Status on write
commands until the data
blocks are actually written
on the medium.
UWEUO = 0, not defined.
MSBD = 0, not defined.
FBW = 0, not defined.
IDSD = 0, Valid Device Sense Data
fields.
DSSD = 1, Device Sense Data fields
supplied by Physical Device.
-- Standard Sense Data --

Error Code xF0 Current Error
Information Bytes are Valid
Segment # x00
Information Byte 3 x01
Byte 2 x24
Byte 1 xFB
Byte 0 xBA
Sense Key x06 Unit Attention
Additional Sense Length x98
CMD Specific Info Byte 3 x00
Byte 2 x00
Byte 1 x00
Byte 0 x00
ASC & ASCQ x0C01 ASC = x000C
ASCQ = x0001
Write Error Recovered with Auto
Reallocation
FRU Code x00
Sense Key Specific Byte 0 x80 Valid Sense Key Data
Byte 1 x00
Byte 2 x01

-- Device Sense Data --

Error Code xF0 Current Error
Information Bytes are Valid
Segment # x00
Information Byte 3 x01
Byte 2 x24
Byte 1 xFB
Byte 0 xBA LBA: x0124FBBA
Sense Key x01 Recovered Error
Additional Sense Length x0A
CMD Specific Info Byte 3 x00
Byte 2 x00
Byte 1 x00
Byte 0 x00
ASC & ASCQ x0C01 ASC = x000C
ASCQ = x0001
Write Error Recovered with Auto
Reallocation
FRU Code x00
Sense Key Specific Byte 0 x80 Valid Sense Key Data
Byte 1 x00
Byte 2 x01

******************************** ENTRY 3 ********************************

Logging OS 2. Digital UNIX
System Architecture 2. Alpha
stdin

Re: Is it something wrong with the array disk ?

Michael Schulte zur Sur — Tue, 25 Oct 2005 00:28:39 GMT

Hi,

it looks like a disk is getting bad blocks and the controller is using bad block replacement.
Device Locator x000106 Port = 6.
Target = 1.
LUN = 0
Write Error Recovered with Auto
Reallocation

greetings,

Michael

Re: Is it something wrong with the array disk ?

Ivan Ferreira — Tue, 25 Oct 2005 07:55:55 GMT

Also, consider that the message is low priority:

Event severity 5. Low Priority

Nothing to be worried about. It's more an informational message.

Re: Is it something wrong with the array disk ?

Johan Brusche — Tue, 25 Oct 2005 08:09:39 GMT

ONE low priority event is probably not to worry about, however MANY of the same low priority are a sign that a HIGH priority (broken disk) is bound to happen --->(RAID-LUN in degraded mode or unuseable JBOD)

__ Johan.

topic Re: Is it something wrong with the array disk ? in Operating System - Tru64 Unix

Is it something wrong with the array disk ?

Re: Is it something wrong with the array disk ?

Re: Is it something wrong with the array disk ?

Re: Is it something wrong with the array disk ?