Antwort: mksysb restore error

• Previous message: Yi XIE: "´ð¸´: mksysb restore error"
• Next in thread: augusta Zhou: "Re: Antwort: mksysb restore error"
• Maybe reply: augusta Zhou: "Re: Antwort: mksysb restore error"
• Maybe reply: Green, Simon: "Re: Antwort: mksysb restore error"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date:         Fri, 3 Dec 2004 15:04:42 +0100
To: aix-l@Princeton.EDU

Are you trying to restore from a tape backup whose boot image is too large?
I had it once but it wasn’t important restore. Afterwards I found
following:



   IBM_PROLOG IBM_PROLOG_BEGIN_TAG
   IBM_PROLOG This is an automatically generated prolog.
   IBM_PROLOG
   IBM_PROLOG bos52F src/bos/usr/sbin/mkcd/README.S 1.4
   IBM_PROLOG
   IBM_PROLOG Licensed Materials - Property of IBM
   IBM_PROLOG
   IBM_PROLOG Restricted Materials of IBM
   IBM_PROLOG
   IBM_PROLOG (C) COPYRIGHT International Business Machines Corp. 2003,2004
   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

   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. This condition is only known to occur on CHRP systems with AIX
   5.1 or
   5.2 installed.

   To determine you 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 7028, 7029, 7038, 7039, and
   7040
   systems, see option 4 regarding these models.
   If APAR IY40824 (AIX 5.1) or IY40975 (AIX 5.2) was installed prior to
   making
   the backup, then you may boot from the backup and 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) To use this option, the backup must have this APAR in it and
   therefore
   must be created after installing the APAR.
   b) The above commands will have to be executed each time you boot from
   the
   large boot image backup media.

   4). This solution WORKS ONLY for models 7028, 7029, 7038, 7039, and
   7040.
   If APAR IY54804 (AIX 5.1) or IY53546 (AIX 5.2) was installed prior to
   making
   the backup and FIRMWARE on the system (these models only) being booted
   is
   at 3x040310 higher (where x is either H, J, K, R, or F), then the system
   will be able to boot from the media as expected.

   Note:
   a) To use this option, the backup must have this APAR in it and
   therefore
   must be created after installing the APAR.
   b) The system being booted must be one of these models and have this
   firmware level or higher on it.
   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:

   Preferably on the same system that the non-bootable backup came from,
   execute
   the following commands:

     # cd /var/adm/ras
     # ls ./bosinst.data ./image.data | backup -ivqf/tmp/fakemksysb
     # mkcd -m /tmp/fakemksysb -d /dev/cdx # Where cdx is an attached
   cdwriter
       OR
     # mkcd -m /tmp/fakemksysb -S # Will create a CD image which can be
                                    # transferred to a system with a
   cdwriter

   Note: The final mkcd command in the previous example makes an image
   that could
   be transferred to another system (AIX or non-AIX) for burning.
   Note: The bosinst.data file must be set for a prompted install (PROMPT
   = yes).

   **** END OF DOCUMENT ****



Could it be you have such a problem?

Ciao
Vesna




|---------+--------------------------------->
| | |
| | |
| | meijun_Zhou@SHANGHAIGM|
| | .COM |
| | |
| | Gesendet von: |
| | aix-l@Princeton.EDU |
| | 03.12.2004 08:40 |
| | Bitte antworten an |
| | aix-l |
| | |
|---------+--------------------------------->
>-------------------------------------------------------------------------------------------------------------------------|
  | |
  |An: aix-l@Princeton.EDU |
  |Kopie: |
  |Blindkopie: |
  |Thema: mksysb restore error |
>-------------------------------------------------------------------------------------------------------------------------|




AIX5.203

restore failure, stop at 0c52

(See attached file: error.gif)

What's mean?

Thanks.

Regards.
Zhou Meijun

IS Department
Shanghai General Motors Co., Ltd.

Tel: (021)28902879
Fax: (021)50317990
E-mail: meijun_zhou@shanghaigm.com(See attached file: error.gif)




This message and any attachment ("the Message") are confidential. If you
have received the Message in error, please notify the sender immediately
and delete the Message from your system , any use of the Message is
forbidden.
Correspondence via e-mail is primarily for information purposes. RZB
neither makes nor accepts legally binding statements unless otherwise
agreed to the contrary.

• Previous message: Yi XIE: "´ð¸´: mksysb restore error"
• Next in thread: augusta Zhou: "Re: Antwort: mksysb restore error"
• Maybe reply: augusta Zhou: "Re: Antwort: mksysb restore error"
• Maybe reply: Green, Simon: "Re: Antwort: mksysb restore error"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]