Need Help to recover from hdisk9 crash on AIX - RS/6000

[CompGeek]

Hi,

We are having a problem with a hard disk on our RS/6000 (AIX 4.3). One of the
hard disks is giving an I/O Error.

Never having faced such an error / crisis before, we are unable to go on. Could
someone please specify the steps that need to be taken to analyse the error and,
if possible, to repair the Hard Disk 9.

An extract of the "errpt -a" is attached to this email. The two unique errors
are attached.

Thanx

With warm regards,

NP



========= Extract of "errpt -a" for two selected messages =========


---------------------------------------------------------------------------
LABEL: LVM_IO_FAIL
IDENTIFIER: 613E5F38

Date/Time: Tue Sep 23 03:27:56
Sequence Number: 4270
Machine Id: 000FC08F4C00
Node Id: ted
Class: H
Type: PERM
Resource Name: LVDD
Resource Class: NONE
Resource Type: NONE
Location: NONE

Description
I/O ERROR DETECTED BY LVM

Probable Causes
POWER, DRIVE, ADAPTER, OR CABLE FAILURE

Recommended Actions
RUN DIAGNOSTICS AGAINST THE FAILING DEVICE

Detail Data
PHYSICAL VOLUME DEVICE MAJOR/MINOR
000E 000A
ERROR CODE AS DEFINED IN sys/errno.h
5
BLOCK NUMBER
528648
LOGICAL VOLUME DEVICE MAJOR/MINOR
002C 000E
PHYSICAL BUFFER TRANSACTION TIME
1
SENSE DATA
0000 0811 000F C08F 7925 7F11 0000 0000 0000 0000 000F C08F 7925 8926 0000 0000
0000 0000
---------------------------------------------------------------------------
LABEL: DISK_ERR3
IDENTIFIER: 35BFC499

Date/Time: Tue Sep 23 03:27:56
Sequence Number: 4269
Machine Id: 000FC08F4C00
Node Id: ted
Class: H
Type: PERM
Resource Name: hdisk9
Resource Class: disk
Resource Type: scsd
Location: 40-61-00-8,0
VPD:
Manufacturer................IBM
Machine Type and Model......ST336605LC
FRU Number..................07K9454
ROS Level and ID............43373031
Serial Number...............3FP0VYM0
EC Level....................H31116
Part Number.................07K9428
Device Specific.(Z0)........000003129F00013E
Device Specific.(Z1)........1109C701
Device Specific.(Z2)........1000
Device Specific.(Z3)........01309
Device Specific.(Z4)........0001
Device Specific.(Z5)........22
Device Specific.(Z6)........162870 C

Description
DISK OPERATION ERROR

Probable Causes
DASD DEVICE
STORAGE DEVICE CABLE

Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
STORAGE DEVICE CABLE

Recommended Actions
PERFORM PROBLEM DETERMINATION PROCEDURES

Detail Data
SENSE DATA
0608 0000 0808 1108 0800 0000 0000 0000 0200 0800 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 0002 2C9A 000C C780
---------------------------------------------------------------------------

[Steve Nottingham]

[email]freakos_arzoo@yahoo.com[/email] (CompGeek) wrote in message news:<4b96ed44.0309222256.7ad083f8@posting.google. com>...

