VERITAS Volume Manager 3.1 Reference Guide

Chapter 2 47
Error Messages
Volume Manager Configuration Daemon Error Messages
It is possible that this error results from a drive that failed to spin up.
If so, rebooting may fix the problem. If that does not fix the problem,
then the only recourse is to restore the root or /usr file system or to
reinstall the system. Restoring the root or /usr file system requires
that you have a valid backup. See the “Recovery” chapter of the
Administrator’s Guide for information on how to fix problems with
root or /usr file system volumes.
Cannot start volume, volume state is invalid
vxvm:vxconfigd: ERROR: Cannot start volume volume,
volume state is invalid
• Description
The volume for the root or /usr file system is in an unexpected state
(not ACTIVE, CLEAN, SYNC or NEEDSYNC). This should not happen
unless the system administrator circumvents the mechanisms used
by the Volume Manager to create these volumes.
• Action
The only recourse is to bring up the Volume Manager on a CD-ROM
or NFS-mounted root file system and to fix the state of the volume.
See the “Recovery” chapter of the Administrator’s Guide for further
information.
Cannot store private storage into the kernel
vxvm:vxconfigd: ERROR: Cannot store private storage into
the
kernel: error
• Description
This is an internal Volume Manager error. This error should not occur
unless there is a bug in the Volume Manager.
• Action
Contact Customer Support for more information.
Differing version of vxconfigd installed
vxvm:vxconfigd: ERROR: Differing version of vxconfigd
installed
• Description