Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AIX 4.3.3 DIAG and SSA/Pdisk Problem

Status
Not open for further replies.

jpor

Technical User
Nov 29, 2000
212
GB
Hi,

We currently have a Development Box situated outside the company I work for. At the moment I keep getting error messages from the G40 running AIX 4.3.3 about a problem with the ssa0 and Pdisk2 situated in it. I have run the 'diag' command and only get the following information:

A PROBLEM WAS DETECTED ON Tue May 13 12:19:30 BST 2003 801014

The Service Request Number(s)/Probable Cause(s)
(causes are listed in descending order of probability):

d0300: Use the Service Guide for your SSA Adapter or SSA Subsystem.
SSA-SUBSYSTEM 00-01-P

When I look in the errpt logs I get the following:

LABEL: SSA_DISK_ERR4
IDENTIFIER: F7863CFE

Date/Time: Tue May 13 12:19:29
Sequence Number: 7262
Machine Id: 00093A7EA700
Node Id: g40_dev2
Class: H
Type: PERM
Resource Name: pdisk2
Resource Class: pdisk
Resource Type: scsd
Location: 00-01-P
VPD:
Manufacturer................IBM
Machine Type and Model......DRVC
Part Number.................
ROS Level and ID............0022
Serial Number...............0000000000
EC Level....................
Device Specific.(Z2)........CUSHA022
Device Specific.(Z3)........
Device Specific.(Z3)........
Device Specific.(Z4)........

Description
DISK OPERATION ERROR

Probable Causes
DASD DEVICE

Failure Causes
DISK DRIVE

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
SENSE DATA
7000 0200 0000 0018 0000 0000 0402 0000 0000 0000 0101 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
---------------------------------------------------------------------------

Could anyone please provide me any info where I should be looking ? Unfortunately I cannot get my hands on the SSA Manual as it has gone missing.

Thanks in Advance,

Jon.
 
Also got this from the errpt:

LABEL: SSA_DEVICE_ERROR
IDENTIFIER: FE9E9357

Date/Time: Tue May 13 12:00:01
Sequence Number: 7261
Machine Id: 00093A7EA700
Node Id: g40_dev2
Class: H
Type: PERM
Resource Name: ssa0
Resource Class: adapter
Resource Type: ssa
Location: 00-01
VPD:
Part Number.................025L5817
Serial Number...............F9620086
EC Level....................0000F24703
Manufacturer................IBM053
ROS Level and ID............7601
Loadable Microcode Level....04
Device Driver Level.........00
Displayable Message.........SSA-ADAPTER
Displayable Message.........SSA-ADAPTER
Device Specific.(Z0)........DRAM=032
Device Specific.(Z1)........CACHE=0
Device Specific.(Z2)........00000020354e9ffc

Description
DISK OPERATION ERROR

Probable Causes
DASD DEVICE

Failure Causes
DISK DRIVE

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
ERROR CODE
0440 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

Thanks again.
 
Check these links: It says the D0300 error means you need to replace the disk.

and
Somewhere out on IBM's site you can download the doc that has gone missing, but I can't find it today.

Check the status of your arrays. If the disk is part of an array, the array will not be in a good state. Until the new disk gets in, if you don't have hot spares set up, you could swap an unused disk for the disk that has gone bad.
 
Thanks Bi.

I will check out those Links.

 
You also might want to check this link:
It appears that you are two versions behind on microcode for the disks, but you are OK with the SSA card. Being behind on the microcode didn't cause the problem with the disk, but IBM might tell you to get the microcode level up to the current version.
 
And that is where you should find the doc. (finally!)
 
Thanks again Bi.

Your a life saver.

Jon.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top