This section describes solutions for common problems when installing from a system image created with the mksysb command.
The section discusses the following topics:
If a backup tape fails to boot, you can still install by using a mksysb image stored on the tape.
Boot the machine from the product media (Volume 1 if there is more than one volume), then install the backup from Maintenance mode. Refer to Chapter 1, Installing the Base Operating System for instructions on booting. Follow the instructions to the point when the Welcome to the Base Operating System Installation and Maintenance screen displays.
Complete the following steps when the Welcome screen is displayed:
The system reads the tape and begins the installation.
The system installs the kernel and device support required on the target system from the CD.
Note: The Use Maps option is not supported in Maintenance Mode. 9 includes a description of the use of maps on disks selected in the System Backup Installation and Settings screen.
Complete the following steps when the Welcome screen is displayed:
The Maintenance screen displays.
The Choose Tape Drive screen displays.
The system reads the tape and begins the installation.
Note: The system prompts you to remove the mksysb tape and insert the product tape after the mksysb backup has been restored.
Note: The Use Maps option is not supported in Maintenance Mode. 9 includes a description of the use of maps on disks selected in the System Backup Installation and Settings screen.
Bootable mksysb tapes are made up of four images: the boot image, the BOS Install/Maintenance image, the toc image and the system backup image. The system backup image is the actual backup of the files in the rootvg in all JFS-mounted file systems.
The first three images must be created with a tape block_size value of 512. The mksysb command ensures that the block size is 512 when these images are created. There are no restrictions on the block size used for the fourth (system backup image) on the tape. The block size of the system, before it was temporarily set to 512, is used for the fourth image on the tape.
The value of the block size must be saved in the /tapeblksz file in the second image on the tape. The second and fourth images are stored in backup/restore format. Again, mksysb ensures the correctness of the tapes created using the mksysb command.
If there are problems with the bosinst.data file, the image.data file, or the tapeblksz file, they can be restored from the second image on the tape and checked. These files, as well as commands necessary for execution in the RAM filesystem (when running in maintenance mode after booting from the tape), are stored in the second image.
To restore a file from the second image follow these steps:
# lsattr -E -l rmt0
If the block size is not correct, use the following command to set it to 512:
# chdev -l rmt0 -a block_size=512
# tctl -f /dev/rmt0 rewind
# restore -xvq -s2 -f /dev/rmt0.1 .filename
Note: The filename should be the full path, and always preceded with a . (dot character), such as ./tapeblksz.
# tctl -f /dev/rmt0 rewind
Consider the differences in the source and target systems when planning an installation from a mksysb backup.
The original system image made with the mksysb command might not match your present configuration. For example, if you changed devices after backing up your system, the original source image does not have the correct device drivers for the target system. Avoid system inequalities such as different communication adapters, TTY attributes, and printer attributes. If you are using the Common Desktop Environment (CDE) on the target system, make all configuration changes, then shut down and reboot the system before you start CDE.
When using a backup image to install additional systems, follow the procedure for Cloning Your System.
The following troubleshooting tips apply to reported problems with installations from a mksysb image: