or is not configured into the kernel.
vgchange: Couldn't activate volume group "/dev/vg01":
Either no physical volumes are attached or no valid VGDAs were found on
the physical volumes.
If a nonroot volume group does not activate because of a failure to meet quorum, follow these
steps:
1.
Check the power and data connections (including Fibre Channel zoning and security) of all
the disks that are part of the volume group that you cannot activate. Return all disks (or at
least enough to make a quorum) to service. Then use the
vgchange
command to activate the
volume group again.
2.
If there is no other way to make a quorum available, use the
-q
option with the
vgchange
command to override the quorum requirement.
# vgchange -a y -q n /dev/vg01
The volume group activates without a quorum. You might get messages about not being able
to access certain logical volumes because part or all of a logical volume might be located on
one of the disks that is not present.
Whenever you override a quorum requirement, you run the risk of using data that is not current.
Be sure to check the data on the logical volumes in the activated volume group and the size
and locations of the logical volumes to ensure that they are up to date.
Return the disabled disks to the volume group as soon as possible. When you return a disk
to service that was not online when you originally activated the volume group, use the
vgchange
command as follows:
# vgchange -a y /dev/vg01
Quorum Problems with a Root Volume Group
Your root volume group can also report a quorum problem. If not enough disks are present in the
root volume group to constitute a quorum, a message indicating that not enough physical volumes
are present appears during the boot sequence. This error might occur if you have physically
removed a disk from your system because you no longer intended to use it, but did not remove
the physical volume from the volume group using
vgreduce
. Do not remove an LVM disk from a
system without first removing it from its volume group. However, you can try to recover by booting
the system with the quorum override option
-lq
.
On an HP 9000 server, enter the following command:
ISL> hpux -lq
On an HP Integrity server, enter the following command:
HPUX> boot -lq
Version 2.x Volume Group Activation Failures
Version 2.x volume groups can fail to activate because of insufficient quorum. For example,
vgchange
could display error messages similar to the following:
# vgchange -a y /dev/vgtest
vgchange: Warning: Couldn't attach to the volume group physical
volume "/dev/disk/disk1":
I/O error
vgchange: I/O error
vgchange: Couldn't activate volume group "/dev/vgtest":
Quorum not present, or some physical volume(s) are missing.
If a Version 2.x volume group does not activate because of a failure to meet quorum, follow the
steps described in
“Quorum Problems with a Nonroot Volume Group” (page 111)
.
A Version 2.x volume group can also fail activation if the necessary commands or kernel drivers
are not present. For example,
vgchange
could display the following error message:
112
Troubleshooting LVM
