Problems after upgrading to AIX 4.3.3 ML-11

[stevkov]

Hi, i upgraded AIX 4.3.3 form ML1 to ML11 but after the restart it couldn't go to graphics mode (suspending desktop login) also ping (error 0821-067), telnet and other network commands don't work.

on the other side, smitty, and other basic commands (cp, rm, etc..) work without any problems, but when i tried to install one APAR to try to fix the problem i got:

0301-111 /usr/lib/boot/bin/mkboot_rspc: Error in Object Data Manager routine

0301-158 bosboot: mkboot failed to create bootimage

One of possible reasons is corrupted boot image, what is the fastest and easiest way to solve the problem, also are there gonna be some data loses, any advice or help is welcomed...

 

[stevkov]

Sorry, i forgot this errors:

0503-407 installp: An error occurred during bosboot processing, when trying to install
0821-223 Cannot get records from CuAt,
0821-229 ifconfig command failed, on ifconfig -a

 

[Mag0007]

run this command first.

lppchk -v -m3

and paste it here.

 

[stevkov]

Thanks for the fast reply, but the server is like 40 miles from here and i will not gonna be there until tommorow, so if somebody also has some other ideas, feel free to tell me...

 

[Mag0007]

what does oslevel -r give you? Does it say ML 11 or still your old ML?

lppchk -v will see what lpp package issues you are having, first fix those before you do anything.

 

[stevkov]

oslevel - r says it's ML 9 ?!

And i did upgrade from ML 1 to ML 11...

 

[stevkov]

The output from lppchk -v -m3 is:

The following file sets need to be installed or corrected to bring the
system to a consistent state:

X11.motif.lib 4.3.3.81 (BROKEN)

I know this, but when i tried to install this file, i got errors:
0301-111 /usr/lib/boot/bin/mkboot_rspc: Error in Object Data Manager routine
0301-158 bosboot: mkboot failed to create bootimage
0503-407 installp: An error occurred during bosboot processing, when trying to install
0301-165 bosboot: WARNING! System not bootable

It looks a lot like that the boot image was corrupted and when i restarted the server, the troubles started.

I found the following procedure to re-create boot image on AIX 5.2, i'm not sure will it work on 4.3.3.

1. Insert the product media into the appropriate drive.
2. Power on the machine following the instructions provided with your system.
3. From the System Management Services menu, select Multiboot.
4. From the next screen, select Install From.
5. Select the device that holds the product media and then select Install.
6. Select the AIX version icon.
7. Follow the online instructions until you can select which mode you use for installation. At that point, select Start Maintenance Mode for System Recovery.
8. Select Access a Root Volume Group.
9. Follow the online instructions until you can select Access this Volume Group and start a shell.
10. Use the bosboot command to re-create the boot image. For example:
bosboot -a -d /dev/hdisk0
If the command fails and you receive the following message:
0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device.
Try to resolve the problem using one of the following options, and then run the bosboot command again until you have successfully created a boot image:
o Delete the default boot logical volume (hd5) and then create a new hd5.
Or
o Run diagnostics on the hard disk. Repair or replace, as necessary.
If the bosboot command continues to fail, contact your customer support representative.
Attention: If the bosboot command fails while creating a boot image, do not reboot your machine.
11. When the bosboot command is successful, use the reboot command to reboot your system.

 

[hirschaj]

Hopefully you only applied the updates, just use smitty to reject the applied updates and roll back to the previous version.


Jim Hirschauer

http://www.aixexpert.com

 

[Mag0007]

Okay. REMOVE that file dependencies and errors.

lppchk -v -m3 will show you all the dependency errors.


REMOVE them!

Reinstall by smitty update_all

which should fix a lot of things!

then rerun oslevel -r, that should be up to ML11

Another good command is

oslevel -rl 4300-11

 

[stevkov]

How should i remove them? Through smitty? or?

 

[hirschaj]

Can you provide output from the following command....

ls -l /etc/objrepos/Cu*

It looks like your ODM may be corrupt.


Jim Hirschauer

http://www.aixexpert.com

 

[stevkov]

Here is the output from ls -l /etc/objrepos/Cu*

as i said, the network is down and the system doesn't have a floppy so i'll just write the list of files:

CuAt 20480 bytes
CuAt.vc 4096 bytes
CuDep 4096 bytes
CuDv 12288 bytes
CuDvDr 36864 bytes
CuVPD 16384 bytes

Just for comparasion on the other server (AIX 5.1):
# ls -l /etc/objrepos/Cu*
-rw-r--r-- 1 root system 16384 25 May 09:36 /etc/objrepos/CuAt
-rw-r--r-- 1 root system 4096 25 May 09:36 /etc/objrepos/CuAt.v
-rw-r--r-- 1 root system 4096 24 May 13:04 /etc/objrepos/CuDep
-rw-r--r-- 1 root system 12288 25 May 09:36 /etc/objrepos/CuDv
-rw-r--r-- 1 root system 36864 24 May 13:04 /etc/objrepos/CuDvDr
-rw-r--r-- 1 root system 4096 24 May 13:04 /etc/objrepos/CuPath
-rw-r--r-- 1 root system 4096 24 May 13:04 /etc/objrepos/CuPath
-rw-r--r-- 1 root system 4096 24 May 13:04 /etc/objrepos/CuPath
vc
-rw-r--r-- 1 root system 4096 24 May 13:04 /etc/objrepos/CuPath
-rw-r--r-- 1 root system 16384 25 May 04:05 /etc/objrepos/CuVPD

 

[hirschaj]

Also make sure the permissions on those files look correct.

Try running this command to see if you can access the Customized Attributes database....

odmget -qname=en0 CuAt

That is strictly an informational command so don't worry about messing up the ODM or anything.

One other thing to try is running this command....
bosboot -ad /dev/ipldevice

It will try to recreate the boot device.

Also, output from "bootlist -m normal -o" wouldn't hurt.


Jim Hirschauer

http://www.aixexpert.com