Ignite-UX Frequently Asked Questions

===============================================================================
4.3
Q: How do I deal with hot-swappable disk devices during recovery?
A: Ignite-UX only supports hot-swappable disks that are completely
installed and present when creating a recovery image. Proper
software and hardware procedures must be used for hot swap disk
removal or replacement before or after recovery, but not during. The
LVM command lvlnboot used by save_config does not work when a disk is
removed and the system is in this transitional state. If this
command is not working, then recovery has no chance of succeeding.
Please also refer to the discussion regarding SAS disks in the
Ignite-UX release notes for Version C.6.8.
===============================================================================
4.4
Q: What is the maximum amount of data that a make_tape_recovery tape
can hold?
A: A make_tape_recovery tape can hold as much data as will fit on the
tape. If make_tape_recovery is run in the foreground it prompts for
more tapes if they are necessary.
Note that to include files larger than 2GB but less than 8GB you may
need to install patches. On HP-UX 11.11 you must have PHCO_28414 or
later installed. On HP-UX B.11.23 you should have PHCO_31634 or
later installed. Otherwise files will be limited to being less than
4GB in size.
===============================================================================
4.5
Q: How do I boot correctly from a recovery tape on a V-class system?
A: When booting from a recovery tape on a V-class system using an
incorrect boot string, it is possible that the following errors are
generated:
Command: bo 4/2/0.1.0 VINSTALL
Device : 4/2/0.1.0
File : hpux
Arguments : hpux VINSTALL
Loading : hpux.....175984bytes Loaded
110448 + 65536 + 865264 start 0xd01c88
Boot
:tape(4/2/0.1.0;0)VINSTALL
tape(4/2/0.1.0;0)VINSTALL:cannot open, or executable
Exec failed : No such file or directory
The correct method for booting any kernel from a tape is to add a
colon (:) to the start of the kernel name. The colon tells the
bootloader that it must read the kernel from the LIF at the start of
the media. Without the colon, the bootloader attempts other methods
to read the kernel, but it does not attempt to install it from a LIF.
The above errors are the result of the bootloader attempting to read
the kernel from an HFS file system, which on a tape is not possible.
Older releases of the bootloader prepended a colon (:) to the
VINSTALL kernel name. The bootloader for 11i v1 does not allow for
this behavior. In this case, the correct boot string would be:
bo 4/2/0.1.0 :VINSTALL
Not:
bo 4/2/0.1.0 VINSTALL
For machines other than the V-class, always use :INSTALL to represent
the installation kernel when manually booting from tape or an
installation CD. The bootloader automatically changes it to
:WINSTALL on systems that require a 64-bit kernel for installation.
===============================================================================
4.6
Q: How do I include all volume/disk groups into a recovery tape?
A: To include all volume and disk groups on the system into a recovery
tape (can be used with make_net_recovery as well) use the following
command:
# make tape recovery -A -x inc cross=/