topic vgchange -c n vgdb error in Operating System - HP-UX

vgchange -c n vgdb error

Ionut Grigorescu_2 — Fri, 25 Aug 2006 06:28:27 GMT

vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c5t11d0":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Could not attach to volume group "vgdb" all of
its physical volumes.
vgchange: Warning: couldn't query physical volume "/dev/dsk/c5t11d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 36.4GST336607LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
disk 3 0/10/0/0.0.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 4 0/10/0/0.1.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t1d0 /dev/rdsk/c4t1d0
disk 5 0/10/0/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC
/dev/dsk/c4t2d0 /dev/rdsk/c4t2d0
disk 6 0/10/0/0.3.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC
/dev/dsk/c4t3d0 /dev/rdsk/c4t3d0
disk 7 0/10/0/0.8.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t8d0 /dev/rdsk/c4t8d0
disk 8 0/10/0/0.9.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t9d0 /dev/rdsk/c4t9d0
disk 9 0/10/0/0.10.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t10d0 /dev/rdsk/c4t10d0
disk 10 0/10/0/0.11.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t11d0 /dev/rdsk/c4t11d0
disk 11 0/10/0/0.12.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t12d0 /dev/rdsk/c4t12d0
disk 12 0/10/0/0.13.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c4t13d0 /dev/rdsk/c4t13d0
disk 13 0/12/0/0.0.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 14 0/12/0/0.1.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c5t1d0 /dev/rdsk/c5t1d0
disk 15 0/12/0/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
disk 16 0/12/0/0.3.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c5t3d0 /dev/rdsk/c5t3d0
disk 17 0/12/0/0.8.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC
/dev/dsk/c5t8d0 /dev/rdsk/c5t8d0
disk 18 0/12/0/0.9.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC
/dev/dsk/c5t9d0 /dev/rdsk/c5t9d0
disk 19 0/12/0/0.10.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c5t10d0 /dev/rdsk/c5t10d0
disk 20 0/12/0/0.11.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC
/dev/dsk/c5t11d0 /dev/rdsk/c5t11d0
disk 21 0/12/0/0.12.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
# ll /dev/dsk/c5t11d0

brw-r----- 1 bin sys 31 0x05b000 May 30 2005 /dev/dsk/c5t11d0
# ll /dev/rdsk/c5t11d0

crw-r----- 1 bin sys 188 0x05b000 Jun 2 2005 /dev/rdsk/c5t11d0
# strings /etc/lvmtab

/dev/vg00
/dev/dsk/c2t2d0
/dev/dsk/c1t2d0
/dev/vgnms
/dev/dsk/c4t0d0
/dev/dsk/c5t0d0
/dev/vgdb01
/dev/dsk/c4t1d0
/dev/dsk/c5t1d0
/dev/vgosspkg1
/dev/dsk/c4t8d0
/dev/dsk/c5t8d0
/dev/vgdb
/dev/dsk/c4t2d0
/dev/dsk/c4t3d0
/dev/dsk/c4t9d0
/dev/dsk/c4t10d0
/dev/dsk/c4t11d0
/dev/dsk/c4t12d0
/dev/dsk/c5t12d0
/dev/dsk/c5t11d0
/dev/dsk/c5t10d0
/dev/dsk/c5t9d0
/dev/dsk/c5t3d0
/dev/dsk/c5t2d0
/dev/dsk/c5t12d0 /dev/rdsk/c5t12d0
disk 22 0/12/0/0.13.0 sdisk CLAIMED DEVICE FUJITSU MAJ3364MC
/dev/dsk/c5t13d0 /dev/rdsk/c5t13d0
# diskinfo /dev/rdsk/c5t11d0
diskinfo: can't open /dev/rdsk/c5t11d0: No such device or address

Any idea?

Re: vgchange -c n vgdb error

Steven E. Protter — Fri, 25 Aug 2006 06:32:56 GMT

Shalom,

A disk that was configured as part of the volume group is no longer there.

This change may have been made on the storage device itself.

The missing "disk" might also be a disk array that was mistakenly detected as a disk. If the machine has no LUN0 attached to it, the disk array itself can be detected as a disk.

I think this last speculation unlikely because a mistaken disk array whould never be configured into a volume group.

So I recommend finding out what has been done on the SAN or control device for the disk array.

SEP

Re: vgchange -c n vgdb error

James R. Ferguson — Fri, 25 Aug 2006 06:37:15 GMT

Hi:

Based upon the unresponsive 'diskinfo /dev/rdsk/c5t11d0' it would appear that you have a dead disk. Follow the appropriate procedure here:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf

Regards!

...JRF...

Re: vgchange -c n vgdb error

siva baskaran — Sat, 26 Aug 2006 10:12:40 GMT

hi,
i thing disk status is CLAIMED correct?, anyway
if it CLAIMED it should show the diskinfo

and issu the insf -e command and get it clear with diskinfo it's not show, that might be (90% problem with from storage upto server

anyway get bakcup and if would u like to do something get vgexport also to repair particular disk operation (for furthor purpose)

thanks
siva
-

Re: vgchange -c n vgdb error

Siju Vadakkan — Sun, 27 Aug 2006 06:56:32 GMT

Please provide the following details

1. ioscan -fnC disk (without u)
2. vgdisplay -v

Re: vgchange -c n vgdb error

Ionut Grigorescu_2 — Mon, 28 Aug 2006 05:58:20 GMT

Hello,

I have checked all the others vg's and pv's, the device files for c5t11d0 don't appear any more in the ioscan funC disk or ioscan -fnC disk, instead there is another disk /dev/dsk/c5t13d0 which isn't belonging to any pv. 2 months before the baseboard was swapped because of a problem with the built-in LAN but I cannot figure out how is possible that only one path is false after that (I proved that time the applications and everything was OK)anyway, what is to do now?

cheers,
Ionut

Re: vgchange -c n vgdb error

freddy_21 — Mon, 28 Aug 2006 08:16:18 GMT

hello,

try this command

# mv /etc/lvmtab /etc/lvmtab.ori
# vgscan -a
# vgchange -a y vgdb
still get that error?

Could u activate the vgdb? check with vgdisplay -v vgdb ( give me the output )

do you have same problem with another vg ( vgdb1, vgnms or vgosspkg1 )

thanks
freddy