[ Bottom of Page | Previous Page | Next Page | Contents | Index | Library Home | Legal | Search ]

Installation Guide and Reference

Acting on System and Error Messages

This section lists messages that can appear during the installation of AIX 5.1 and later. Information about most messages is provided in the following format:

System Message The system message is displayed in bold type.
Explanation Describes what is likely to have caused the system message to be displayed.
System Action Describes what the system does after the message is displayed.
User Action Suggests a possible resolution to the problem suggested by the system message.

Note: Multiple messages can have the same explanation, system action, and user action.

0516-404 allocp: Not enough resources available to fulfill allocation. Either not enough free partitions or not enough physical volumes to keep strictness. Try again with different allocation characteristics.


0516-788: extendlv: Unable to extend logical volume


0503-008 installp: There is not enough free disk space in file system /usr (506935 more 512-byte blocks are required.) An attempt to extend this file system was unsuccessful. Make more space available, then retry this operation.

Explanation There is not enough space to complete the installation.
System Action The installation cannot begin until the problem is resolved.
User Action You have several options:
  • Select fewer filesets than the number originally selected for installation.

    OR

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

    OR

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

    OR

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

BOS Install: After saving all the data from the previous system into /tmp, it was discovered that there will not be enough free space in /tmp to make the boot image. Please reboot in normal mode and increase the size of /tmp or reduce the number of files to save as listed in the /etc/preserve.list file.

Explanation During a preservation installation, files listed in the/etc/preserve.list file were copied to the /tmp file. After doing so, there was not enough room in /tmp to create the boot image.
System Action Installation cannot continue.
User Action Reboot in normal mode and increase the size of /tmp or reduce the number of files to be saved.

BOS Install: You chose to create logical volumes mapped exactly as they were on the previous disks, but there are no map files specified in the image.data file.

Explanation On system backup restore, EXACT_FIT = yes was specified in the image.data file, but no map files were specified in the image.data file.
System Action Nonprompted mode is terminated. The user is prompted.
User Action Run the mkszfile command with the -m option before creating the system backup tape.

OR

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

The boot logical volume (hd5) must be at least 12 MB. The system you are installing has a boot logical volume smaller than this, and the system does not have enough free contiguous physical partitions on diskname to increase the size of the boot logical volume. Please reboot in normal mode and correct this problem, or restart the installation and choose an overwrite install. Use the lspv -M diskname command to see the current allocation map of the disk.

OR

Error: No space available to create a larger boot logical volume. In order to proceed with this installation the size of the boot logical volume (hd5) must be increased to 12 MB. At this time there are not N contiguous physical partitions available on the boot disk (diskname) for recreating the larger boot logical volume. You must free up this space by removing or relocating one or more logical volumes or file systems from diskname. Use lspv -M diskname to see its current partition allocation map.

Explanation Starting with AIX 5.2 the boot logical volume (blv), logical volume hd5, must be greater than 12 megabytes. If your system had disks less than 4 gigabytes in size in the root volume group, or was originally installed with a version of AIX earlier than AIX 4.3.2 your boot logical volume may only be 4 megabytes. You might experience this failure during preservation or migration installations. Overwrite installations create the boot logical volume with a minimum size of 12 megabytes. If free partitions contiguous to hd5 are available or if another location on the disk contains hd5 is identified, the installation process increases the size of hd5 and continues. Only the disk that currently contains the boot logical volume is checked for additional partitions in order to increase the size of the boot logical volume. Other disks in the rootvg are not checked.
System Action You will be prompted to reboot in normal mode from the existing rootvg and increase the boot logical volume, or restart the installation and choose an overwrite install.
User Action Only a system administrator with root authority should attempt to increase the boot logical volume. To increase the boot logical volume, follow the process described below:

If you received 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 with the command:

# lsvg rootvg
  • Look for the field: PP SIZE:

    You can obtain the current number of partitions in hd5 with the following 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 installation 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
User Action, continued

If there are not enough contiguous free partitions, you must 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, you can back up, remove, re-create, 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 re-creating hd5. For example, if you want to re-create 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

      The 2 represents the number of partitions and can vary as needed.

      Note: If the mklv command moves hd5 to a new location, you must run the following command: 

      echo ":C:C:C" | /usr/lpp/bosinst/blvset -d /dev/hdiskN

      Where C is the message, locale, and keyboard (respectively) and hdiskN is the disk that contains hd5.

    6. Run the mkboot command 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 the bosboot command to re-create the boot image and boot record on the new disk. For example, if hd5 was re-created on hdisk2, use the command: 

      bosboot -a -d /dev/hdisk2
