IBM_PROLOG IBM_PROLOG_BEGIN_TAG IBM_PROLOG This is an automatically generated prolog. IBM_PROLOG IBM_PROLOG bos720 src/bos/usr/sbin/mkcd/README.S 1.4.1.6 IBM_PROLOG IBM_PROLOG Licensed Materials - Property of IBM IBM_PROLOG IBM_PROLOG Restricted Materials of IBM IBM_PROLOG IBM_PROLOG COPYRIGHT International Business Machines Corp. 2003,2008 IBM_PROLOG All Rights Reserved IBM_PROLOG IBM_PROLOG US Government Users Restricted Rights - Use, duplication or IBM_PROLOG disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM_PROLOG IBM_PROLOG IBM_PROLOG_END_TAG * Installing from a tape backup whose boot image is too large * Use -a flag to create backups compatible with earlier AIX levels * Backing up DMAPI filesystems * 0512-064 Installing from a tape backup whose boot image is too large As more and more devices become supported on AIX, the boot image continues to grow in size until it reaches a pre-existing limit at which point it is not possible to boot directly from the tape media containing an over-the-limit boot image. To determine your system type, run the following command: # bootinfo -a A 3 means CHRP. SYMPTOM: The symptoms of this problem are that the system might appear to hang with the message: "Software starting... Please wait" At this point the system continues trying to boot from this device without success. Codes that might be displayed on the LCD are 20EE000B, 20EE000A or E14D. Also, text displayed on the system console containing the words "default catch". Or, it may boot off the next bootable device in the bootlist. SOLUTIONS: Note: Solutions 2, 3 and 4 may require that you create a new backup. 1). Boot off of media that has a smaller boot image and is at the same level as the backup. (For example, the AIX product media, or network boot image.) Then, select "3 Access Advanced Maintenance Functions", select "4 Install from a System Backup", select tape drive and install. If you do not have AIX product media at the same level, see "CREATING BOOTABLE CD MEDIA" below. Note: If install media is not at equal to or higher maintenance level than the level of the backup image being installed, unpredictable results might occur. 2). Remove filesets from the system that would result in a smaller boot image and then create a new backup. This option might not be valid if the system requires all the filesets that it currently has on it to run. This includes filesets whose names begin with devices, for example: devices.pci.xxxxxx.rte). Do not remove any filesets for devices that you might have on other systems in your environment because the resulting backup may not be able to boot or install onto those systems. 3). This solution DOES NOT WORK on models with POWER4 or higher processors. For systems with POWER4 and higher processors, refer to option 4 in lieu of this option. This option is only valid for systems with POWER 3 and lower processors. To boot the backup, first go to the open firmware prompt. To get to the open firmware prompt, when the system beeps twice after powering it on, press F8 on the keyboard (or the 8 key on an ASCII terminal). You can also get to the open firmware prompt from SMS. The open firmware prompt is also referred to as the "OK" prompt. On some systems there will be a menu option located on the initial SMS menu. On others, it will be located under the Multiboot menu. From the open firmware prompt execute the following: >setenv real-base 1000000 >reset-all Notes: a) The above commands will have to be executed each time you boot from the media with a large boot image (>12MB). b) If the backup is AIX 5.1 or AIX 5.2, the backup must have APAR IY40824 (AIX 5.1) or IY40975 (AIX 5.2). This implies that the system where the backup was created was running with the APAR installed at the time the backup was taken. 4). This solution WORKS ONLY on models with POWER4 or higher processors. If APAR IY57522 (AIX 5.1) or IY56839 (AIX 5.2) was installed prior to making the backup and FIRMWARE on the system supports boot from large boot images, the system will be able to boot from the media as expected. Notes: a) To use this option, the backup must have the recommended APAR. This implies that the system where the backup was created was running with the APAR installed at the time the backup was taken. b) The system being booted must be POWER4 or later and at a level of FIRMWARE that supports boot from large boot images (>12MB). c) To download the latest firmware, access the technical support microcode website at: http://techsupport.services.ibm.com/server/mdownload2/download.html CREATING BOOTABLE CD MEDIA: For instructions about how to create bootable cd media, please read the /usr/lpp/bos.sysmgt/mkcd.README file. Backing up DMAPI filesystems In this release, AIX has implemented DMAPI (Data Management Application Programming Interface) for JFS2 filesystems. Depending on the data management application used, it is possible that the data residing in a DMAPI filesystem may not be accurately represented to AIX. As a result, mkcd may not be able to calculate its temporary space requirements and thus may experience out of space conditions. Additionally, installation/restoration of a backup may result in failure to restore all DMAPI filesystem files if the filesystem was not created big enough to contain all the data residing in the filesystem. The data management application does not manage the DMAPI filesystem at restore time. Due to the above situations, the default is that mksysb/savevg and mkcd do not back up files within DMAPI filesystems. The filesystems will be recreated on restoration of the backup, but no data will be restored. If it is desired to back up the files, then add a -A flag to the mksysb/savevg or mkcd command currently being used. However, backup and restore behaviour will be unpredictable dependent on the data management applications control of files in the DMAPI filesystems. 0512-064 The mkszfile/mkvgdata command looks to see if there is 500 blocks of free working space in jfs2 filesystems. Restores may fail from backups (mksysb/savevg) created where there are filesystems with less than 500 blocks of free working space. **** END OF DOCUMENT ****