Veritas Volume Manager 5.0 Troubleshooting Guide, HP-UX 11i v3, First Edition, May 2008
70 Error messages
Understanding messages
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 “Recovering from boot disk failure” on page 35.
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.
■ Action: If hot-relocation is enabled, Veritas Volume Manager objects affected
by the disk failure are taken care of automatically. Mail is sent to root
indicating what actions were taken by VxVM and what further actions the
administrator should take.
V-5-1-480
VxVM vxconfigd ERROR V-5-1-480 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 device is open” does not normally
occur unless there is a bug in the operating system or in VxVM.