VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Chapter 3, Error Messages
vxconfigd Error Messages
57
vxvm:vxconfigd: ERROR: Unexpected configuration tid for group group
found in kernel
vxvm:vxconfigd: ERROR: Unexpected error during volume volume
reconfiguration: reason
vxvm:vxconfigd: ERROR: Unexpected error fetching disk for disk volume:
reason
vxvm:vxconfigd: ERROR: Unexpected values stored in the kernel
◆ Description: These internal errors should not occur unless there is a bug in VxVM.
◆ Action: Contact Customer Support.
vxvm:vxconfigd: ERROR: Version number of kernel does not match
vxconfigd
◆ Description: The release of vxconfigd does not match the release of the VERITAS
Volume Manager kernel drivers. This should happen only as a result of upgrading
VxVM, and then running vxconfigd without a reboot.
◆ 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), andreconfigurethe /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 systemis avolume, but thevolume namedis notin 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