Chapter 12. Acting on System and Error Messages

• Select fewer filesets than the number originally selected for installation.

  OR

• Extend the root volume group to another disk. Enter: extendvg rootvg hdiskNumber, where Number is the number of the specified disk.

  OR

• Remove user-defined file systems to free up space in the rootvg file system.

  OR

• Follow the instructions in Troubleshooting a Full /usr File System.

OR

Do not specify EXACT_FIT = yes in the image.data file.

If you've gotten this error then your partition size is less than 8 megabytes, and you need to increase the number of partitions in hd5 (boot logical volume). You can check your partition size by with the command:

# lsvg rootvg

Look for the field: PP SIZE:

You can get the current number of partitions in hd5 with the command:

# lslv hd5

Look for the field: LPs:

Your boot logical volume must contain enough partitions such that:

PP SIZE multiplied by LPs is greater than or equal to 8.

The partitions for the boot logical volume must be contiguous.

If there were free partitions available next to hd5 or at some other location on the disk that contains hd5, the install process would have increased the size of hd5, and continued.

To view the current allocation map (free and used partitions) of a disk, use the command:

# lspv -M diskname

If there are not enough contiguous free partitions, then you will need to increase the size of the boot logical volume (hd5) using one of the options described below, and rerun the installation. The options for increasing the boot logical volume size are as follows:

• If a user-created logical volume or file system follows hd5 on the disk (check the allocation map), and has free partitions, then you could back up, remove, recreate and restore the logical volume.

• If there is another disk in the rootvg, that has enough contiguous free partitions, then you could move hd5 to the other disk with the following steps:

  1. Verify that the disk you plan to move hd5 to is bootable by using the command:

     bosinfo -B diskname

     If 1 is returned, the disk is bootable.

     If 0 is returned, the disk is not bootable.

  2. Find the free contiguous partitions you need on the other disk by viewing the allocation map with the command:

     lspv -M diskname

  3. Create a map file to use when recreating hd5. For example, if you want to recreate hd5 on hdisk2, on partitions 88 and 89, use the command:

     echo "hdisk2:88-89" > your_MAP_file

  4. Remove the existing hd5:

     rmlv -f hd5

  5. Create the new hd5:

     mklv -y hd5 -t boot -m your_MAP_file rootvg 2

     2 is the number of partitions and may vary as needed.

  6. Run mkboot to clear the boot record from the disk that previously contained hd5 (boot logical volume). For example, if hd5 was previously on hdisk0, use the command:

     mkboot -d /dev/hdisk0 -c

  7. Use bosboot, to recreate the boot image and boot record on the new disk. For example, if hd5 was recreated on hdisk2, use the command:

     bosboot -a -d /dev/hdisk2

  8. Change the bootlist of your system, to boot from the new disk. To see the current bootlist, use the command:

     bootlist -m normal -o

     If your previous hd5 was on hdisk0, the output might be:

     hdisk0

     To change the bootlist to use hdisk2 use the command:

     bootlist -m normal hdisk2

     If there were additional items in your bootlist, add them after hdisk2, with spaces separating each item.

  9. Reboot your system if there were no errors.

• If you encountered this error when installing a mksysb on a system other than the system it was created on (cloning), then you may be able to use a customized image.data file to increase the size of hd5.

  The vg_data stanza contains the size of the physical partitions in the PPSIZE field. Use this information to determine how many partitions are needed for hd5. The lv_data stanza for hd5 contains the fields for the number of logical partitions (LPs) and the minimum number of logical partitions required for the logical volume (LV_MIN_LPS). These fields need to be set to the number of partitions needed.

  Refer to the section titled Create and Use a Supplementary Diskette for information on putting an image.data file on diskette as well as a bosinst.data file.

  If the source machine had no free partitions, and the target machine has the same disk size, then you may need to install using the shrink option, as well as the customized image.data file.

OR

Add a bootable disk to the bosinst.data file target_disk_data stanzas.

OR

Add more target_disk_data stanzas to bosinst.data file.

OR

Specify disks in the bosinst.data file that define a root volume group.

To unlock a root volume group:

