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

Fixing a missing or corrupt /etc/vx/volboot file
The following messages may be displayed at boot time if the /etc/vx/volboot
file is missing or its contents are incorrect:
vxvm:vxconfigd: ERROR: enable failed: Volboot file not loaded
transactions are disabled.
vxvm:vxconfigd: FATAL ERROR: Bootdg cannot be imported during
boot
Error returned from vxconfigd -m boot, halting
During system bootup, the VxVM configuration daemon reads the file
/etc/vx/volboot. If that file is missing or corrupted, the configuration daemon
fails and aborts the boot sequence.
To fix a missing or corrupt /etc/vx/volboot file
◆
Reboot the system from recovery media, and run the following command:
# vx_emerg_start -m hostname
This determines if the volboot file is present, and rewrites it if it is not
present.
Initiating VxVM Maintenance Mode Boot
Another method for performing limited recovery on a VxVM boot disk is to use
the VxVM Maintenance Mode Boot (MMB).
45Recovering from boot disk failure
Initiating VxVM Maintenance Mode Boot