Looks like this is reporting against an Hitachi. Do you have Hitachi in your environment? Assume it's not the host since you state it's an AIX host.

that sure is a Hitachi LDEV , equates to EMC's hyper.

in case it is an EMC drive, does anyone know how to analyse the SENSE DATA (in those kind of scsi error) ?

example :
LABEL: SC_DISK_ERR4
IDENTIFIER: DCB47997

Date/Time: Wed Nov 5 15:18:31 NFT 2008
Sequence Number: 109740
Machine Id: 00xxxxxxxxxx
Node Id: op12adb1
Class: H
Type: TEMP
Resource Name: hdisk395
Resource Class: disk
Resource Type: SYMM_RAID5_RDF1
Location: U5791.001.99B085Y-P2-C05-T1-W5006048448943312-L44000000000000
VPD:
Manufacturer................EMC
Machine Type and Model......SYMMETRIX
ROS Level and ID............5671
Serial Number...............80A3D000
Part Number.................000000000000570012000287
EC Level....................461580
Device Specific.(Z0)........04
Device Specific.(Z1)........57
Device Specific.(Z2)........567100690000000000021508
Device Specific.(Z3)........12008000
Device Specific.(Z4)........54130008
Device Specific.(Z5)........BF80
Device Specific.(Z6)........4D

Description
DISK OPERATION ERROR

Probable Causes
MEDIA
DASD DEVICE

User Causes
MEDIA DEFECTIVE

Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PERFORM PROBLEM DETERMINATION PROCEDURES

Failure Causes
MEDIA
DISK DRIVE

Recommended Actions
FOR REMOVABLE MEDIA, CHANGE MEDIA AND RETRY
PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
PATH ID
0
SENSE DATA
0A00 2A00 018D 3A00 0001 0004 0000 0000 0000 0000 0000 0000 0102 0000 7000 0B00
0000 000A 0000 0000 4400 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 C800 0000 0001 0000 0000 0000 0000 0000 0000 0000
0000 0030 001D

Message was edited by: KCSCP. I removed the machine ID.

Jurjen .. just a question .. Do you have children?
How did you call them ?? SBC and SPC ??

SC_DISK_ERR2 and SC_DISK_ERR4 contain Sense Data. The format of the sense data is the same for each type of disk (EMC, Hitachi, local disks, etc.). You can get the SCSI Status Code, Sense Key, Additional Sense Code (ASC) and Additional Sense Code Qualifier (ASCQ) from the AIX SENSE DATA as follows:

In the first line of the SENSE DATA, locate the fourth number *counting from the right*. In the example below, that's "0102". Now take the right half of that number, and you get the SCSI Status. In this case: "02".

Also in the first line of the SENSE DATA, take the rightmost number. In the example below, that's "0B00". Now take the left half of that number ("0B"), and you get the SCSI Sense Key.

In the second line of the SENSE DATA, take the fifth number from the left, in this case "4400". The left part of that number is the SCSI Additional Sense Code (ASC), the right part is the Additional Sense Code Qualifier (ASCQ).

In the example below, we have SCSI Status 02, Sense Key 0B, ASC 44 and ASCQ 00.

SCSI Status 02 means "CHECK CONDITION", i.e.: the command didn't complete successfully. Sense Key 0B means "ABORTED COMMAND". ASC/ASCQ 4400 means "INTERNAL TARGET FAILURE". (You can find this in the document at http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc2r20.pdf)

The reason of the target failure is of course array specific, but the SCSI return codes are standardized. Using the SENSE DATA, you can sometimes pinpoint a problem very well.

Take a look at Primus solution emc92530 regarding these internal target failure errors...

Conor