From: Javier González Arenas [ conatel ] (jgonzalez@conatel.com.uy)
Date: Wed May 11 2005 - 11:22:16 EDT
In my case ( dev_t=0x1f000000 ) the disk to be replaced is /dev/dsk/c0t0d0.
The explanation you sent is below.
I think I'll be busy this weekend the faulty disk is one of four disks of an
splitted logical volume.
Thanks again
Best regards
The following command will show you the HW path of the disk that is
failing:
# ioscan -f /dev/dsk/c0t0d0
When you see the "dev_t" value, match up the last 6 digits to the hex
numbers in /dev/dsk - in your case, the last 6 digits are 000000, and
that matches the 0x000000 number for /dev/dsk/c0t0d0
----- Original Message -----
From: "Javier González Arenas [ conatel ]" <jgonzalez@conatel.com.uy>
To: "hpux-admin" <hpux-admin@DutchWorks.nl>
Sent: Wednesday, May 11, 2005 11:58 AM
Subject: [HPADM] Re: physical volume powerfailed
Hello there,
Thanks for your suggestions about the powerfailing disk, I'll take the
correcting actions in this order:
- check the scsi cables
- replace the disk
- replace the scsi controller
By the way, given the following message, which disk is supposed to be
replaced ?
May 6 17:20:47 parma2 vmunix: LVM: vg[1]: pvnum=3 (dev_t=0x1f000000) is
POWERFAILED
I've got the following disks on my system::
root@parma2:/>ll /dev/dsk/*
brw-r----- 1 bin sys 31 0x000000 Mar 25 1999
/dev/dsk/c0t0d0
brw-r----- 1 bin sys 31 0x005000 Mar 24 1999
/dev/dsk/c0t5d0
brw-r----- 1 bin sys 31 0x006000 Mar 24 1999
/dev/dsk/c0t6d0
brw-r----- 1 bin sys 31 0x008000 Aug 29 2003
/dev/dsk/c0t8d0
brw-r----- 1 bin sys 31 0x013000 Mar 24 1999
/dev/dsk/c1t3d0
brw-r----- 1 bin sys 31 0x014000 Mar 24 1999
/dev/dsk/c1t4d0
brw-r----- 1 bin sys 31 0x015000 Mar 24 1999
/dev/dsk/c1t5d0
brw-r----- 1 bin sys 31 0x016000 Mar 24 1999
/dev/dsk/c1t6d0
brw-r----- 1 bin sys 31 0x026000 Mar 24 2000
/dev/dsk/c2t6d0
brw-r----- 1 bin sys 31 0x032000 Mar 24 1999
/dev/dsk/c3t2d0
Best regards,
javier
----- Original Message -----
From: "Javier González Arenas [ conatel ]" <jgonzalez@conatel.com.uy>
To: "hpux-admin" <hpux-admin@DutchWorks.nl>
Sent: Tuesday, May 10, 2005 5:23 PM
Subject: [HPADM] [hpadm] physical volume powerfailed
> Hello there,
>
> I'm getting sporadically the following error in syslog.log:
>
> May 6 17:20:47 parma2 vmunix: LVM: vg[1]: pvnum=3 (dev_t=0x1f000000)
is
> POWERFAILED
> May 6 17:54:46 parma2 vmunix: DIAGNOSTIC SYSTEM WARNING:
> May 6 17:54:46 parma2 vmunix: The diagnostic logging facility has
> started receiving excessive
> May 6 17:54:46 parma2 vmunix: errors from the I/O subsystem. I/O
> error entries will be lost
> May 6 17:54:46 parma2 vmunix: until the cause of the excessive I/O
> logging is corrected.
> May 6 17:54:46 parma2 vmunix: If the diaglogd daemon is not
active,
> use the Daemon Startup command
> May 6 17:54:46 parma2 vmunix: in stm to start it.
> May 6 17:54:46 parma2 vmunix: If the diaglogd daemon is active,
use
> the logtool utility in stm
> May 6 17:54:46 parma2 vmunix: to determine which I/O subsystem is
> logging excessive errors.
>
>
> The applications hung and only a reboot can make things work again.
>
> Anyone had overcome this issue in the past and wants to give advice.
>
> Thanks again,
> javier
>
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact
majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner:
owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse
only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse &
search)
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:47 EDT