> Hi,
>
> We are having a problem with a hard disk on our RS/6000 (AIX 4.3). One of the
> hard disks is giving an I/O Error.
>
> Never having faced such an error / crisis before, we are unable to go on. Could
> someone please specify the steps that need to be taken to analyse the error and,
> if possible, to repair the Hard Disk 9.
>
> An extract of the "errpt -a" is attached to this email. The two unique errors
> are attached.
>
> Thanx
>
> With warm regards,
>
> NP
>
>
>
> ========= Extract of "errpt -a" for two selected messages =========
>
>
> ---------------------------------------------------------------------------
> LABEL: LVM_IO_FAIL
> IDENTIFIER: 613E5F38
>
> Date/Time: Tue Sep 23 03:27:56
> Sequence Number: 4270
> Machine Id: 000FC08F4C00
> Node Id: ted
> Class: H
> Type: PERM
> Resource Name: LVDD
> Resource Class: NONE
> Resource Type: NONE
> Location: NONE
>
> Description
> I/O ERROR DETECTED BY LVM
>
> Probable Causes
> POWER, DRIVE, ADAPTER, OR CABLE FAILURE
>
> Recommended Actions
> RUN DIAGNOSTICS AGAINST THE FAILING DEVICE
>
> Detail Data
> PHYSICAL VOLUME DEVICE MAJOR/MINOR
> 000E 000A
> ERROR CODE AS DEFINED IN sys/errno.h
> 5
> BLOCK NUMBER
> 528648
> LOGICAL VOLUME DEVICE MAJOR/MINOR
> 002C 000E
> PHYSICAL BUFFER TRANSACTION TIME
> 1
> SENSE DATA
> 0000 0811 000F C08F 7925 7F11 0000 0000 0000 0000 000F C08F 7925 8926 0000 0000
> 0000 0000
> ---------------------------------------------------------------------------
> LABEL: DISK_ERR3
> IDENTIFIER: 35BFC499
>
> Date/Time: Tue Sep 23 03:27:56
> Sequence Number: 4269
> Machine Id: 000FC08F4C00
> Node Id: ted
> Class: H
> Type: PERM
> Resource Name: hdisk9
> Resource Class: disk
> Resource Type: scsd
> Location: 40-61-00-8,0
> VPD:
> Manufacturer................IBM
> Machine Type and Model......ST336605LC
> FRU Number..................07K9454
> ROS Level and ID............43373031
> Serial Number...............3FP0VYM0
> EC Level....................H31116
> Part Number.................07K9428
> Device Specific.(Z0)........000003129F00013E
> Device Specific.(Z1)........1109C701
> Device Specific.(Z2)........1000
> Device Specific.(Z3)........01309
> Device Specific.(Z4)........0001
> Device Specific.(Z5)........22
> Device Specific.(Z6)........162870 C
>
> Description
> DISK OPERATION ERROR
>
> Probable Causes
> DASD DEVICE
> STORAGE DEVICE CABLE
>
> Failure Causes
> DISK DRIVE
> DISK DRIVE ELECTRONICS
> STORAGE DEVICE CABLE
>
> Recommended Actions
> PERFORM PROBLEM DETERMINATION PROCEDURES
>
> Detail Data
> SENSE DATA
> 0608 0000 0808 1108 0800 0000 0000 0000 0200 0800 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 0002 2C9A 000C C780
> ---------------------------------------------------------------------------

You might want to post theoutput of lspv, lspv -l hdisk9, lsvg -l
<volume group that hdisk9 is in (from lspv)>

DISK_ERR3 aren't usually that serious, but you might want your
hardware support vendor to analyse there error report.

Steve

[Nicholas Dronen]

Steve Nottingham <steve@wakefieldrfc.freeserve.co.uk> wrote:
SN> [email]freakos_arzoo@yahoo.com[/email] (CompGeek) wrote in message news:<4b96ed44.0309222256.7ad083f8@posting.google. com>...

>> Hi,
>>
>> We are having a problem with a hard disk on our RS/6000 (AIX 4.3). One of the
>> hard disks is giving an I/O Error.
>>
>> Never having faced such an error / crisis before, we are unable to go on. Could
>> someone please specify the steps that need to be taken to analyse the error and,
>> if possible, to repair the Hard Disk 9.
>>
>> An extract of the "errpt -a" is attached to this email. The two unique errors
>> are attached.

>> ========= Extract of "errpt -a" for two selected messages =========
>>
>>
>> ---------------------------------------------------------------------------
>> LABEL: LVM_IO_FAIL
>> IDENTIFIER: 613E5F38
>>
>> Date/Time: Tue Sep 23 03:27:56
>> Sequence Number: 4270
>> Machine Id: 000FC08F4C00
>> Node Id: ted
>> Class: H
>> Type: PERM
>> Resource Name: LVDD
>> Resource Class: NONE
>> Resource Type: NONE
>> Location: NONE

