Topics:
Operating System Boot Processes
Troubleshooting the Boot Process
Recovering the Boot Disk Group
Files Used in the Boot Process
* /etc/system (Sun only)
Contains VxVM entries
* /etc/vfstab (Sun), /etc/fstab (HP-UX and Linux)
Maps mount points to devices
* /etc/vx/volboot
Contains disk ownership data
* /etc/vx/licenses/lic, /etc/vx/elm
Contains license files
* /var/vxvm/tempdb
Stores data about diskgroups
* /etc/vx/reconfig.d/state.d/install-db
Indicates VxVM is not initialized
* /VXVM#.#.#-UPGRADE/.start_runed
Indicates that the VxVM upgrade is not complete
Troubleshooting: The Boot Device Cannot be Opened
Possible causes:
* Boot disk is not powered on
* Boot disk has failed
* SCSI bus is not terminated
* Controller failure has occurred
* Disk is failing and locking the bus
To resolve:
* Check SCSI bus connections:
- On Sun, use probe-scsi-all
- On Linux, use non-fast or verbose boot in the BIOS
* Boot from an alternate boot disk
Troubleshooting: Startup Scripts Exit Without Initialization
Possible causes:
Either one of the following files is present:
* /etc/vx/reconfig.d/state.d/install-db
This file indicates that VxVM software packages have been added, but VxVM has not been initialized with vxinstall. Therefore, vxconfigd is not started.
* / VXVM#.#.#-UPGRADE/.start_runed
This file indicates that a VxVM upgrade has been started but not completed. Therefore, vxconfigd is not started.
Troubleshooting: Conflicting Host ID in volboot
The volboot file contains the host ID that was on the system when you installed VxVM.
If you manually edit this file, VxVM does not function.
* To change the hostname in the volboot file:
vxdctl hosted newhostname
* To re-create the volboot file:
vxdctl init [hostname]
Troubleshooting: License Problems (keys corrupted, missing, or expired)
Save /etc/vx/licenses/lic/* to a backup device. If the license files are removed or corrupted, you can copy the files back.
License problems can occur if:
* The /etc/vx/licenses/lic files become corrupted
* An evaluation license was installed and not updated to a full license.
To resolve license issues:
* vxlicinst (installs a new license)
* vxiod set 10 (starts the I/O daemons)
* vxconfigd (starts the configuration daemon)
Troubleshooting: Missing /var/vxvm/tempdb (missing, misnamed, or corrupted)
This directory stores configuration information about imported diskgroups. The contents are recreated after a reboot. If this directory is missing, misnamed, or corrupted, vxconfigd does not start.
To remove and recreate this directory:
# vxconfigd –k –x cleartempdir
Troubleshooting: Debugging with vxconfigd
Running vxconfigd in debug mode:
# vxconfigd –k –m enable –x debug_level
* debug_level = 0 – No debugging (default)
* debug_level = 9 – Highest debug level
Some debugging options:
* -x log
Logs all console output to the /var/vxvm/vxconfigd.log file
* -x logfile=name
Use the specified log file instead
* -x syslog
Direct all console output through the syslog() interface
* -x timestamp
Attach a timestamp to all messages
* -x tracefile=name
Log all possible tracing information in the given file.
Troubleshooting: Invalid or Missing /etc/system File (Sun only)
The /etc/system file is used in the kernel initialization and /sbin/init phases of the boot process.
This file is a standard Sun system file to which VxVM add entries to:
* Specify drivers to be loaded
* Specify root encapsulation
If the file or these entries are missing, you encounter problems in the boot process.
When booting from an alternate system file, do not go past the maint mode. Boot up on the alternate system file, fix the VxVM problem, and then reboot with the original system file.
ok> boot –a
When prompted specify the /etc/hosts file for the system file. You will get many errors but you’ll get far enough in order to fix the original system file.
Temporarily Importing the Boot Diskgroup
Through a temporary import, you can bring the boot diskgroup to a working system and repair it there:
1) Obtain the diskgroup ID (dgid) of the boot diskgroup:
# vxdisk –s list
2) On the importing host, import and temporarily rename the diskgroup:
# vxdg –tC –n tmpdg import dgid
3) Fix and replace the files and volumes as necessary.
4) Deport the diskgroup back to the original host:
# vxdg –h orig_hostname deport tmpdg
Custom Search
