RAID adapter error in Rs6000 F80

[samirm]

Hi,

We have Rs6000 F80 . Last night few errors encountered in errpt as follows :-

8AC43378 0618000903 T H scraid0 ADAPTER ERROR
8AC43378 0618000903 T H scraid0 ADAPTER ERROR
5ABCCC6B 0618000903 T H scraid0 DISK OPERATION ERROR
8AC43378 0618000903 T H scraid0 ADAPTER ERROR
8AC43378 0618000903 T H scraid0 ADAPTER ERROR

Error description is as follows :-

---------------------------------------------------------------------------
LABEL: SCSI_ARRAY_ERR4
IDENTIFIER: 5ABCCC6B

Date/Time: Wed Jun 18 00:09:36
Sequence Number: 151336
Machine Id: 00015A4F4C00
Node Id: bramha
Class: H
Type: TEMP
Resource Name: scraid0
Resource Class: adapter
Resource Type: 14102e00
Location: 37-08
VPD:
Part Number.................00N9585
EC Level....................E73829H
Serial Number...............0015JF22
FRU Number..................37L6892
Manufacturer................IBM
Displayable Message.........UL3RAID
Diagnostic Level............04
Device Driver Level.........04
Loadable Microcode Level....4.84.01
ROS Level and ID............4.00.26

Description
DISK OPERATION ERROR

Probable Causes
DASD MEDIA
DASD DEVICE

Failure Causes
DASD MEDIA
DISK DRIVE

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
SENSE DATA
0000 0030 1C20 0000 0000 8202 0001 588B F108 6000 0803 4000 0000 0000 0000 0000
---------------------------------------------------------------------------


LABEL: SCSI_ARRAY_ERR9
IDENTIFIER: 8AC43378

Date/Time: Wed Jun 18 00:09:37
Sequence Number: 151339
Machine Id: 00015A4F4C00
Node Id: bramha
Class: H
Type: TEMP
Resource Name: scraid0
Resource Class: adapter
Resource Type: 14102e00
Location: 37-08
VPD:
Part Number.................00N9585
EC Level....................E73829H
Serial Number...............0015JF22
FRU Number..................37L6892
Manufacturer................IBM
Displayable Message.........UL3RAID
Diagnostic Level............04
Device Driver Level.........04
Loadable Microcode Level....4.84.01
ROS Level and ID............4.00.26

Description
ADAPTER ERROR

Probable Causes
DASD DEVICE
CABLE
SCSI BACKPLANE
SCSI REPEATER

Failure Causes
DISK DRIVE
CABLE LOOSE OR DEFECTIVE
SCSI BACKPLANE
SCSI REPEATER

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
SENSE DATA
0000 0088 10F3 1100 1004 0319 9E9A 8E3C 0211 1111 9E9A 8E3C 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
-------------------------------------------------------------------

Please find the output of lscfg for RAID ..

DEVICE LOCATION DESCRIPTION

scraid0 37-08 PCI 4-Channel Ultra3 SCSI RAID
Adapter

Part Number.................00N9585
EC Level....................E73829H
Serial Number...............0015JF22
FRU Number..................37L6892
Manufacturer................IBM
Displayable Message.........UL3RAID
Diagnostic Level............04
Device Driver Level.........04
Loadable Microcode Level....4.84.01
ROS Level and ID............4.00.26
Device Specific.(YL)........P1-I10/Q1


PLATFORM SPECIFIC

Name: raid
Node: raid@1
Physical Location: P1-I10/Q1

My qestion is :-
1. Is this a serious problem ?

2. Is Microcode updation required ?

3. How can I determine whether Microcode needs to be updated for any device ? I know there is a calculation ...but I can't recall it ..

Thanks in advance ...

Sam

 

[zaxxon]

Hi,

not sure if you have checked anything else but the errpt, but here are some steps that might help to identify or solve the problem:

Isn't there a configuration tool/software for the adapter and check the status? If there isn't a separate software for that, maybe it's integrated in some smit menue. Does a "lsdev -Cc adapter | grep -i raid0" show that it is currently available?
Are you missing any Filesystems (df -k)?
Can you still access all files and directories? Maybe try a "find . -print" all over the filesystems, that are placed on the raid array to check this.
Or just open the rs6k-box and check if any cable is not correctly connected.

If you can't find any problem and all LEDs of the drives are in the correct color, all cables are proper connected, all filesystems can be accessed, the configuration tool for your raid adapter shows no errors, and the errors are not occuring again, you might want to forget the problem or do a microcode update.

If a microcode update is necessary or not, might tell you the company you got the Raid adapter from or maybe their website.

For me, it looks like either one of
- these "ghostly" errors, that don't really harm anything and only show up once a year
- like a cable not properly connected between adapter and drives
- like a damage raid-controller

 

[samirm]

Hi Zaxxon ..

I can access all the file systems ...and my database is also running smoothly without giving any error ...only that chunk of errors viewed in errpt output ...which happened yesterday late night ..since morning no such error reported in errpt output ..

You may be right ....I need microcode updation for this.

Thanks ...

Sam