[ Previous | Next | Contents | Glossary | Home | Search ]
AIX Version 4.3 Installation Guide

Chapter 12. Acting on System and Error Messages

This chapter lists messages that can appear during the installation of AIX Version 4.3. Information about each message is organized in the following manner:

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.

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. 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".

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 install, files listed in /etc/preserve.list were copied to /tmp. 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 No prompt mode is terminated, the user is prompted.
User Action Run the mkszfile with the -m option before creating the system backup tape.

OR

Do not specify EXACT_FIT = yes in the 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/devinst.log file for errors.

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

Explanation The bosinst.data file does not specify any bootable disks.
System Action No-prompt mode is terminated, and 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 3.2, 4.1, or 4.2.

Explanation An BOS installation method of migration was specified in the bosinst.data file, but the existing volume group is at level 3.1 or 4.3.
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 migration 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 No-prompt mode was specified, and there were not enough disks specified in the bosinst.data file to hold the operating system.
System Action No-prompt 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 No-prompt mode was specified, and 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 No-prompt mode is terminated, and 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.

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 You interrupted the installation of your optional software.
System Action Sometimes, when an installation is interrupted, the system locks the root volume group.
User Action You must unlock the root volume group. Then attempt the installation procedure again.

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.

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 required indicates the number of 1024KB blocks required.
User Action Free up 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:

  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 . 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 An invalid device is specified with the bosboot -d command. 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 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.

Invalid table of contents.

Explanation The installation of the operating system from a stacked tape (a bootable tape with multiple software images) was unable to verify the validity of the tape TOC. A valid TOC has a numeric string in the following format: single_digit_number 12_digit_number single_digit_number as the first entry in the TOC. For example, 1 042309235291 1 is a valid TOC header. The TOC records the tape position installable images. Without a valid TOC, the installation process cannot locate and install installable images.
System Action The installation process returns to the System Settings menu.
User Action Recreate your tape with a valid table of contents or contact your point of sale for assistance.

The media contains an image designed for installing the base operating system.

Explanation You have chosen Install the operating system from media that was created with the `smit install_assist' or `mksysb' command . However, the media you are installing from contains a BOS image. A mksysb image is an installable backup (backup format) of a root volume group. This type of image can be created with the Backups application, the smit install_assist command, or the mksysb command. Options 1 and 2 on the second installation menu determine the installation type. Consequently, the installation media must contain the corresponding image type (mksysb or BOS).
System Action Installation cannot begin until the problem is resolved.
User Action You have several options:
  • Provide a mksysb image and continue with installation.

    OR

  • Return to the Main Installation menu, select the option to install the operating system from factory media (option 1 ), and continue with the installation.

    OR

  • Follow your local problem-reporting procedures.

The media contains an image designed for installing a mksysb image.

Explanation You have chosen Install the operating system from factory media , but the media contains an image that is an installable backup (tar format) of a root volume group. This type of image is created with the smit startup or the mksysb commands. Options 1 and 2 on the main installation menu determine the installation type. Consequently the installation media must contain the corresponding image type (mksysb or BOS).
System Action The install process has returned to the Current System Settings menu.
User Action You have several options:
  • Provide a BOS image and continue with installation.

    OR

  • Return to the Main Installation menu, select the option to install a mksysb image (option 2 ), and continue with the installation.

    OR

  • Follow your local problem reporting procedures.

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-004 mksysb: The /.fs.size file does not exist. System backup canceled.

Explanation Either the / or /tmp file system is not large enough, or the mksysb command was run from a command line without first running the mkszfile command.
System Action The mksysb command did not find the /.fs.size file.
User Action Enter the mkszfile command, then enter the mksysb command again.

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.

No disks are available.

Explanation No hard disks are configured on the system. Consequently, the only functioning menu option is the maintenance option. The devices that the configuration process was able to locate are listed in the /etc/objrepos/devs file.
System Action Installation cannot begin until the problem is resolved.
User Action You have several options:
  • View the devices file from the maintenance shell by typing the following command: 
    cat /etc/objrepos/devs
    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 tape or CD-ROM and check the hard disks.

    OR

  • Follow your local problem-reporting procedures.

No entry for bos.rte in the table of contents.

Explanation The installation of the operating system from a stacked tape (a bootable tape with multiple software images) was unable to locate an entry for a BOS image in the tape TOC. Without a BOS entry in the TOC, the installation process cannot locate and install the BOS image.
System Action The installation process returns to the Current System Settings menu.
User Action Ensure that the BOS image on the stacked tape is in the same position as listed in the table of contents. Otherwise, contact your point of sale for assistance.

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 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 which had no volume group on them.
System Action No-prompt mode is terminated, the user is prompted.
User Action If you want the system to select which disks to install on, set EXISTING_SYSTEM_OVERWRITE in the bosisnt.data file to yes.

OR

When the system prompts, select disks to install on.

0505-113 alt_disk_install: No target disk name provided.

Explanation This message is displayed in three situations:
  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.

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 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.

[ Previous | Next | Contents | Glossary | Home | Search ]