1. Be sure you have logged in as root.
2. Enter chvg -u rootvg
3. Enter smit_install and attempt to install your optional software products again.

To resize the /tmp file system and complete the installation:

1. Note the error message preceding this one. Either the message bosboot verification starting or bosboot process starting will precede this message.
2. Change directories to /tmp. List the files and determine which can be deleted. If there is sufficient space available, go to step 6. If you need to expand /tmp, continue this procedure.
3. Enter smit chfs
4. Select the/tmp file system from the displayed list.
5. Add the additional block space required. The smit chfs command requires disk space to be defined in 512KB blocks. Double the required disk space displayed in the system message.
6. If the message installp: An error occurred during bosboot processing was displayed after the message bosboot verification starting, rerun the installation procedure.

   OR

   If the message installp: An error occurred during bosboot processing was displayed after the message bosboot process starting, enter installp -C.

7. Continue the installation process.

To identify the boot device and complete the installation:

1. To identify the boot disk, enter lslv -m hd5. The boot disk name is displayed.
2. Create a link between the boot device indicated and the /dev/ipldevice file. Enter: ln /dev/boot_device_name /dev/ipldevice. (An example of boot_device_name is rhdisk0.)

   OR

3. If the message installp: An error occurred during bosboot processing was displayed after the message bosboot verification starting, rerun the installation procedure.

   OR

   If the message installp: An error occurred during bosboot processing was displayed after the message bosboot process starting, enter installp -C. Continue the installation process.

• Select Maintenance (option 3) from the Welcome to Base Operating System Install Menu, and select the Limited Function Maintenance Shell. Verify that no disks were configured by entering the following command:

  lsdev -Cc disk

  To determine if there were configuration errors, enter the command:

  cfgmgr -v 2>1 | tee /tmp/cfgmgr.out

  You can use the cat command to view /tmp/cfgmgr.out, and look specifically for errors in configuration of disks. The file can be copied to diskette media using either the dd or pax commands, and moved to a running system for ease of viewing.

  OR

• Turn the system off and check the following on systems with SCSI devices:
  • Check all SCSI devices to ensure that all SCSI addresses are unique.
  • Make sure the SCSI cards are properly terminated.
  • If external SCSI devices are in use, make sure that the SCSI chain is terminated and that the devices are turned on.
  • Check the SCSI cabling and connections.
  • Reboot and attempt the install again.

  OR

• Turn the system off and check the following on systems with IDE devices:
  • Check all IDE devices to ensure that all IDE master and slave settings are unique per controller. If only one IDE device is connected to a controller, it must be set to master. If an ATA device (disk) and an ATAPI device (CD-ROM or tape) are connected to the same controller, the ATA device must be set to the master device and the ATAPI device must be set as the slave device.
  • Check the IDE cabling and connections.
  • Reboot and attempt the install again.

  OR

• Boot from the diagnostics and check the hard disks.

  OR

• Follow your local problem-reporting procedures.

OR

When the system prompts, select disks to install on.

OR

When the system prompts, select disks to install on.

1. You did not enter a target disk.
2. The disk that was specified as the target disk has a volume group already associated with it. Running lspv should show the word None by disks that do not have a volume group associated with them. This is what alt_disk_install checks.
3. The target disk (or disks) specified are not bootable. alt_disk_install runs bootinfo -B disk_name on each disk specified in the target disk list. If any one bootinfo -B command returns a 0, then the disk is not bootable, and it cannot be used as a target disk for alt_disk_install.

The alt_disk_install command first checks the second image on the tape for a ./tapeblksz file, which contains the block size that the mksysb image was created in. The mksysb command creates this file and puts it in the second image on the tape. The first three images of a mksysb tape are always created at a 512byte block size. The mksysb image (the fourth image on the tape) can be created at another block size.

If the alt_disk_install command cannot restore the ./tapeblksz file from the second image, then the block size will remain what it was when the alt_disk_install command was started. It will attempt to restore the ./image.data file from the mksysb image. If this block size does not match the block size that the mksysb image was created in, then the restore fails, and the alt_disk_install produces this error.