PANIC!!! "disk operation error" - what do I do.
Nir Levy
Hello,
please help.
I'm getting in my error log the following messages:
(this is just a part of the messages, the rest is at the end)
>LABEL: DISK_ERR1
>Resource Name: hdisk1
>Resource Class: disk
>
>Description
>DISK OPERATION ERROR
>
>Probable Causes
>MEDIA
>
>User Causes
>MEDIA DEFECTIVE
>
>Failure Causes
>MEDIA
>DISK DRIVE
>
and:
>LABEL: LVM_HWFAIL
>
>Description
>HARDWARE DISK BLOCK RELOCATION FAILED
>
>Probable Causes
>DEVICE DOES NOT SUPPORT HW RELOCATION
>DASD DEVICE
>
>Failure Causes
>DEVICE DOES NOT SUPPORT HW RELOCATION
>DASD MEDIA
>DISK DRIVE
>DISK DRIVE ELECTRONICS
>
I'm using AIX4.2 . Please let me know what to do. the disk is currently
working fine but I don't wish to have a major crash.
Should I replace the disk or should I just ignore the error.
full entires of error log below. I thank you very much.
Nir.
---------------------------------------------------------------------------
LABEL: DISK_ERR1
IDENTIFIER: 21F54B38
Date/Time: Wed Jul 8 15:16:07
Sequence Number: 42
Machine Id: 00152885C000
Node Id: amsys2000
Class: H
Type: PERM
Resource Name: hdisk1
Resource Class: disk
Resource Type: 2200mb16bit
Location: 04-C0-00-1,0
VPD:
Manufacturer................IBMRISC
Machine Type and Model......DFHSS2W
Part Number.................74G6984
ROS Level and ID............34313431
Serial Number...............68388292
EC Level....................486506
FRU Number..................74G7007
Device Specific.(Z0)........000002029F00003E
Device Specific.(Z1)........RAMST04A
Device Specific.(Z2)........09RI
Device Specific.(Z3)........96004
Device Specific.(Z4)........0002
Device Specific.(Z5)........22
Device Specific.(Z6)........E38411
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
0A01 0000 2800 0036 9F4D 0000 0100 0000 0102 0000 F000 0300 369F 4D18 0000 0000
110B 0080 0032 0000 01D2 0000 0D74 0749 0049 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 028E 0001 6E80
---------------------------------------------------------------------------
LABEL: LVM_HWFAIL
IDENTIFIER: C67E7D0F
Date/Time: Wed Jul 8 15:15:42
Sequence Number: 39
Machine Id: 00152885C000
Node Id: amsys2000
Class: H
Type: UNKN
Resource Name: LVDD
Resource Class: NONE
Resource Type: NONE
Location: NONE
Description
HARDWARE DISK BLOCK RELOCATION FAILED
Probable Causes
DEVICE DOES NOT SUPPORT HW RELOCATION
DASD DEVICE
Failure Causes
DEVICE DOES NOT SUPPORT HW RELOCATION
DASD MEDIA
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
IF HW RELOCATION NOT SUPPORTED ON DEVICE NO ACTION REQUIRED
PERFORM PROBLEM DETERMINATION PROCEDURES
Detail Data
MAJOR/MINOR DEVICE NUMBER
000E 0001
BLOCK NUMBER
3579703
---------------------------------------------------------------------------
--
Nir Levy, The above opinions are my own,
nlevy @ usa.net not my employer's.
--
I didn't do it; Nobody saw me do it;
You can't prove anything; -Bart Simpson
--
Dischner Anton
maybe the spare blocks if you harddisk are exhausted.
maybe your drive does not support bad block relocation.
Change the drive now!
Kind regards,
Toni
dischner@_NOSPAM_klch.med.uni-muenchen.de
please remove _NOSPAM_ for mail.
Super Dave Mac
most probably related to the disk drive's microelectronics.
Almost all IBM drives, except for the very old ones (400MB
or less, usually) support hardware bad block relocation.
Even so, you should have seen an LVM_SWREL "error"
logged after the LVM_HWFAIL message. This would
indicate that the LVM performed a software relocation
of the bad block because the hardware relocation
failed. In any case, I would suspect the drive needs
replacement soon. In the mean time, make frequent
backups!
--
My opinions are completely my own. As for my heart and soul,
I'm not so sure....but my ass definately belongs to the IRS.
Dischner Anton wrote in message ...
Nir Levy
>A DISK_ERR1 error usually identifies a permanent condition,
>most probably related to the disk drive's microelectronics.
>Almost all IBM drives, except for the very old ones (400MB
>or less, usually) support hardware bad block relocation.
>Even so, you should have seen an LVM_SWREL "error"
>logged after the LVM_HWFAIL message. This would
>indicate that the LVM performed a software relocation
>of the bad block because the hardware relocation
>failed.
I didn't get it.
>In any case, I would suspect the drive needs
>replacement soon.
I will.
> In the mean time, make frequent
>backups!
I do.
thanks all for the reply.
Nir.
--
Nir Levy, The above opinions are my own,
nlevy @ usa.net not my employer's.
--
Norman Levin
disk architecture (count/key/data, count/data, Extended Count/K/Data)
and a variety of IBM disk caching algorithms. Is there an online
tutorial that covers scsi disks? I'm completely bewildered by a
formatting operation would 'time out' on a 9gb drive! Most drives
that I know about have a formating write (per track) or with track
overflow, a full cylinder. The idea that there is a formatting write
that goes for the full extent of a disk is new/foreign to me. Any
pointers would be appreciated. Don't worry how detailed, I used to
program at the 'channel program level' and hardware doesn't scare me
unless it whines, screams, howls... ooops... that's my home life.
> From: "Super Dave Mac" <mcc...@airmail.net>
> Date: Thu, 9 Jul 1998 23:36:44 -0500
> Subject: Re: PANIC!!! "disk operation error" - what do I do.
Kevin Gee
>
> A DISK_ERR1 error usually identifies a permanent condition,
> most probably related to the disk drive's microelectronics.
> Almost all IBM drives, except for the very old ones (400MB
> or less, usually) support hardware bad block relocation.
> logged after the LVM_HWFAIL message. This would
> indicate that the LVM performed a software relocation
> of the bad block because the hardware relocation
> replacement soon. In the mean time, make frequent
> backups!
DISK_ERR2 is usually an electronics problem. DISK_ERR1 is usually a
media problem. DISK_ERR3 is a "communications" problem with the drive.
Just FYI...
> --
> My opinions are completely my own. As for my heart and soul,
> I'm not so sure....but my ass definately belongs to the IRS.
> Dischner Anton wrote in message ...
> >Hi Nir,
> >
> >maybe the spare blocks if you harddisk are exhausted.
> >maybe your drive does not support bad block relocation.
> >
> >Change the drive now!
> >
> >Kind regards,
> >
> >Toni
> >
> >dischner@_NOSPAM_klch.med.uni-muenchen.de
> >please remove _NOSPAM_ for mail.
> >
> >> I didn't do it; Nobody saw me do it;
> >> You can't prove anything; -Bart Simpson
> >> --
> >>
--
Kevin Gee
ge...@cse.uta.edu Graduate Student, Univ. of Texas at Arlington
kr...@us.ibm.com AIX Software Analyst, IBM Product Support Services
IBM and UTA are not responsible for my opinions.
Dave Hill
>
> DISK_ERR2 is usually an electronics problem. DISK_ERR1 is usually a
> media problem. DISK_ERR3 is a "communications" problem with the drive.
> Just FYI...
>
DISK_ERR4 seems to be a media problem also.
Dave Hill
--
"Using encryption on the Internet is the equivalent of arranging an
armored car to deliver credit-card information from someone living in a
cardboard box to someone living on a park bench." - Gene Spafford.
Kevin Gee
>
> Kevin Gee wrote:
> >
> > DISK_ERR2 is usually an electronics problem. DISK_ERR1 is usually a
> > media problem. DISK_ERR3 is a "communications" problem with the drive.
> > Just FYI...
> >
>
> DISK_ERR4 seems to be a media problem also.
It's a temporary error. You shouldn't ignore it, but it doesn't
automatically mean you should pull out the backup tape like the other 3
usually do.
Scott L. Fields
This could be due to a bad block relocation, a command timeout that was
retried successfully, etc.
I wouldn't simplify it the point you give.
Dave Hill wrote:
> Kevin Gee wrote:
> >
> > DISK_ERR2 is usually an electronics problem. DISK_ERR1 is usually a
> > media problem. DISK_ERR3 is a "communications" problem with the drive.
> > Just FYI...
> >
>
> DISK_ERR4 seems to be a media problem also.
>