HP-UX 11i v3 - LVM Volume Group Version Migration (September 2010)

18
Error: The Physical Volume "/dev/disk/disk348" has bad blocks relocated on it.
Version 2.x volume groups cannot handle bad blocks on physical volumes. If any physical volumes
of a Version 1.0 volume group have relocated bad blocks, vgversion fails the migration. You
cannot migrate the volume group to 2.x.
Error: The Physical Volume "/dev/disk/disk348 " has the pvkey 512, which is not
supported by volume group Version 2.0
The pvkey of a physical volume of a Version 2.x volume group is more than 510, even though the
total number of physical volumes in the volumes group is less than 511; vgversion failed the
migration.
Error: The Physical Volume "/dev/disk/disk348" is a boot disk.
A Version 2.x volume group cannot be a bootable volume group. If any of the physical volumes of
a Version 1.0 volume group are marked as bootable, vgversion fails the migration. To continue
the migration, you must convert all bootable physical volumes to nonbootable by using the
vgmodify –B n command.
Note: After the migration, you cannot use the volume group as bootable volume group.
Error: The Physical Volume "/dev/disk/disk348" is a cluster lock disk.
The vgversion command cannot continue with the migration because one of the physical volumes
belonging to the volume group is a cluster lock disk for a high availability HP Serviceguard cluster.
To continue with the migration, modify the cluster configuration so the physical volume is not a
cluster lock disk.
Error: The Physical Volume "/dev/disk/disk348" is configured as a spare.
Version 2.x volume groups do not support spare physical volumes. If any physical volume of a
Version 1.0 volume group is marked as a spare physical volume, vgversion fails the migration.
To continue with the migration, you must convert all spare physical volumes to regular physical
volumes.
New Volume Group configuration for "/dev/vg01" has been saved in
"/etc/lvmconf/vgversion_vg01/vg01_2.1.conf"
While migrating a volume group to the specified volume group version, vgversion created the
configuration backup file of the volume group corresponding to the new volume group version.
Old Volume Group configuration for "/dev/vg01" has been saved in
"/etc/lvmconf/vgversion_vg01/vg01_1.0.conf"
The vgversion command stored the configuration backup file corresponding to the initial
configuration of the volume group. You can use this file to undo the volume group migration
operation, if the volume group does not under go any configuration changes after the migration.
Performing "vgchange -a y -l -p -s vg01" to collect data
When vgversion runs, it internally activates the volume group to ensure that all physical volumes
are present and all logical volume opens are blocked. Stale extents are not resynchronized during
this activation.