Re: Adendum - mksysb restore hangs on 0c45 from tape at 530 ml4 on pseries 7028 6E1

rob@xxxxxxxxxxxxxxxx wrote:
The test of the failure from the cfgcon command is

"cfgcon: Failure accessing the device database (ODM)" error code 36

Is that really the only output from the mksysb restore in debug mode ?
Normaly you should see much more data round that error messages.


tried the above, RECOVER_DEVICES=
ALL_DEVICES_KERNELS=yes

and there was no difference

After reading your original post again:
A 0c45 message means:
....
c45
Failed to configure a system console
The cfgcon command failed because of missing device support for either
the graphic adapter or standard I/O slot for ASCII monitors. You must
install the appropriate device support on the system from which the
backup tape was made, or install the appropriate device support on the
network boot server, reboot the server, and remake the network boot
image for the client.
.....

Normaly it means that the bos.rte.console fileset is missing. But
little more debug information would be nice ( 10-20 lines before cfgcon
fails should be enough )

But i would like to step a little bit back and would suggest the
following:

Make a minimun installation on the test system (TS) from the CD - no
mirroring/ no tcb , Just a simple installation with a configured
network.

Create a mksysb from that installation and try to restore it back to
the machine itself.
1) No changes are done to the original bosinst_data for the first
restore
( Except set : BOSINST_DEBUG = yes )

if step 1 is ok then go to step 2)
If not call IBM

2) Change the bosinst_data file to the example below
( Except set : BOSINST_DEBUG = yes )

If step 2 is successfull then use the simple bosinst_data on your
primary system and create a new mksysb ( Do not forget to set
BOSINST_DEBUG = yes ) . Use this mksysb to restore it on your test
system.
If this fails. Call IBM and/or post the LED code and the error messages
on the screen.
If it works:
Change the bosinst_data to your special needs. BUT do only changs which
are really needed !
An bad example is your target_disk_data stanze which looks like a mess
for me.

Reagarding
I'll see what happens. The reason I use recover devices is for cloning.
The aio and ipsec devs (at least) +comms, are conveniently configured
this way?
In my option : NO.
Normal i do just simple installations and use post configure scripts to
configure the system to my needs. IMHO mksyb images are often to much
misused for cloning a fully configured system.
An mksysb is a SYSTEM-BACKUP and not a cloning software.

- Just think what happen if you get a new machine with slightly
different hardware.
You might fail miserable

So if you would like to clone: Create a machine with all fileset
needed, with no configuration done ( no mirror, no network and what
so ever ) and use post script to configure the system finaly.
On AIX you have for all task commands so writing post configuration
scripts is pretty simple.

hth
Hajo



This is an example for bosinst_data from the below mentioned IBM
website

control_flow:
CONSOLE = Default
INSTALL_METHOD = overwrite
PROMPT = no
EXISTING_SYSTEM_OVERWRITE = yes
INSTALL_X_IF_ADAPTER = yes
RUN_STARTUP = yes
RM_INST_ROOTS = no
ERROR_EXIT =
CUSTOMIZATION_FILE =
TCB = no
INSTALL_TYPE =
BUNDLES =
RECOVER_DEVICES = no
BOSINST_DEBUG = no
ACCEPT_LICENSES = yes
DESKTOP = NONE
INSTALL_DEVICES_AND_UPDATES = yes
IMPORT_USER_VGS =
ENABLE_64BIT_KERNEL = Default
CREATE_JFS2_FS = Default
ALL_DEVICES_KERNELS = yes
GRAPHICS_BUNDLE = yes
MOZILLA_BUNDLE = no
KERBEROS_5_BUNDLE = no
SERVER_BUNDLE = no
REMOVE_JAVA_118 = no
HARDWARE_DUMP = yes
ADD_CDE = no
ADD_GNOME = no
ADD_KDE = no
ERASE_ITERATIONS = 0
ERASE_PATTERNS =

target_disk_data:
LOCATION =
SIZE_MB =
HDISKNAME =

locale:
BOSINST_LANG =
CULTURAL_CONVENTION =
MESSAGES =
KEYBOARD =


Some addtional questions:
1 )You really do not use the 64bit kernel ?
2) Do you really use the TCB ?

Additional help
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp

and search for bosinst_data

.

Relevant Pages

  • Re: Restore mksysb/shrink filesystems
    ... I have the option when restoring from an AIX 5.1 mksysb tape after booting ... from the installation cd: ... Subject: Restore mksysb/shrink filesystems ... run a mksysb without the -i or -m flags. ...
    (AIX-L)
  • Re: 5.3 ML4 - mksysb restore - 0c45 on display (BUG?)
    ... There have been issues with the boot image on 5.1 and 5.2. ... Booting from the AIX installation CD is the simplest solution. ... remove device filesets from the server and make another mksysb. ... 5.3 ML4 - mksysb restore - 0c45 on display ...
    (AIX-L)
  • Re: Starting Aix 4.3.3 ML11 without /tmp
    ... Installation using a mksysb is a multi ... Both files are part of the backup, ... >restore them and check what is in there. ... vous pouvez faire un installation jusqu'au Maintenance Shell ...
    (comp.unix.aix)
  • Re: mksysb reloaded after raid configured
    ... load the necessary drivers and restore the MKSYSB for you. ... probably the drivers of RAID adapter only can be loaded AFTER AIX ... AIX can't see any boot drive with this configuration. ...
    (AIX-L)
  • Re: How to migrate existing users and groups to a new (upgraded) system??
    ... When I restore my configuration over a new ... >>installation, those three files seem to be sufficient. ... I have this whole business set up as a set of backup/restore scripts ...
    (comp.unix.bsd.freebsd.misc)