Unsolved
This post is more than 5 years old
36 Posts
0
9908
November 4th, 2008 12:00
SC_DISK_ERR4 in AIX host
The Nulss4 server log (see errpt) is intermittently reporting a SC_DISK_ERR4 error at location U5791.001.99B0NWM-P1-C08-T1-W50060E8004F3AF09-L10000000000000.
Can this hardware error be investigated please
LABEL: SC_DISK_ERR4
IDENTIFIER: DCB47997
Date/Time: Fri Oct 31 09:28:24 GMT 2008
Sequence Number: 66142
Machine Id: 00xxxxxxxx00
Node Id: nulss4
Class: H
Type: TEMP
Resource Name: hdisk25
Resource Class: disk
Resource Type: Hitachi
Location: U5791.001.99B0NWM-P1-C08-T1-W50060E8004F3AF09-L17000000000000
VPD:
Manufacturer................HITACHI
Machine Type and Model......OPEN-V
Part Number.................
ROS Level and ID............35303039
Serial Number...............50 0F3AF
EC Level....................
FRU Number..................
Device Specific.(Z0)........00000332CF000002
Device Specific.(Z1)........05C4 1K ^A^A^A^A
Device Specific.(Z2)........^EM-^P^E^E
Device Specific.(Z3)........ÿ
Device Specific.(Z4)........É_M-^Zû
Device Specific.(Z5)........
Device Specific.(Z6)........
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
Standard input
***********************Can any one suggest any solution on this?**********************
Message was edited by: KCSCP Removed Machine ID.
Can this hardware error be investigated please
LABEL: SC_DISK_ERR4
IDENTIFIER: DCB47997
Date/Time: Fri Oct 31 09:28:24 GMT 2008
Sequence Number: 66142
Machine Id: 00xxxxxxxx00
Node Id: nulss4
Class: H
Type: TEMP
Resource Name: hdisk25
Resource Class: disk
Resource Type: Hitachi
Location: U5791.001.99B0NWM-P1-C08-T1-W50060E8004F3AF09-L17000000000000
VPD:
Manufacturer................HITACHI
Machine Type and Model......OPEN-V
Part Number.................
ROS Level and ID............35303039
Serial Number...............50 0F3AF
EC Level....................
FRU Number..................
Device Specific.(Z0)........00000332CF000002
Device Specific.(Z1)........05C4 1K ^A^A^A^A
Device Specific.(Z2)........^EM-^P^E^E
Device Specific.(Z3)........ÿ
Device Specific.(Z4)........É_M-^Zû
Device Specific.(Z5)........
Device Specific.(Z6)........
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
Standard input
***********************Can any one suggest any solution on this?**********************
Message was edited by: KCSCP Removed Machine ID.
0 events found
No Events found!
MikeMac1
2 Intern
•
292 Posts
0
November 4th, 2008 12:00
Machine Type and Model......OPEN-V
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.
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
November 4th, 2008 16:00
laurentp1
1 Rookie
•
11 Posts
0
November 5th, 2008 06:00
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.
xe2sdc
6 Operator
•
2.8K Posts
0
November 6th, 2008 02:00
How did you call them ?? SBC and SPC ??
Jurjen_Oskam
56 Posts
2
November 6th, 2008 02:00
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.
Conor
341 Posts
0
November 24th, 2008 07:00
Conor
DanielVolochen
4 Posts
0
May 6th, 2010 06:00
Hi All,
Last week i've got some errors like this, but was related to many storages arrays (at least 3 in each site) and ocurred with hosts in 2 diferent sites.
My question is, could this error be related to some kind of problem in SAN? Because it'll be amazing to have this problem in more than 1 storage array at same time.
Regards,
Daniel Volochen