VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Starting VxVM after Booting from Recovery Media
20 VERITAS Volume Manager Troubleshooting Guide
If there is a failure to boot from the VxVM boot disk on HP-UX 11i, and no bootable root
mirror is available, use one of the following methods to recover. The method you choose
depends on the type of failure:
◆ If the kernel is corrupted or the files required for booting are missing, boot the system
from the recovery media and use the vx_emerg_start utility to start VxVM as
described in “Starting VxVM after Booting from Recovery Media” on page 20.
◆ Use the VxVM maintenance mode boot as described in “Correcting Boot Problems in
VxVM Maintenance Mode” if any of the following files are missing or corrupted:
- LABEL
- /etc/vx/volboot
- /stand/ioconfig
- device files
If these methods fail, use the procedures described in “Recovery by Reinstallation” on
page 27.
Starting VxVM after Booting from Recovery Media
You can use the vx_emerg_start utility to start VxVM after booting a system from
recovery media. This command allows a rootable VxVM configuration to be repaired in
the event of a catastrophic failure. The command is invoked as shown here:
# vx_emerg_start hostname
The hostname argument specifies the name (node name) of the system that you are
repairing. This name must match the name of the system that you are repairing, as it is
unlikely to be recorded on the recovery media from which you booted the system.
Recovering the Root Volume After VxVM Emergency Startup
After you have used vx_emerg_start to start VxVM, use the vxprint command to
determine the configuration state.
One common problem is for all the plexes of the root volume, rootvol, to be stale. This
would be shown in the STATE field of the vxprint output as follows:
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 - ...