Veritas Volume Manager 5.0.1 Troubleshooting Guide, HP-UX 11i v3, First Edition, November 2009

disk group. This should happen only as a result of direct manipulation by the
administrator.
■ Case 2: The system somehow has a duplicate boot disk group, one of which
contains the /usr file system volume and one of which does not (or uses a
different volume name), and vxconfigd somehow chose the wrong boot disk
group. Since vxconfigd chooses the more recently accessed version of the
boot disk group, this error can happen if the system clock was updated
incorrectly at some point (causing the apparent access order of the two disk
groups to be reversed). This can also happen if some disk group was deported
and assigned the same name as the boot disk group with locks given to this
host.
Recommended action:
The following are recommended actions for each case:
■ Case 1: Boot the system on a CD-ROM or networking-mounted root file system.
If the root file system is defined on a volume, then start and mount the root
volume. If the root file system is not defined on a volume, mount the root file
system directly. Edit the /etc/fstab file to correct the entry for the /usr file
system.
■ Case 2: Either boot with all drives in the offending version of the boot disk
group turned off, or import and rename the offending boot disk group from
another host.
See the vxdg(1M) manual page.
If you turn off drives, run the following command after booting:
# vxdg flush bootdg
This updates time stamps on the imported version of the boot disk group,
bootdg, which should make the correct version appear to be the more recently
accessed. If this does not correct the problem, contact Veritas Technical
Support.
V-5-1-1589
VxVM vxconfigd ERROR V-5-1-1589 enable failed: aborting
VxVM vxconfigd ERROR V-5-1-1589 enable failed: Error check group
configuration copies. Database file not found
VxVM vxconfigd ERROR V-5-1-1589 enable failed: transactions are
disabled
Description:
95Error messages
Types of messages