Chapter 04 System Recovery HP-UX Handbook Revision 13.
Chapter 04 System Recovery October 29, 2013 TERMS OF USE AND LEGAL RESTRICTIONS FOR THE HP-UX RECOVERY HANDBOOK ATTENTION: PLEASE READ THESE TERMS CAREFULLY BEFORE USING THE HP-UX HANDBOOK. USING THESE MATERIALS INDICATES THAT YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THESE TERMS, DO NOT USE THE HP-UX HANDBOOK. THE HP-UX HANDBOOK HAS BEEN COMPILED FROM THE NOTES OF HP ENGINEERS AND CONTAINS HP CONFIDENTIAL INFORMATION.
Chapter 04 System Recovery October 29, 2013 TABLE OF CONTENTS How an HP-UX System boots _________________________________________________________ 4 Automated Recovery Procedures _____________________________________________________ 5 Automated Procedure 1: Rebuilding bootlif and Installing Critical Files_______________________________ 6 Automated Procedure 2: Installing Critical Files only ____________________________________________11 Automated Procedure 3: Rebuilding the bootlif only __________________
Chapter 04 System Recovery October 29, 2013 This chapter deals with several kinds of HP-UX boot problems and offers different approaches how to get the system up and running again. First of all it is always useful to know the general sequence of events that occure when an HP 9000 system boots up the HP-UX operating system. ATTENTION: The boot process is different on Itanium system. Refer to the Itanium chapter. How an HP-UX System boots 1.
Chapter 04 System Recovery October 29, 2013 NOTE: Things are different on a virtual partition (vPars) system. You do not load the kernel directly but through the vPars monitor vpmon. Refer to the vPars Chapter for details. 7. The HPUX program (also known as the secondary loader or Mongoose) figures out what HP-UX kernel to load, and what arguments to pass to it (like init state). 8.
Chapter 04 System Recovery October 29, 2013 The address of the root filesystem on the disk (i.e., what file system you will be checking/repairing using fsck). The address of the bootlif path of that disk. Whether you have an LVM or non-LVM system. The more you know about the system disk and its partitioning scheme, before you encounter major damage or corruption, the easier it will be for you to recover.
Chapter 04 System Recovery October 29, 2013 3. Select a to install both the bootlif and critical files; the following menu is then displayed: DEVICE FILE VERIFICATION MENU This menu is used to specify the path of the root file system. When the information is correct, select 'a'. INFORMATION to verify: Device file used for '/'(ROOT) is c0t1d0s1lvm The path to disk is 0/0/1/0.1.0 Select one of the following: a. The above information is correct. b. WRONG!! The device file used for '/'(ROOT) is incorrect. m.
Chapter 04 System Recovery October 29, 2013 This menu must be used to verify the system's boot string. When the information is correct, select 'a'. INFORMATION to verify: The system's boot string should be: 'hpux -lm /stand/vmunix' NOTE: The Boot address is {0/0/2/0.0.0} the Root address is {0/0/1/0.1.0}. Select one of the following: a. The above information is correct. b. WRONG!! Prompt the user for the system's boot string. m. x. Return to the 'HP-UX Recovery MENU.' Exit to the shell.
Chapter 04 ** ** ** ** 63 Phase 2 - Check Phase 3 - Check Phase 4 - Check Phase 5 - Check files, 0 icont, System Recovery October 29, 2013 Pathnames Connectivity Reference Counts Cyl groups 74047 used, 54185 free (97 frags, 6761 blocks) Mounting c2t0d0s1lvm to the /ROOT directory...
Chapter 04 System Recovery ./sbin/vgreduce linked to ./sbin/lvchange ./sbin/vgremove linked to ./sbin/lvchange ./sbin/vgscan linked to ./sbin/lvchange x ./sbin/awk, 397312 bytes, 776 tape blocks x ./sbin/cat, 208896 bytes, 408 tape blocks x ./sbin/chmod, 249856 bytes, 488 tape blocks x ./sbin/chown, 258048 bytes, 504 tape blocks x ./sbin/frecover, 339968 bytes, 664 tape blocks x ./sbin/fsck symbolic link to /sbin/fs_wrapper x ./sbin/init, 299008 bytes, 584 tape blocks x .
Chapter 04 System Recovery October 29, 2013 RECOVERY COMPLETION MENU Use this menu after the recovery process has installed all requested files on your system. Select one of the following: a. REBOOT the customer's system and continue with recovery. b. Return to the HP-UX Recovery Media Main Menu. Selection: 11. Once you find yourself at the Recovery Completion menu, complete the recovery process by selecting a.
Chapter 04 System Recovery October 29, 2013 The path to disk is 0/0/1/0.1.0 Select one of the following: a. The above information is correct. b. WRONG!! The device file used for '/'(ROOT) is incorrect. m. x. Return to the 'HP-UX Recovery MENU.' Exit to the shell. NOTE: If '/' is an LVM, use an 's1lvm' suffix (e.g.,c0t1d0s1lvm). Selection: Carefully check if the patch is the correct one, enter a in this case. In doubt choose Exit to shell and verify the path using ioscan(1M).
Chapter 04 System Recovery October 29, 2013 For this reason, this part of the process is being skipped. The only operation that should be performed when the client is not installed with at least 11.00, is rebuilding the bootlif. To recover a pre 11.00 system use the diagnostic media to rebuild your system. Unfortunately, the initial 11.11 Core CD talks about 11.00 also… 7. After confirmation the system starts to download the critical files to your root VG. ***** Downloading files to disk ***** x .
Chapter 04 System Recovery /ROOT Filesystem /ROOT/stand 163840 kbytes 128232 70173 used 74047 87840 44% 2486 avail %cap iused 41361 64% 65 October 29, 2013 23414 10% ? ifree iused Mounted on 20415 0% ? 8. You need to decide if and how the current kernel in /stand should be replaced by a generic recovery kernel. Should the existing kernel be 'left', 'overwritten', or 'moved'?[overwritten] To skip the replacement, simply enter left.
Chapter 04 System Recovery October 29, 2013 These two files are also part of this document. Automated Procedure 3: Rebuilding the bootlif only 1. Boot the system to the Recovery Main Menu (see Co-Procedure). 2. From the main menu, select Recover an unbootable HP-UX system. The following menu is presented: HP-UX Recovery MENU Select one of the following: a. Rebuild the bootlif (ISL, HPUX, and the AUTO file) and install all files required to boot and recover HP-UX on the root file system. b.
Chapter 04 System Recovery October 29, 2013 BOOTLIF PATH VERIFICATION MENU This menu must be used to determine the path to the bootlif (ISL, HPUX and the AUTO file). When the information is correct, select 'a'. INFORMATION to verify: Path to the bootlif is 0/0/2/0.0.0 Select one of the following: a. The above information is correct. b. WRONG!! The path to bootlif is incorrect. m. x. Return to the 'HP-UX Recovery MENU.' Exit to the shell. Selection: 5. Confirm the path by entering a.
Chapter 04 System Recovery October 29, 2013 SWAP: lvlnboot -s /dev// Refer to the lvlnboot man page for more information. RECOVERY COMPLETION MENU Use this menu after the recovery process has installed all requested files on your system. Select one of the following: a. REBOOT the customer's system and continue with recovery. b. Return to the HP-UX Recovery Media Main Menu. Selection: 7.
Chapter 04 System Recovery October 29, 2013 The path to disk is 0/0/1/0.1.0 Select one of the following: a. The above information is correct. b. WRONG!! The device file used for '/'(ROOT) is incorrect. m. x. Return to the 'HP-UX Recovery MENU.' Exit to the shell. NOTE: If '/' is an LVM, use an 's1lvm' suffix (e.g. c0t1d0s1lvm). Selection: Carefully check if the patch is the correct one, enter a in this case. In doubt choose Exit to shell and verify the path using ioscan(1M).
Chapter 04 System Recovery October 29, 2013 files can create incompatibilities during the boot process For this reason, this part of the process is being skipped. The only operation that should be performed when the client is not installed with at least 11.00, is rebuilding the bootlif. To recover a pre 11.00 system use the diagnostic media to rebuild your system. Unfortunately the initial 11.11 Core CD talks about 11.00 also… 7.
Chapter 04 System Recovery October 29, 2013 Processor is booting from first available device. To discontinue, press any key within 10 seconds. 2. Press any key before the 10 seconds elapses. The system console will display the following or a similar prompt: Boot terminated.
Chapter 04 System Recovery October 29, 2013 executed. Booting... Boot IO Dependent Code (IODC) revision 1 HARD Booted. ISL Revision A.00.43 Apr 12, 2000 ISL> 5. At the the ISL> prompt you have many possible options to continue. For standard Multi User Mode boot: hpux For Single User Mode boot (if the root passwd is lost): hpux –is For LVM Maintenance Mode: hpux –lm To boot without LVM quorum check: hpux -lq To boot an alternate kernel: hpux /stand/vmunix.
Chapter 04 System Recovery SEArch [DIsplay|IPL] [] Search for boot devices COnfiguration menu INformation menu SERvice menu Displays or sets boot values Displays hardware information Displays service commands DIsplay HElp [
Chapter 04 System Recovery ISL booting October 29, 2013 hpux (;0):INSTALL Boot : disk(0/0/1/0.1.0.0.0.0.0;0):WINSTALL 8941568 + 1642496 + 2596176 start 0x1fef68 8. If you are booting from an Ignite/UX recovery tape you need to cancel the noninteractive installation by pressing any key when you see the following message (unless an automated install session is what you intend to do): WARNING: The configuration information calls for a non-interactive Installation.
Chapter 04 System Recovery October 29, 2013 The menus and exact procedures presented in the following sections may vary, depending on how old your CD-ROM revision is and what type of machine you actually try to recover. 2. Boot the system from CD-ROM, tape or network (see Co-Procedure). 3.
Chapter 04 System Recovery October 29, 2013 [ 0/4/0/0/7/0 lan2 0x0010837B2A11 HP_A5838A_PCI_100Base-TX/SCSI_ ] [ 0/7/0/0 0x001083FC0354 HP_A4926A_PCI_1000Base-SX_Adap ] lan3 Select the desired interface card, and press return. The system continues displaying the following messages: * Searching the network for a DHCP server to supply default networking information.... This could take up to 30 seconds if a DHCP server cannot be found.
Chapter 04 System Recovery October 29, 2013 NOTE: Commands residing in the RAM-based file system are unsupported 'mini' commands. These commands are only intended for recovery purposes. Loading minimal set of commands needed for recovery... WARNING: If ANYTHING is changed on a root(/) that is mirrored a 'maintence mode'(HPUX -lm) boot MUST be done in order to force the mirrored disk to be updated!! Press to continue. 5.
Chapter 04 System Recovery [ * ] [ ] [ ] October 29, 2013 Media only installation Media with Network enabled (allows use of SD depots) Ignite-UX server based installation User Interface Options: [ ] Guided Installation (recommended for basic installs) [ * ] Advanced Installation (recommended for disk and filesystem management) [ ] No user interface - use all the defaults and go Hint: If you need to make LVM size changes, or want to set the final networking parameters during the install, you will need t
Chapter 04 System Recovery October 29, 2013 … * Constructing the bootconf file. * Setting primary boot path to "0/0/2/0.0.0". * Starting swinstall of the source (B7994-10001 Mission Critical). Hit Ctrl-C to interrupt! WARNING: Exiting due to keyboard interrupt. WARNING: The task will continue in unattended mode on host "loopback". ERROR: Software load had one or more errors. ======= 03/30/01 09:51:55 EST The operating system software has not been successfully loaded.
Chapter 04 System Recovery October 29, 2013 # chroot /rootfs /sbin/sh # rm –rf rootfs Note: If you are using these instructions and are booting over the network from an Ignite server you must provide the full path to the SYSCMDS file applicable to the HP-UX revision you are attempting to recover. For example if you are recovering an 11i Version 1 system you must use /opt/ignite/data/Rel_B.11.11/SYSCMDS.
Chapter 04 System Recovery October 29, 2013 Co-Procedure: Mounting Volumes of an Imported Root VG If you need to access the file systems of your root VG you may check and mount them now. In our example we assume a separate HFS boot volume /stand while all other volumes are VxFS. 1. Import the root VG (see Co-Procedure). 2. Load mount and fsck commands if needed. # loadfile /sbin/fs/hfs/mount /sbin/fs/hfs/fsck # loadfile /sbin/fs/vxfs/mount /sbin/fs/vxfs/fsck 3.
Chapter 04 System Recovery October 29, 2013 # cd /ROOT # chroot /ROOT /sbin/sh Please remember that your system is currently booted using a generic recovery kernel. This kernel may be incompatible with executables that reside inside your root VG. Never try to bring the system up to Multi User Mode from this state! Even basic LVM or VxFS commands are known to make trouble under such conditions. Contents of RECOVERY.DOC and LVM.
Chapter 04 System Recovery October 29, 2013 Example: to change to use mkboot -a "hpux -lm (52.6.0;0)/stand/vmunix" "hpux (52.6.0;0)/stand/vmunix" "hpux (52.6.0;0)/stand/vmunix" /dev/rdsk/ step 2. Restore a valid copy /etc/fstab (either from backup or from the /etc/fstabBK file created during the recovery process). step 3. Restore a valid copy /etc/lvmtab, if needed. step 4. Restore a valid copy /dev, if needed. step 5. Run '/lvmrec.
Chapter 04 System Recovery October 29, 2013 step 7: Refer back to RECOVERY.DOC step 2. *** NOTE *** If the same volume group contains more than one corrupted boot disk, repeat the above steps for each disk that needs to be repaired. Manual Procedure 1: Recovery after Minimum OS Cold Installation This procedure can be used to restore a complete system upon an OS Cold Installation. It is sufficient to cold-install only the base components of the OS.
Chapter 04 System Recovery October 29, 2013 # /sbin/pax.rec –r –pe < /dev/rmt/0m e.g. for frecover(1M): # cp /sbin/frecover /sbin/frecover.rec # /sbin/frecover.rec –r -f /dev/rmt/0m -os 5. Restore /stand/rootconf and /stand/bootconf from your previously created backup files. The valid /stand/rootconf file is required for booting into LVM Maintenance Mode later! # cp –p /stand/rootconf.min /stand/rootconf # cp –p /stand/bootconf.min /stand/bootconf 6.
Chapter 04 System Recovery October 29, 2013 Manual Procedure 2: Recovery from Scratch with Root VG Creation This procedure is mainly for reference. It shows a complete recovery of a system that was booted from a recovery medium. It contains most of the configuration steps that are performed automatically during a cold installation. It is intended to help understanding these steps. 1. Boot the system to the Recovery Main Menu (see Co-Procedure). 2. From the main menu select Exit to shell. 3.
Chapter 04 System Recovery October 29, 2013 Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf # lvcreate -L 1536 vg00 # /opt Logical volume "/dev/vg00/lvol4" has been successfully created with character device "/dev/vg00/rlvol4". Logical volume "/dev/vg00/lvol4" has been successfully extended. Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.
Chapter 04 System Recovery October 29, 2013 needs to be an HFS file system! lvol2 will be the primary swap, so no file system is created there.
Chapter 04 System Recovery October 29, 2013 outside the root VG are part of the backup. Either those file systems are also mounted or excluded from restore! Especially the root file system could get overflowed otherwise. If VGs are imported at this point we need to take care that all names used for them and their logical volumes are absolutely identical with the ones contained in the backup! We need to ensure that all LVM device files in /dev are unique after restore. 10.
Chapter 04 System Recovery October 29, 2013 Please remember to take a backup using the vgcfgbackup command after activating the volume group. # vgchange -a y /dev/vg00 Activated volume group Volume group "vg00" has been successfully changed. 15. Perform a fresh vgcfgbackup(1M) of your root VG. # vgcfgbackup /dev/vg00 Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf 16. Reboot the system to Multi User Mode (see Co-Procedure).
Chapter 04 System Recovery October 29, 2013 hpux ALTKERNEL where ALTKERNEL is the kernel name that you want to boot. The standard backup kernel name is /stand/vmunix.
Chapter 04 System Recovery October 29, 2013 Booting from primary path, press any key to override 800 Series except T-Class, VClass, Nova: Boot from an alternate disk 800 Series Nova: Boot from an alternate disk At the menu, type: boot PATH where PATH is the physical path of the disk you want to boot off of Answer "y" to: interact with ISL ?(if asked) Example: boot 52.5.
Chapter 04 System Recovery Boot from primary path and interact with isl Answer "y" to Interact with IPL ? Enter boot command At the ISL prompt type: hpux -lm October 29, 2013 Series 800 (except T-Class/V-Class): Single User Mode Boot Step Action Interrupt the boot process Hit any key when the following message appears: Booting from primary path, press any key to override 800 Series except T-Class, VClass, Nova: Boot from primary path and interact with isl 800 Series Nova: Boot from primary path a
Chapter 04 System Recovery October 29, 2013 boot PATH where PATH is your alternate disk path Example: boot 10/52.5.0 V-Class: Alternate Kernel Boot Step Action Interrupt the boot process Hit any key when the f ollowing message appears: Booting from primary path, press any key to o verride Boot from primary path and select an alternate kernel in o ne easy step. At the menu, type: boot pri ALTKERNEL where ALTKERNEL is the kernel name that you want to boot.
Chapter 04 System Recovery October 29, 2013 T-Class: Alternate Disk Boot Step Action Interrupt the boot process Hit any key when the following message appears: Booting from primary path, press any key to override NOTE: On a T-Class box, there will be initial question about interrupting the boot process to change the configuration prior to the above message.
Chapter 04 System Recovery October 29, 2013 T-Class: Single User Mode Boot Step Action Hit any key when the following message appears: Booting from primary path, press any key to override Interrupt the boot process NOTE: On a T-Class box, there will be initial question about interrupting the boot process to change the configuration prior to the above message.
Chapter 04 System Recovery October 29, 2013 Booting to VxVM MMB prevents the VxVM configuration daemon (vxconfigd) from being started during system initialization. When booted to VxVM MMB, the system will be in single user mode with only the root volume mounted. Several conditions will prevent the system from being booted in a normal way. This section provides symptoms that accompany such conditions and procedures that may be used to repair the system to once again allow normal operation.
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.
Chapter 04 System Recovery October 29, 2013 subsequent invocation of the vxbootsetup command prior to the latest system reboot. NOTE: Running the mkboot command alone will result in a LABEL not suitable for booting a system with a VxVM boot disk. To create a LABEL file suitable for a VxVM boot disk, one must run the vxbootsetup command after having run the 'mkboot -l ' (see example under Missing LABEL file section above) .
Chapter 04 System Recovery October 29, 2013 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. Symptoms of missing or corrupt /etc/vx/volboot file Welcome to HP-UX for IA64 setting hpux path(\EFI\HPUX)... type 'fs[x]:' where x is your bootdisk (0, 1, 2...
Chapter 04 System Recovery October 29, 2013 sync'ing disks (0 buffers to flush): 0 buffers not flushed 0 buffers still dirty System has halted OK to turn off power or reset system Restoring the volboot file Boot the system to VxVM maintenance mode. fs1:\> hpux -vm VxVM maintenance mode *** HP-UX Boot Loader for IA-64 **** *** Version 1.
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 ...
Chapter 04 System Recovery October 29, 2013 *** HP-UX Boot Loader for IA-64 **** *** Version 1.65 **** *** Type 'help' for help **** Press Any Key to interrupt Autoboot \efi\hpux\AUTO ==> boot vmunix Seconds left till autoboot - 0 AUTOBOOTING... AUTO BOOT> boot vmunix System Memory = 4091 MB loading section 0 ................................. loading section 1 ..... Loading symbol table. Num of Sec Header(29) Loading System Directory(boot.sys) to MFS ..... Loading Kernel Boot Directory(boot.
Chapter 04 System Recovery October 29, 2013 Press Any Key to interrupt Autoboot \efi\hpux\AUTO ==> boot vmunix Seconds left till autoboot - 10 HPUX> boot vmunix -vm > System Memory = 4091 MB loading section 0 loading section 1 .....
Chapter 04 System Recovery October 29, 2013 Additional Information Recovery Media Users Guide http://docs.hp.com/hpux/hw/index.html#General%20Guides Refer to the vPars Chapter to learn how a virtual partition is booted. Refer to the Itanium Chapter to learn how an Itanium system is booted. HP-UX Handbook – Rev 13.
