Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 HP-UX 11i Version 1.5 Release Notes: release id B.11.20 for rx9610 and rx4610 hp servers and i2000 hp workstations > Chapter 3 HP-UX Features

Maintenance Mode Boot
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

Maintenance Mode Boot is useful on systems where a standard boot has failed due to VxVM problems. This would only occur on a system where the boot disk is made up of VxVM volumes that contain the root, stand and possibly other file systems. On such a system, you must resolve the VxVM or related problem before being able to perform a standard boot once again.

Conditions Requiring VxVM Maintenance Mode Boot

Several situations will prevent the system from being booted in a standard way. This section provides descriptions of symptoms that accompany these situations and procedures that should be used to repair the system to once again allow normal operation.

  • Missing LABEL file

    During system boot, the LABEL file is used to determine the offset and length of the root, stand, and swap/dump volumes before the VxVM configuration daemon may be started. A missing LIF LABEL file will prevent successful bootup of the system.

  • Corrupt 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 subsequent invocation of the vxbootsetup command prior to the latest system reboot.

  • Missing or corrupt /etc/vx/volboot file

    During system bootup, the VxVM configuration daemon is started. It makes use of the file /etc/vx/volboot. If for any reason that file is somehow missing or somehow corrupted, the configuration daemon will fail and abort the boot sequence.

  • Booting to VxVM Maintenance Mode

    To boot the system to VxVM Maintenance Mode Boot use the -vm option to the boot command. This boots the system to single user mode without starting the VxVM configuration daemon.

  • Missing or stale device files and missing or corrupt /stand/ioconfig file

    If the I/O hardware configuration is changed and 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 no longer map to valid or correct I/O hardware paths. On a system where this situation exists, the VxVM configuration daemon (vxconfigd) will not be able to start up properly and will prevent normal system bootup.

Maintenance Mode Boot Documentation

For more information, see the HP-UX 11i Version 1.5 Maintenance Mode Boot white paper.



Changing /dev/* permissions
  		 


System Crash Dump Changes  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2001 Hewlett-Packard Development Company, L.P.