topic Re: Error on command vgdisplay -v vg00. in Operating System - HP-UX

Error on command vgdisplay -v vg00.

Dimitri di Paolo — Fri, 20 Feb 2004 08:42:48 GMT

Hi,
I have changed the boot disk (vg00) whith new egual disk and I recovered data from a make_recovery.
The system is 9000/800 L1000 HP-UX 11.00 and now it seem works well but when I running the "vgdisplay -v vg00" command I receive the follow message:
#vgdisplay -v vg00
vgdisplay: Couldn't query volume group "vg00".
Possible error in the Volume Group minor number; Please check and make sure the group minor number is unique.
vgdisplay: Cannot display volume group "vg00".
I receive the same message on the "lvnboot -v" command.
What does it means ?

Thanks

Re: Error on command vgdisplay -v vg00.

Pete Randall — Fri, 20 Feb 2004 08:48:32 GMT

Two thoughts/guesses:

First, /etc/lvmtab is out of sync, move it aside (mv /etc/lvmtab /etc/lvmtab.old) and rebuild it (vgscan -av).

Second, you have some sort of conflict with the minor numbers in your LVM VGs. Check with "ll /dev/vg*/group" to make sure that the minor numbers (0xNN0000, where NN is the minor number) for each VG are unique.

Pete

Re: Error on command vgdisplay -v vg00.

T G Manikandan — Fri, 20 Feb 2004 08:57:36 GMT

#ll /dev/vg*/group

check the minor number is unique

Re: Error on command vgdisplay -v vg00.

T G Manikandan — Fri, 20 Feb 2004 09:02:10 GMT

Also,

was serviceguard was previously installed.

check whether the file is present
#ll /dev/slvmvg
If present,
#mv /dev/slvmvg /tmp
#mv /etc/lvmtab /etc/lvmtab.old
#vgscan -a
#vgdisplay -v /dev/vg00

Re: Error on command vgdisplay -v vg00.

Dimitri di Paolo — Fri, 20 Feb 2004 09:06:18 GMT

I renamed vfstab.
I ran "vgscan -v" (only -v option) and now when I run "vgdisplay -v vg00" and lvlnboot commandit it is ok.
Wath is different -a and -a -v options ?
I needed to run "vgchange -a y" and "lvlnboot -R" to resync information on disk ?

Thanks

Re: Error on command vgdisplay -v vg00.

Pete Randall — Fri, 20 Feb 2004 09:10:34 GMT

The -a option scans "all controller device paths for all disks". I usually include it just to be thorough but I don't really think it's necessary. Running vgchange or lvlnboot would only apply if your root disk was mirrored. I think what happened in your case is that the lvmtab you restored had the physical ID of the damaged disk in it. Re-creating the lvmtab recorded the physical ID of the new disk, thus eliminating your problem.

Pete