VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)

Chapter 2, Recovery from Boot Disk Failure
Correcting Boot Problems in VxVM Maintenance Mode
23
d. Create a LABEL file on the root disk and display its contents:
# mkboot -l /dev/rdsk/c4t8d0s2
# vxvmboot -v /dev/rdsk/c4t8d0s2
LIF Label File @ (1k) block # 846 on LVM Disk \
/dev/rdsk/c4t8d0s2:
Label Entry: 0, Boot Volume start: 2912; length: 3992 MB
e. Write VxVM volume information to the LABEL file and display this:
# /etc/vx/bin/vxbootsetup rootdisk01
# vxvmboot -v /dev/rdsk/c4t8d0s2
LIF Label File @ (1k) block # 846 on VxVM Disk \
/dev/rdsk/c4t8d0s2:
Label Entry: 0, Boot Volume start: 3168; length: 512 MB
Label Entry: 1, Root Volume start: 1576032; length: 256 MB
Label Entry: 2, Swap Volume start: 527456; length: 1024 MB
Label Entry: 3, Dump Volume start: 527456; length: 1024 MB
f. Reboot the system:
# reboot
Corrupt or Incorrect LABEL File
The following message may be displayed at boot time if the contents of the LABEL file
have been corrupted or are incorrect:
No root vol information found in VxVM LABEL file
◆ Description: A corrupted LABEL file or a LABEL file that contains incorrect data for a
VxVM boot disk prevents successful bootup of the system. This can occur if the
mkboot command was invoked improperly, or if the system was rebooted after
running mkboot without using the vxbootsetup command to set up the LABEL file.
◆ Action: Use the procedure described in “Missing LABEL file” on page 22 to create a
correct LABEL file.