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

HP-UX Handbook – Rev 13.00 Page 51 (of 54)
Chapter 04 System Recovery
October 29, 2013
/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
INIT: Running /sbin/sh
…
Value of TERM has been set to "vt100".
WARNING: YOU ARE SUPERUSER !!
Start the vxconfigd:
# vxconfigd -m disable
NOTICE: vxvm:vxdmp: added disk array SEAGATE_DISKS
# vxdctl init <hostname>
# vxdctl add disk c3t1d0s2 privoffset=2144
# vxconfigd -kr reset -m boot
Confirm that VxVM is running
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c3t0d0s2 simple - - FS wholedisk
c3t1d0s2 simple rootdisk01 rootdg online
c4t8d0s2 simple - - online
Now reboot the system.
Missing or Corrupt Device Files or Missing or Corrupt ioconfig File
The ioconfig file provides the mapping between information stored in devices files (major
number and logical unit) and the information the I/O system uses to communicate with the
devices via hardware paths. VxVM only interacts directly with device files.
If the I/O hardware configuration is changed and, at any time later, the ioconfig file is removed
or corrupted, the mapping between the I/O system and device files will be changed. As a result,
some or all device files may not map to valid I/O hardware paths. If these device files are either
missing or stale, the VxVM configuration daemon (vxconfigd) will not start. This in turn will
abort the system boot sequence.
Symptoms of missing or corrupt /stand/ioconfig file
Welcome to HP-UX for IA64
setting hpux path(\EFI\HPUX)...
type 'fs[x]:' where x is your bootdisk (0, 1, 2...)
type 'hpux' to start hpux bootloader
Shell> fs1:
fs1:\> hpux