Veritas Volume Manager 5.0.1 Troubleshooting Guide, HP-UX 11i v3, First Edition, November 2009

■ Case 1: cannot open /dev/vx/config: reason
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.”
The following are likely causes:
■ The Veritas Volume Manager package installation did not complete
correctly.
■ The device node was removed by the administrator or by an errant shell
script.
■ Case 2: 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.
Recommended action:
For Case 1, 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. If you cannot re-install the package, contact Veritas
Technical Support for more information.
For Case 2, 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.
See “VxVM and boot disk failure” on page 41.
V-5-1-249
VxVM vxconfigd NOTICE V-5-1-249 Volume volume entering degraded mode
Description:
Detaching a subdisk in the named RAID-5 volume has caused the volume to enter
“degraded” mode. While in degraded mode, performance of the RAID-5 volume
is substantially reduced. More importantly, failure of another subdisk may leave
the RAID-5 volume unusable. Also, if the RAID-5 volume does not have an active
log, then failure of the system may leave the volume unusable.
81Error messages
Types of messages