User Action, continued
  1. Change the bootlist of your system to boot from the new disk. To see the current bootlist, use the command: 

    bootlist -m normal -o

    OR

    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.

  2. Reboot your system if there were no errors.
  3. If you encountered this error when installing a mksysb on a system other than the system it was created on (cloning), then you might 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), the number of physical partitions (PP), and the minimum number of logical partitions required for the logical volume (LV_MIN_LPS). These fields must be set to the number of partitions needed.

    See 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 might need to install using the shrink option, as well as the customized image.data file.

BOS Install: Could not create boot image.

Explanation The bosboot command failed.
System Action The boot image was not created.
User Action Check the /var/adm/ras/bosinst.log file for errors (alog -o -f bosinst.log | pg). This log is updated by appending, so make sure you check the last entry.

The bosinst.data file does not specify any bootable disks.

Explanation The bosinst.data file does not specify any bootable disks.
System Action Nonprompted mode is terminated. The user is prompted.
User Action When the system prompts, select bootable disks to install on.

OR

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

The bosinst.data file specified doing a migration install, but there is no existing root volume group of level 4.2, 4.3, or 5.1.

Explanation A BOS installation method of migration was specified in the bosinst.data file, but the existing volume group is at level 3.1 or 5.2.
System Action This error only occurs during a nonprompted BOS installation. The installation menus are displayed.
User Action Respond to the menu prompts to complete the installation.

The bosinst.data file specified doing either a migration or a preservation install, but there is no existing root volume group.

Explanation A BOS installation method of migrate or preserve was specified in the bosinst.data file, but no root volume group was found.
System Action This error only occurs during a nonprompted BOS installation. The installation menus are displayed.
User Action Respond to the menu prompts to complete the installation.

The data file did not specify enough disk space to contain the operating system.

Explanation Nonprompted mode was specified, and there were not enough disks specified in the bosinst.data file to hold the operating system.
System Action Nonprompted mode is terminated. The user is prompted.
User Action When the system prompts, select disks to install on.

OR

Add more target_disk_data stanzas to bosinst.data file.

Duplicate lv_data stanzas specified in the image.data file. The installation cannot continue because data may be lost.

Explanation An lv_data stanza was duplicated in the image.data file.
System Action Installation cannot continue.
User Action Correct the problem and try the installation again.

Duplicate fs_data stanzas specified in the image.data file. The installation cannot continue because data may be lost.

Explanation An fs_data stanza was duplicated in the image.data file.
System Action Installation cannot continue.
User Action Correct the problem and try the installation again.

The following disks failed the preliminary diagnostic tests: <disk name>


bosset: No hard disks can be accessed.

Explanation The listed disks failed pretest.
System Action The system initiated a diagnostic pretest on the specified disk.
User Action Run full diagnostics on the specified disks.

Disks specified in bosinst.data do not define a root volume group.

Explanation Nonprompted mode was specified. The install method was set to preserve or migrate, and the disks specified in bosinst.data do not define a root volume group.
System Action Nonprompted mode is terminated. The user is prompted.
User Action When the system prompts, select a root volume group to install on.

OR

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

Encountered an unrecoverable error.

Explanation The menus subsystem encountered an unrecoverable error.
System Action The menu is restarted.
User Action None

The image.data file contains no vg_data stanza for rootvg. The installation cannot continue.

Explanation The image.data file is incomplete.
System Action Installation cannot continue.
User Action Use the default image.data file supplied with product media.

image.data has invalid logical volume data. Cannot continue.

Explanation The system could not parse the logical volume data stanzas in the image.data file.
System Action Installation cannot continue.
User Action Use the default image.data file supplied with product media.

image.data has invalid file system data. Cannot continue.

Explanation The system detected invalid file system data stanzas in the image.data file.
System Action Installation cannot continue.
User Action Use the default image.data file supplied with product media.

0516-366 putlvodm: Volume group rootvg is locked. Try again.


0516-788: extendlv: Unable to extend logical volume.

Explanation You interrupted the installation of your optional software.
System Action When an installation is interrupted, the system sometimes locks the root volume group.
User Action Unlock the root volume group. Then attempt the installation procedure again.

To unlock a root volume group:

  1. Log in with root authority.
  2. Type chvg -u rootvg
  3. Type smit_install and attempt to install your optional software products again.

installp: An error occurred during bosboot processing.

Please correct the problem and rerun.

0301-52 bosboot: not enough file space to create: /tmp/disk.image.

OR

0301-152 bosboot: not enough file space to create: /tmp/unix.

Explanation The bosboot command was unable to finish processing because of insufficient space in /tmp.
System Action The bosboot process is interrupted. The error message, the amount of disk space required, and the available disk space are displayed. The disk space displayed indicates the number of 1024 KB blocks required.
User Action Release space in the /tmp file system or extend the /tmp file system. Continue or restart the installation process.

To resize the /tmp file system and complete the installation, do the following:

  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 files can be deleted. If there is sufficient space available, go to step 6. If you need to expand /tmp, continue with this procedure.
  3. Type 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.

installp: An error occurred during bosboot processing.

