VERITAS Volume Manager 3.5 Troubleshooting Guide (August 2002)
Chapter 2, Recovery from Boot Disk Failure
Correcting Boot Problems in VxVM Maintenance Mode
25
Missing or Corrupt ioconfig or Device Files
The following messages may be displayed at boot time if the /stand/ioconfig file is
missing, its contents have been corrupted, or it does not correctly describe the devices in
the system:
ioconfig_lock: Cannot open /etc/ioconfig with specified flags.
Error returned from vxconfigd -m boot, halting
◆ Description: The ioconfig file provides the mapping between information stored as
device file metadata (major number and logical unit) and the information that the I/O
system uses to communicate with devices via hardware paths. If the I/O hardware
configuration is changed and the ioconfig file is subsequently removed or becomes
corrupted,some or all devicefiles may notmap to validI/O hardwarepaths. If device
files are either missing or stale, the configuration daemon may fail and abort the boot
sequence. The /stand/ioconfig file that is used at boot time can be recreated from
/etc/ioconfig if this is regenerated so that it contains the correct device mapping
entries.
◆ Action: The following example shows the sequence of commands that should be used
to recreate the ioconfig and device files:
a. Enter the following command at the boot prompt to put the system into VxVM
maintenance mode:
hpux -vm
b. List the mounted file systems:
# mount
/ on /dev/vx/dsk/rootdg/rootvol log on Wed Apr 17 14:15:29 2002
c. Remove all block and raw disk device files under /dev/dsk and /dev/rdsk,
and verify that they have been removed:
# rm /dev/dsk/* /dev/rdsk/*
# ls /dev/rdsk /dev/dsk
/dev/dsk:
/dev/rdsk: