HP-UX HB v13.00 Ch-04 - System Recovery

HP-UX Handbook Rev 13.00 Page 47 (of 54)
Chapter 04 System Recovery
October 29, 2013
Starting vxconfigd in boot mode (pre_init_rc).
INFO: VxVM Maintenance Mode Boot - vxconfigd aborted
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: njl selectors: CUPI80_BL2001_0223 xxx_xxx 'CU$
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4190020 Kbytes, lockable: 2968036 Kbytes, available: 3122284 Kbyts
/sbin/ioinitrc:
vxfs fsck: Cannot open /dev/vx/dsk/rootdg/standvol: No such device or address
file system check failure, aborting ...
/dev/vx/dsk/rootdg/standvol: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted
INFO: VxVM Maintenance Mode Boot - vxconfigd aborted
INIT: Overriding default level with level 's'
INIT: SINGLE USER MODE
Value of TERM has been set to "vt100".
WARNING: YOU ARE SUPERUSER !!
At the prompt run the vxconfigd:
# vxconfigd
NOTICE: vxvm:vxdmp: added disk array OTHER_DISKS
Mount the file systems:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c4t8d0s2 simple rootdisk01 rootdg online
# vxvol startall
# mountall
Write the LABEL file:
# 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
# /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
Reboot the system.
Corrupted or Incorrect LABEL File
A corrupted LABEL file or a LABEL file containing incorrect data for a VxVM boot
disk will prevent successful boot up of the system. An incorrect LABEL file can occur,
for example, if the mkboot command has been invoked improperly or without a