Veritas Volume Manager 4.1 Troubleshooting Guide (HP-UX 11i v3, February 2007)

Understanding Messages
78 VERITAS Volume Manager Troubleshooting Guide
◆ Case 1: The /etc/fstab file was erroneously updated to indicate the device for
the /usr file system is a volume, but the volume named is not in the boot 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.
◆ Action: In 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.
In case 2, either boot with all drives in the offending version of the boot disk group
turned off, or import and rename (see vxdg(1M)) the offending boot disk group from
another host. 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
◆ Description: Regular startup of vxconfigd failed. This error can also result from the
command vxdctl enable.
◆ Action: The failure was fatal and vxconfigd was forced to exit. The most likely cause
is that the operating system is unable to create interprocess communication channels
to other utilities.
VxVM vxconfigd ERROR V-5-1-1589 enable failed: Error check group
configuration copies. Database file not found
◆ Description: Regular startup of vxconfigd failed. This error can also result from the
command vxdctl enable.
The directory /var/vxvm/tempdb is inaccessible. This may be because of root file
system corruption, if the root file system is full, or if /var is a separate file system,
because it has become corrupted or has not been mounted.