HP-UX System Administrator's Guide: Logical Volume Management (5900-3028, March 2013)

# vgchange -a y /dev/vgtest
vgchange: Error: The "lvmp" driver is not loaded.
Here is another possible error message:
# vgchange -a y /dev/vgtest
vgchange: Warning: Couldn't attach to the volume group physical
volume "/dev/disk/disk1":
Illegal byte sequence
vgchange: Couldn't activate volume group "/dev/vgtest":
Quorum not present, or some physical volume(s) are missing.
A third possible error message is the following:
# vgchange -a y /dev/vgtest
vgchange: Warning: Couldn't attach to the volume group
physical volume "/dev/dsk/c1t0d0":
Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c1t0d0":
The specified path does not correspond to physical volume
attached to this volume group
vgchange: Couldn't query the list of physical volumes.
vgchange: Couldn't activate volume group "/dev/vgtest":
Quorum not present, or some physical volume(s) are missing.
To troubleshoot these activation failures, run the lvmadm command as follows:
# lvmadm -t -V 2.0
If the necessary commands and drivers are present, lvmadm displays the following:
--- LVM Limits ---
VG Version 2.0
Max VG Size (Tbytes) 2048
Max LV Size (Tbytes) 256
Max PV Size (Tbytes) 16
Max VGs 512
Max LVs 511
Max PVs 511
Max Mirrors 6
Max Stripes 511
Max Stripe Size (Kbytes) 262144
Max LXs per LV 33554432
Max PXs per PV 16777216
Max Extent Size (Mbytes) 256
If lvmadm displays no output, your operating system release does not support Version 2.x volumes.
You must update your system to the March 2008 release of HP-UX 11i Version 3 or a newer
release.
If the kernel driver to support Version 2.x volume groups is not loaded, lvmadm displays the
following error:
# lvmadm -t -V 2.0
lvmadm: Error: The "lvmp" driver is not loaded.
Load the lvmp module using the kcmodule command as follows:
# kcmodule lvmp=best
==> Update the automatic 'backup' configuration first? n
* Future operations will ask whether to update the backup.
* The requested changes have been applied to the currently
running configuration.
Module State Cause Notes
lvmp (before) unused loadable, unloadable
(now) loaded best
(next boot) loaded explicit
You do not need to reboot. After you load the lvmp module, lvmadm succeeds:
# lvmadm -t -V 2.0
--- LVM Limits ---
VG Version 2.0
116 Troubleshooting LVM