VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

vxconfigd Error Messages
48 VERITAS Volume Manager Troubleshooting Guide
- 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 Customer Support for more information.
vxvm:vxconfigd: ERROR: 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 19.
vxvm:vxconfigd: ERROR: Cannot recover operation in progress
Failed to get group group from the kernel: error
◆ Description: This internal error should not occur unless there is a bug in VxVM.
◆ Action: Contact Customer Support.
vxvm:vxconfigd: ERROR: Cannot reset VxVM kernel: reason
◆ Description: The-r reset option was specified to vxconfigd,but the VxVM kernel
drivers could not be reset. The most common reason is “A virtual disk device is
open.” This implies that a VxVM tracing or volume device is open.
◆ Action: If you want to reset the kernel devices, track down and kill all processes that
have a volume or VERITAS Volume Manager tracing device open. Also, if any
volumes are mounted as file systems, unmount those file systems.
Any reason other than“A virtual disk deviceis open” does not normally occur unless
there is a bug in the operating system or in VxVM.
vxvm:vxconfigd: ERROR: Cannot start volume volume, no valid plexes
vxvm:vxconfigd: ERROR: Cannot start volume volume, no valid complete
plexes