Disk Operation Error question 1

[Mag0007]

While looking at the errpt I get the following:
LABEL: SC_DISK_ERR4
IDENTIFIER: 67581038

Date/Time: Sun Dec 11 00:04:06
Sequence Number: 83638
Machine Id: 00053F8F4C00
Node Id: cold
Class: H
Type: TEMP
Resource Name: hdisk101
Resource Class: disk
Resource Type: osdisk
Location: 14-08-01
VPD:
Manufacturer................EMC
Machine Type and Model......SYMMETRIX
Part Number.................
ROS Level and ID............35363730
Serial Number...............5736C000
EC Level....................p^GW^L^E
FRU Number..................
Device Specific.(Z0)........000003329000001A
Device Specific.(Z1)........Q
Device Specific.(Z2)........
Device Specific.(Z3)........
Device Specific.(Z4)........T^S
Device Specific.(Z5)........ßM-^@

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
SENSE DATA
0A00 2800 0337 9C80 0000 4000 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 000E 5A3A 0000 0580 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000


Could this be a faulty fibercard? or bad SAN disk? Any ideas?

 

[mrn]

I'd suspect a bad disk. Is the SAN reporting any errors?

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant."

http://www.airport-parking-site.co.uk/

 

[p5wizard]

If that LUN is (part of) a raid array, OS shouldn't even see that a (raid member) disk in the EMC has gone bad. However, I get these types of errors also (ESS LUNs RAID5). Mostly generated because of an induced SCSI reset somewhere on the SAN or the SAN server.

It is a TEMP error, and your multipathing software should be able to deal with it: retry on another path for the same LUN, or just retry on the same path.

You may be able to get rid of these errors by applying the latest fix to the FC disk device driver, or by applying the latest AIX RM level. What level are you currently on? (oslevel -r). Might even be related to the microcode level currently on your FC adapter.




HTH,

p5wizard

 

[Mag0007]

oslevel= 4.3.3 ML 9
i will see if the SAN team has any news!

p5wiz, thanks for the good help!

 

[Mag0007]

p5wiz:

you are correct! the SAN team was doing maintenence (microcode upgrade)

 

[p5wizard]

Wow! Without informing all SAN clients about it first? Mostly, a SAN team would first make sure that all SAN client machines are at the correct OS level and have necessary patches to FC dev drivers and/or multipathing drivers, so a concurrent microcode upgrade to SAN hardware is survivable for all...


HTH,

p5wizard

 

[Mag0007]

p5wiz:
hehhe, I wish I worked for you

i work in a pretty large scale environment