VERITAS Volume Manager 3.1 Reference Guide

46 Chapter2
Error Messages
Volume Manager Configuration Daemon Error Messages
VxVM tracing device open. Also, if any volumes are mounted as file
systems, unmount those file systems.
An error reason other than “A virtual disk device is open”
should not normally occur unless there is a bug in the operating
system or in the Volume Manager.
Cannot start volume, no valid complete plexes
vxvm:vxconfigd: ERROR: Cannot start volume volume,
no valid complete plexes
• Description
This error indicates that the volume for either the root or /usr file
system cannot be started because the volume contains no valid
plexes. This can happen, for example, if disk failures have caused all
plexes to be unusable. It can also happen as a result of Actions that
caused all plexes to become unusable (for example, forcing the
dissociation of subdisks or detaching, dissociation, or offlining of
plexes).
• Action
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, no valid plexes
vxvm:vxconfigd: ERROR: Cannot start volume volume,
no valid plexes
• Description
This error indicates that the volume for either the root or /usr file
system cannot be started because the volume contains no valid
plexes. This can happen, for example, if disk failures have caused all
plexes to be unusable. It can also happen as a result of Actions that
caused all plexes to become unusable (for example, forcing the
dissociation of subdisks or detaching, dissociating, or offlining plexes).
• Action