>> Detail Data
>> PHYSICAL VOLUME DEVICE MAJOR/MINOR
>> 000E 000A
>> ERROR CODE AS DEFINED IN sys/errno.h
>> 5
>> BLOCK NUMBER
>> 528648
>> LOGICAL VOLUME DEVICE MAJOR/MINOR
>> 002C 000E
>> PHYSICAL BUFFER TRANSACTION TIME
>> 1

[ snip ]

>> ---------------------------------------------------------------------------
>> LABEL: DISK_ERR3
>> IDENTIFIER: 35BFC499
>>
>> Date/Time: Tue Sep 23 03:27:56
>> Sequence Number: 4269
>> Machine Id: 000FC08F4C00
>> Node Id: ted
>> Class: H
>> Type: PERM
>> Resource Name: hdisk9
>> Resource Class: disk
>> Resource Type: scsd
>> Location: 40-61-00-8,0
>> VPD:
>> Manufacturer................IBM
>> Machine Type and Model......ST336605LC
>> FRU Number..................07K9454
>> ROS Level and ID............43373031
>> Serial Number...............3FP0VYM0
>> EC Level....................H31116
>> Part Number.................07K9428
>> Device Specific.(Z0)........000003129F00013E
>> Device Specific.(Z1)........1109C701
>> Device Specific.(Z2)........1000
>> Device Specific.(Z3)........01309
>> Device Specific.(Z4)........0001
>> Device Specific.(Z5)........22
>> Device Specific.(Z6)........162870 C

[ snip ]

SN> You might want to post theoutput of lspv, lspv -l hdisk9, lsvg -l
SN> <volume group that hdisk9 is in (from lspv)>

SN> DISK_ERR3 aren't usually that serious, but you might want your
SN> hardware support vendor to analyse there error report.

Please take a moment before posting to trim generic and other
irrelevant information, such as the sense data, from the previous
posts. Reading threads is much easier and much more pleasant
when follow-up-ers take a moment to make things tidy, don't you
think?

Regards,

Nicholas

--
"Why shouldn't I top-post?" [url]http://www.aglami.com/tpfaq.html[/url]
"Meanings are another story." [url]http://www.ifas.org/wa/glossolalia.html[/url]

[Terry Polzin]

[email]freakos_arzoo@yahoo.com[/email] (CompGeek) wrote in message news:<4b96ed44.0309222256.7ad083f8@posting.google. com>...

> Hi,
>
> We are having a problem with a hard disk on our RS/6000 (AIX 4.3). One of the
> hard disks is giving an I/O Error.
>
> Never having faced such an error / crisis before, we are unable to go on. Could
> someone please specify the steps that need to be taken to analyse the error and,
> if possible, to repair the Hard Disk 9.
>
> An extract of the "errpt -a" is attached to this email. The two unique errors
> are attached.
>
> Thanx
>
> With warm regards,
>
> NP

Can you access the logical volumes (lvs) on hdisk9?

What volume group (vg) is hdisk9 in?

Send output of the following commands:

lspv hdisk9
lspv -l hdisk9
lsvg (hdisk9 volume group name)
lsvg -l (hdisk9 volume name)
lsvg -p (hdisk9 volume name)

[Peter Z.]

Nicholas Dronen <ndronen@io.frii.com> wrote in message news:<3f705212$0

>
> Please take a moment before posting to trim generic and other
> irrelevant information, such as the sense data, from the previous
> posts. Reading threads is much easier and much more pleasant
> when follow-up-ers take a moment to make things tidy, don't you
> think?
>
> Regards,
>
> Nicholas

Nicholas,
I don't get you. Who did untie your sleeves?
Please do guard your own posts.

PS. Sorry for my English. I am not native speaker. I just try.

Peter/Germany

[Ricardo Alan]

