VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages
vxconfigd Error Messages
Chapter 3
70
• Action: Reboot the system. If that does not cure the problem, re-add the VxVM
packages.
vxvm:vxconfigd:ERROR: volume_name :vxconfigd cannot boot-start RAID-5
volumes
• Description: A volume that vxconfigd should start immediately upon booting the
system (that is, the volume for the /usr file system) has a RAID-5 layout. The /usr
file system should never be defined on a RAID-5 volume.
• Action: It is likely that the only recovery for this is to boot VxVM from a
network-mounted root file system (or from a CD-ROM), and reconfigure the /usr file
system to be defined on a regular non-RAID-5 volume.
vxvm:vxconfigd: ERROR: Volume volume for mount point /usr not found in
rootdg disk group
• Description: The system is configured to boot with /usr mounted on a volume, but
the volume associated with /usr is not listed in the configuration of the rootdg disk
group. There are two possible causes of this error:
— 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 rootdg disk
group. This should happen only as a result of direct manipulation by the
administrator.
— Case 2: The system somehow has a duplicate rootdg 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 rootdg. Since
vxconfigd chooses the more recently accessed version of rootdg, 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 renamed to rootdg 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 rootdg turned off, or
import and rename (see vxdg (1M)) the offending rootdg disk group from another
host. If you turn off drives, run the following command after booting:
# vxdg flush rootdg
This updates time stamps on the imported version of rootdg, which should make the
correct version appear to be the more recently accessed. If this does not correct the
problem, contact Customer Support.