Veritas Volume Manager 4.1 Troubleshooting Guide (HP-UX 11i v3, February 2007)

Understanding Messages
66 VERITAS Volume Manager Troubleshooting Guide
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 package. If you cannot re-add the
package, contact VERITAS Technical Support for more information.
VxVM vxconfigd ERROR V-5-1-169 Cannot open /etc/fstab: reason
◆ Description: vxconfigd could not open the /etc/fstab file, for the reason given.
The /etc/fstab file is used to determine which volume (if any) to use for the /usr
file system.
◆ Action: This error implies that your root file system is currently unusable. You may
be able to repair the root file system by mounting it after booting from a network or
CD-ROM root file system. If the root file system is defined on a volume, then see
the procedures defined for recovering from a failed root file system in “Recovery
from Boot Disk Failure” on page 31.