1.
The disk was missing when the volume group was activated, but was later restored. This
typically occurs when a system is rebooted or the volume group is activated with a disk missing,
uncabled, or powered down.
2.
The disk LVM header was overwritten with the wrong volume group information. If the disk is
shared between two systems, one system might not be aware that the disk was already in a
volume group. To confirm, check the volume group information using the
dump_lvmtab
command (available from your HP support representative) and look for inconsistencies. For
example:
# dump_lvmtab -s | more
SYSTEM : 0x35c8cf58
TIME : 0x3f9acc69 : Sat Oct 25 15:18:01 2003
FILE : /etc/lvmtab
HEADER : version:0x03e8 vgnum:7
VG[00] VGID:35c8cf58 3dd13164 (@0x00040c) pvnum:2 state:0 /dev/vg00
(00) VGID:35c8cf58 3dd13164 PVID:35c8cf58 3dd13164 /dev/dsk/c0t6d0
(01) VGID:35c8cf58 3dd13164 PVID:35c8cf58 3dda4694 /dev/dsk/c4t6d0
VG[01] VGID:065f303f 3e63f01a (@0x001032) pvnum:92 state:0 /dev/vg01
(00) !VGID:35c8cf58 3f8df316 PVID:065f303f 3e63effa /dev/dsk/c40t0d0
(01) !VGID:35c8cf58 3f8df316 PVID:065f303f 3e63effe /dev/dsk/c40t0d4
(02) !VGID:35c8cf58 3f8df316 PVID:065f303f 3e63f003 /dev/dsk/c40t1d0
...
In this example, the VGIDs for the disks in
/dev/vg01
are not consistent; inconsistencies are
marked
!VGID
.
Recommended Action
1.
Use
ioscan
and
diskinfo
to confirm that the disk is functioning properly. Reactivate the
volume group using the following command:
# vgchange –a y vgname
2.
There are several methods of recovery from this error. If you are not familiar with the commands
outlined in the following procedures, contact your HP support representative for assistance.
a.
Restore a known good configuration to the disks using
vgcfgrestore
. Be sure to use
a valid copy dated before the first occurrence of the problem. For example:
# vgcfgrestore –n vgname pvname
b.
Recreate the volume group and its logical volumes, restoring the data from the most current
backup. See
“Creating a Volume Group” (page 44)
and
“Creating a Logical Volume”
(page 52)
.
c.
Export and reimport the volume group, as described in
“Exporting a Volume Group”
(page 57)
and
“Importing a Volume Group” (page 58)
. For example:
# vgexport -m vgname.map -v -f vgname.file /dev/vgname
# vgimport -m vgname.map -v -f vgname.file /dev/vgname
Message Text
vgchange: Couldn't set the unique id for volume group "/dev/vgname"
Cause
There are multiple LVM group files with the same minor number.
Recommended Action
List the LVM group files. If there are any duplicate minor numbers, export one of the affected volume
groups, optionally create a new group file with a unique minor number, and reimport the volume
group. If you are not familiar with this procedure, contact your HP support representative for
assistance.
# ll /dev/*/group
# vgexport -m vgname.map -v -f vgname.file /dev/vgname
168 Warning and Error Messages