Please correct the problem and rerun.

301-155 bosboot: Invalid or no boot device specified.

Explanation A device specified with the bosboot -d command is not valid. The bosboot command was unable to finish processing because it could not locate the required boot device. The installp command calls the bosboot command with /dev/ipldevice. If this error does occur, it is probably because /dev/ipldevice does not exist. /dev/ipldevice is a link to the boot disk.
System Action The bosboot process is interrupted.
User Action Determine if the link to the boot device is missing or incorrect, correct the error and complete 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 displays.
  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.)

  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.

Missing image.data file. The tape does not contain a valid install image.

Explanation The system could not find an image.data file.
System Action Installation cannot continue.
User Action The most likely cause of this error is the tape is bad. Try a different tape.

0512-0016 mksysb: Attempt to create a bootable tape failed: bosboot -d /dev/device -a failed with return code xxx.

OR

0512-0016 mksysb: Attempt to create a bootable tape failed: mkinsttape /dev/device failed with return code xxx.

Explanation The xxx return code indicates the error:
5 OR 1
Not enough space in one or more of three file systems:
  • / must have at least 500 1KB blocks.
  • /tmp must have at least 7400 1KB blocks.
  • /usr must have at least 4000 1KB blocks.
11
Defective tape.
42 OR 45
Either the /usr/lib/boot/unix file is corrupted (may be 0 length) or the link to /unix is missing.
48
Cannot write to the tape drive or cannot read /dev/blv. This is probably caused by an incorrect density setting for the tape drive. It could also be caused by either a hardware problem with the tape drive or by dirty heads on the drive.
System Action The mksysb command failed to make a bootable tape.
User Action The return code xxx indicates the action required:
5 OR 1
Check the /, /tmp, and /usr file systems and create more space as required.
11
Replace the defective tape.
42 OR 45
Either restore the /usr/lib/boot/unix file from the original tape or create the missing link.
48
Check the tape drive settings and clean the heads.

There are no disks available on this system.

Explanation No hard disks are configured on the system. Consequently, the only functioning menu option is the maintenance option.
System Action Installation cannot begin until the problem is resolved.
User Action You have several options:
  • 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 off the system 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 installation again.

    OR

  • Turn off the system 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 installation again.

    OR

  • Boot from the diagnostics and check the hard disks.

    OR

  • Follow your local problem-reporting procedures.

There are no disks on this system which can be booted.

Explanation The system could not find any bootable disks on the system.
System Action Installation cannot continue.
User Action Some third-party disks are not bootable. If a disk should be bootable but is not, run diagnostics.

You chose to install only onto disks in the existing root volume group and those not in any volume group. There are not enough of those disks to contain the mksysb image.

Explanation The EXISTING_SYSTEM_OVERWRITE field in bosinst.data was set to yes, and prompt was set to no, and there were not enough disks on the system that contained the root volume group or contained no volume group.
System Action Nonprompted mode is terminated. The user is prompted.
User Action Use target_disk_data stanzas to specify the disks to install on, set SHRINK to yes in the image.data file, or at the BOS Install prompt set the EXISTING_SYSTEM_OVERWRITE in the bosinst.data file to any. This allows any disks to be used for the install.

Attention: If EXISTING_SYSTEM_OVERWRITE is set to any, user volume groups might be overwritten.

OR

When the system prompts, select disks on which to install or select to shrink the file systems.

You chose to install only onto disks which are not contained in a volume group, but there are not enough of those disks to contain the mksysb image.

Explanation The EXISTING_SYSTEM_OVERWRITE field in bosinst.data was set to no, and prompt was set to no, and there were not enough disks on the system that contained a volume group.
System Action Nonprompted mode is terminated. The user is prompted.
User Action If you want the system to select the disk to install on, use the target_disk_data stanzas to specify the target disks and set the appropriate setting for EXISTING_SYSTEM_OVERWRITE, leave EXISTING_SYSTEM_OVERWRITE blank in the bosinst.data file , or set SHRINK to yes in the image.data file and retry the installation.

OR

When the system prompts, select disks on which to install.

0505-113 alt_disk_install: No target disk name provided.

Explanation This message is displayed in these situations:
  • You did not enter a target disk.
  • The disk that was specified as the target disk has a volume group already associated with it. Running the lspv command should show the word None by disks that do not have a volume group associated with them, which is what the alt_disk_install command checks.
  • 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.

0505-117 alt_disk_install: Error restoring image.data file from mksysb image.

Explanation This message is displayed when you are trying to install a mksysb image from tape.

The alt_disk_install command first checks the second image on the tape for a ./tapeblksz file, which contains the block size in which the mksysb image was created. 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 in which the mksysb image was created, then the restore fails, and the alt_disk_install produces this error.

[ Top of Page | Previous Page | Next Page | Contents | Index | Library Home | Legal | Search ]