Call 911

Just type  » 911  »  on the Installation menu :

                    Welcome to Base Operating System
                     Installation and Maintenance

Type the number of your choice and press Enter. Choice is indicated by

 1 Start Install Now with Default Settings

   2 Change/Show Installation Settings and Install

   3 Start Maintenance Mode for System Recovery

   4 Configure Network Disks (iSCSI)

   5 Select Storage Adapters

   88  Help ?
   99  Previous Menu

 Choice [1]:  911          

It should display « BOSINST_DEBUG enabled » :

                   Welcome to Base Operating System
                     Installation and Maintenance

Type the number of your choice and press Enter. Choice is indicated by

 1 Start Install Now with Default Settings

   2 Change/Show Installation Settings and Install

   3 Start Maintenance Mode for System Recovery

   4 Configure Network Disks (iSCSI)

   5 Select Storage Adapters

    BOSINST_DEBUG enabled

   88  Help ?
   99  Previous Menu

 Choice [1]:            

 

Let’s debug

Now we can launch migration again and check why it crashes (in my example , my AIX 5.3 to 6.1 migration got stucked at boot code 0c49 : « Could not mount the BOS Install file system. » ) :

+ mount -o log=/dev/hd8 /dev/hd4 /mnt
Replaying log for /dev/hd4.
mount: /dev/hd4 on /mnt: Unformatted or incompatible media
The superblock on /dev/hd4 is dirty.  Run a full fsck to fix.
+ mountrc=1
+ + getlvcb -tt hd4
preservetype=jfs2
+ preservetype=jfs2
+ preservetype=jfs2
+ [[ jfs2 = jfs ]]
+ [ 1 != 0 ]
+ mount -v jfs2 -o log=/dev/hd8 /dev/hd4 /mnt
Replaying log for /dev/hd4.
mount: /dev/hd4 on /mnt: Unformatted or incompatible media
The superblock on /dev/hd4 is dirty.  Run a full fsck to fix.
+ [ 1 = 0 ]
+ /usr/lib/methods/showled 0xA49
+ BI_Error BOS Install 51 2 / (root)

Could not mount the BOS Install file system.
ID#        OPTION
1        Continue
2        Perform System Maintenance and Then Continue
Enter ID number:  2

#  fsck -fy /dev/hd4
The current volume is: /dev/hd4
Primary superblock is valid.
Could not load program /sbin/helpers/jfs2/logredo64:
Dependent module /../usr/lib/libc.a(shr_64.o) could not be loaded.
File /../usr/lib/libc.a is not an
archive or the file could not be read properly.
System error: Exec format error
J2_LOGREDO:log redo processing for /dev/hd4
Primary superblock is valid.
*** Phase 1 - Initial inode scan
*** Phase 2 - Process remaining directories
*** Phase 3 - Process remaining files
*** Phase 4 - Check and repair inode allocation map
*** Phase 5 - Check and repair block allocation map

File system is clean.
Superblock is marked dirty (FIXED)
All observed inconsistencies have been repaired.

… My root device hd4 was corrupted… fsck fixed it and after a reboot, NIM migration went smoothly !  

 

Enable debug for a nimadm operation

Sometimes you just need to know what’s going on with your nim -o or nimadm operation.

You’ll just have to export the INST_DEBUG variable, before executing the nimadm command, like this  :

 # export INST_DEBUG=yes

nimadm -l lpp_source61TL9SP2 -s spot61TL9SP2 -c [host] -d hdisk2 -j nimadmvg -YVD

Hope it helps.

LINKS

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.install/doc/insgdrf/debug_output_without_nim_bos.htm

Share Button
NIM : enabling debug mode for a bos install without using a bosinst_data resource
Taggé sur :            

Laisser un commentaire