VERITAS Volume Manager 3.1 Reference Guide

58 Chapter2
Error Messages
Volume Manager Configuration Daemon Error Messages
Either the root or the /usr file system volume could not be started,
rendering the system unusable. The error that resulted in this
condition should appear prior to this error message.
• Action
Look up other error messages appearing on the console and take the
actions suggested in the descriptions of those messages.
There is no volume configured for the root device
vxvm:vxconfigd: ERROR: There is no volume configured for
the
root device
• Description
The system is configured to boot from a root file system defined on a
volume, but there is no root volume listed in the configuration of the
rootdg disk group.
There are two possible causes of this error:
• Case 1: The /etc/system file was erroneously updated to
indicate that the root device is /pseudo/vxio@0:0. 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 a root file system volume and one of which
does not, and vxconfigd somehow chose the wrong one. 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, directly mount the disk partition of the root file system,
and remove the following lines from /etc/system:
rootdev:/pseudo/vxio@0:0
set vxio:vol_rootdev_is_volume=1