VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Recovery from Boot Disk Failure
Recovery by Booting from Recovery Media
Chapter 2
33
...
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 loadedtransactions
are disabled.vxvm:vxconfigd: FATAL ERROR: Rootdg cannot be imported during
boot