re-install bos.up?

[mcroy71]

Hi,
Strange problem: my usr/lib/boot/unix_up file has a size 0. This results in an error when installing ML11 on aix 4.3.3.0.

lppchk -f --> lppchk: 0504-208 Size of /usr/lib/boot/unix_up is 0, expected value was 3281217.

I have tried to re-install it serveral ways (smitty), but no success.

Except for a complete re-install of my system, what other options do I have? Couldn't find a decent APAR to fix the problem as well.

thanx!

 

[kHz]

To reinstall any base level fileset when you are at a higher level of maintenance, you have to install the base bos.up and do a force overwrite, then install your ML11.

 

[mcroy71]

Hi Khz,
Tried, but was unsuccessful. Used following lines to install the bos up

# installp -acF -d /dev/cd0 bos.up
and
# installp -acFNQqSwX -d /dev/cd0 bos.up

but both were unsuccessful and ended with the following error:

FILESET STATISTICS
------------------
1 Selected to be installed, of which:
1 Passed pre-installation verification
----
1 Total to be installed

0503-409 installp: bosboot verification starting...
0503-497 installp: An error occurred during bosboot verification processing.

Any ideas on how I could bypass this prob???

thnx

 

[p5wizard]

If you have a similar machine with the same AIX oslevel -r, then I would just copy over the /usr/lib/boot/unix_up from that machine and then reinstall base level and ML updates like kHz suggested.

Is your machine uni- or multiprocessor? If uni, then you don't even need bos.up (see what file the links /unix and /usr/lib/boot/unix point to)

As your machine is not using bos.up (which I assume because your machine is still up and running without it), then the version you are copying over can even be older than the one that is missing as you will be reinstalling it anyway. Same oslevel should suffice.

You could also extract the file from the bos.up.5.2.0.X file - it should be a BFF file:

list files contained in the BFF file:
restore -T -q -f /path/to/ML11files/bos.up.5.2.0.X

restore the file
restore -x -q -f /path... ./usr/lib/boot/unix_up

Please note: use exact same filename as is listed in restore -T output


HTH,

p5wizard

 

[kHz]

A bosboot verification failure like you got may be due to a corrupt or nonexistent BLV. You can try to recreate it:

rmlv hd5
chpv -c hdisk # --> for ALL disks -c clears boot record of given pv
mkboot -cd /dev/hdisk# --> ..use this if the above (chpv) command fails
mklv -y hd5 -t boot -a e rootvg 1 hdisk#
bosboot -ad /dev/hdisk#
sync;sync;sync
reboot

 

[mcroy71]

Thanx p5! your tip did the trick Managed to copy the bos.up from the install CD and overwrite manually the unix_up file. :-D

It was somewhat strange, because i AM running a UP system. It is an old AIX box, but somehow I only got into trouble when doing a MKSYSB or a ML update.... weird. I would reckon i had need the kernel at boot!

The solution proposed by kHz intrigued me: wouldn't the rmlv kill my bos??? <

 

[p5wizard]

no hd5 is only needed at boot time, what intrigues me more is that your system kept running without the unix_up file.

as asked earlier what does /unix and /usr/lib/boot/unix point to?

glad I could help


HTH,

p5wizard

 

[mcroy71]

The sym.link /unix to /usr/lib/boot/unix to the unix_up file!