Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008

69Error messages
Understanding messages
V-5-1-135
VxVM vxconfigd FATAL ERROR V-5-1-135 Memory allocation failure
during startup
■ Description: This implies that there is insufficient memory to start up
VxVM.
■ Action: This error should not normally occur, unless your system has very
small amounts of memory. Adding swap space probably will not help,
because this error is most likely to occur early in the boot sequence, before
swap areas have been added.
V-5-1-148
VxVM vxconfigd ERROR V-5-1-148 System startup failed
■ Description: 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.
V-5-1-169
VxVM vxconfigd ERROR V-5-1-169 cannot open /dev/vx/config: reason
■ Description: The /dev/vx/config device could not be opened. vxconfigd
uses this device to communicate with the Veritas Volume Manager kernel
drivers. The most likely reason is “Device is already open.” This indicates
that some process (most likely vxconfigd) already has /dev/vx/config
open. Less likely reasons are “No such file or directory” or “No such device
or address.” For either of these reasons, likely causes are:
■ The Veritas Volume Manager package installation did not complete
correctly.
■ The device node was removed by the administrator or by an errant
shell script.
■ Action: If the reason is “Device is already open,” stop or kill the old
vxconfigd by running the command:
# vxdctl -k stop
For other failure reasons, consider re-adding the base Veritas Volume
Manager package. This will reconfigure the device node and re-install the
Veritas Volume Manager kernel device drivers. See the Veritas Volume
Manager 3.5 for HP-UX Release Notes for information on how to add the