VERITAS Volume Manager 4.1 Troubleshooting Guide

Recovery from Boot Disk Failure
Recovery by Booting from Recovery Media
Chapter 3
49
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE ...
v rootvol root DISABLED 393216 - ACTIVE ...
pl rootvol-01 rootvol DISABLED 393216 - STALE ...
sd rootdisk01-02 rootvol-01 ENABLED 393216 0 -...
pl rootvol-02 rootvol DISABLED 393216 - STALE ...
sd rootdisk02-02 rootvol-02 ENABLED 393216 0 - ...
When this happens, the root volume can usually be repaired by using the following
command:
# vxvol -g rootdg -f start rootvol
If the root volume is mirrored, recovery is started. Wait until recovery completes and the
command exits. Then run the fsck command and mount the root file system as shown
here:
# fsck -F vxfs -o full /dev/vx/rdsk/rootdg/rootvol
# mkdir /tmp_mnt
# mount -F vxfs /dev/vx/dsk/rootdg/rootvol /tmp_mnt
The following form of the vx_emerg_start command combines all these operations in a
single command to recover the root volume and its mirrors, check the root file system,
and mount it:
# vx_emerg_start -m hostname
When you have recovered the volumes on the VxVM root disk, and performed any other
necessary repairs, reboot the system:
# reboot
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: Rootdg cannot be imported during boot
Error returned from vxconfigd -m boot, halting
• Description: 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.
• Action: Reboot 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.