[email]freakos_arzoo@yahoo.com[/email] (CompGeek) wrote in message news:<4b96ed44.0309222256.7ad083f8@posting.google. com>...

> Hi,
>
> We are having a problem with a hard disk on our RS/6000 (AIX 4.3). One of the
> hard disks is giving an I/O Error.
>
> Never having faced such an error / crisis before, we are unable to go on. Could
> someone please specify the steps that need to be taken to analyse the error and,
> if possible, to repair the Hard Disk 9.
>
> An extract of the "errpt -a" is attached to this email. The two unique errors
> are attached.
>
> Thanx
>
> With warm regards,
>
> NP
>
>
>
> ========= Extract of "errpt -a" for two selected messages =========
>
>
> ---------------------------------------------------------------------------
> LABEL: LVM_IO_FAIL
> IDENTIFIER: 613E5F38
>
> Date/Time: Tue Sep 23 03:27:56
> Sequence Number: 4270
> Machine Id: 000FC08F4C00
> Node Id: ted
> Class: H
> Type: PERM
> Resource Name: LVDD
> Resource Class: NONE
> Resource Type: NONE
> Location: NONE
>
> Description
> I/O ERROR DETECTED BY LVM
>
> Probable Causes
> POWER, DRIVE, ADAPTER, OR CABLE FAILURE
>
> Recommended Actions
> RUN DIAGNOSTICS AGAINST THE FAILING DEVICE
>
> Detail Data
> PHYSICAL VOLUME DEVICE MAJOR/MINOR
> 000E 000A
> ERROR CODE AS DEFINED IN sys/errno.h
> 5
> BLOCK NUMBER
> 528648
> LOGICAL VOLUME DEVICE MAJOR/MINOR
> 002C 000E
> PHYSICAL BUFFER TRANSACTION TIME
> 1
> SENSE DATA
> 0000 0811 000F C08F 7925 7F11 0000 0000 0000 0000 000F C08F 7925 8926 0000 0000
> 0000 0000
> ---------------------------------------------------------------------------
> LABEL: DISK_ERR3
> IDENTIFIER: 35BFC499
>
> Date/Time: Tue Sep 23 03:27:56
> Sequence Number: 4269
> Machine Id: 000FC08F4C00
> Node Id: ted
> Class: H
> Type: PERM
> Resource Name: hdisk9
> Resource Class: disk
> Resource Type: scsd
> Location: 40-61-00-8,0
> VPD:
> Manufacturer................IBM
> Machine Type and Model......ST336605LC
> FRU Number..................07K9454
> ROS Level and ID............43373031
> Serial Number...............3FP0VYM0
> EC Level....................H31116
> Part Number.................07K9428
> Device Specific.(Z0)........000003129F00013E
> Device Specific.(Z1)........1109C701
> Device Specific.(Z2)........1000
> Device Specific.(Z3)........01309
> Device Specific.(Z4)........0001
> Device Specific.(Z5)........22
> Device Specific.(Z6)........162870 C
>
> Description
> DISK OPERATION ERROR
>
> Probable Causes
> DASD DEVICE
> STORAGE DEVICE CABLE
>
> Failure Causes
> DISK DRIVE
> DISK DRIVE ELECTRONICS
> STORAGE DEVICE CABLE
>
> Recommended Actions
> PERFORM PROBLEM DETERMINATION PROCEDURES
>
> Detail Data
> SENSE DATA
> 0608 0000 0808 1108 0800 0000 0000 0000 0200 0800 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 0002 2C9A 000C C780
> ---------------------------------------------------------------------------

Hi, good morning, NP...How are you doing?

Okay, let´s go...these two erros in errpt -a came together all the
times, okay?...This is the cause of a Filesystem corruption so, I
would recommend you run the fsck for all filesystems, I mean, hd1,
hd2, hd3 and hd4 in Maintenance mode (filesystem must be unmounted).

This step can solve the problem...

Please, let me know if it works or not, okay?

Best Regards