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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HD error

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
does anybody know how to deal with this aside from replacing the Hard Disk?

i appreciate any suggestion/s:

---------------------------------------------------------------------------
LABEL: DISK_ERR1
IDENTIFIER: 21F54B38

Date/Time: Wed Sep 19 08:40:05
Sequence Number: 5050
Machine Id: 00FFFFFF4C00
Node Id: ivanhoe
Class: H
Type: PERM
Resource Name: hdisk0
Resource Class: disk
Resource Type: 2200mb
Location: 04-B0-00-5,0
VPD:
Manufacturer................IBM
Machine Type and Model......DFHSS2F !d
Part Number.................06H3370
ROS Level and ID............34313431
Serial Number...............68445958
EC Level....................486506
FRU Number..................21H0772
Device Specific.(Z0)........000002029F00001E
Device Specific.(Z1)........RAMST04A
Device Specific.(Z2)........09RI
Device Specific.(Z3)........96037
Device Specific.(Z4)........0002
Device Specific.(Z5)........22
Device Specific.(Z6)........D46995

Description
DISK OPERATION ERROR

Probable Causes
MEDIA

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
0A05 0000 2800 002F 7886 0000 0100 0000 0102 0000 F000 0300 2F78 8618 0000 0000
110B 0080 0032 0000 01D2 0000 0B8E 060A 000A 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 031D 000E 7EC0
---------------------------------------------------------------------------
 
Have you run diag on the disk?

On the command line, type diag and choose the Advanced Diagnostic Routines. In the next screen choose Problem Determination. In the next screen scroll down the list and select the disk that is giving you trouble. I also will choose the IO card that the disk is attached to.

For advanced testing, you will be told to bring the system down to service mode or to make the disk available for additional testing. This requires getting all data off the disk and removing it from the volume group. I will usually mirror the LVs on the affected disk to another disk and then break the mirror, gradually moving all data off the affected disk. Then diag runs a certification on the disk.

If a lot of problems are found, the certification stops and you are advised to replace the disk. Sometimes no real problems are found.

Your disk is a smaller disk, so I am assuming it's older. It may be time to replace it.

Good luck.
 
This error "DISK OPERATION ERRO" can occur when the system tries to write to the disk, but finds that it can't for some strange esoteric reason.

I've had this same error on a number of occasions, usually three or times over a two month period and diags reports nothing wrong... which may be the case.

However, I personally operate a 'three strikes and you're out' policy in cases like this just to be sure.

If diags shows nothing wrong, wait and see if you get the same error again then decide - I'm assuming that the data is mirrored or similar though.

Cheers,
Dave V.
 
thanks to both of you.

i think i have to do some mirroring and transfer LVs.
 
ok...are you willing to help?

actually - i'm not happy to do such horrible task, but i guess i'm running out of options.

what help do you provide? free?
 
Of course! That's what tek-tips is all about isn't it :)

First of all I'd need to know version of AIX you're using and whether you are trying to mirror the rootvg?

Dave V.
 
vickersdc,

thank you. silly me.

yeah! for now i can't think of anything except mirroring the rootvg. i am using AIX 4.2.1

i got these two VGs: rootvg and datavg. each resides on one HD. i tried "savevg" but only works for datavg.

for rootvg:

* i always got this "mksysb backup complete with errors".

* i tried fsck (with -p & -y under maint mode, exit, sync3x & shutdown -Fr) for each LVs and tried mksysb, nothing changed - but one time - it's strange, processing keeps on looping back "backing up file (0%)........" for hours that i decided to stop it.

* i would appreciate detailed steps to fix this. though the system is still running fine but concern about the failing HD for rootvg.


 
by the way ...the system runs AIX 4.2.1 and has no "diag"

# diag
The 'diag' command is not supported on this sytem.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top