when running updates to 5200-08 I get an error:

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

So I try

bosboot -ad /dev/hdisk0 and I get

0301-154 bosboot: missing proto file: /tmp/bosboot_786560_13680/
boot_ODM/CuData

Then lppchk -v reports

lppchk: The following filesets need to be installed or corrected to
bring
the system to a consistent state:

bos.64bit 5.2.0.95 (not installed; requisite
fileset)
bos.adt.include 5.2.0.105 (not installed; requisite
fileset)
bos.adt.include 5.2.0.95 (not installed; requisite
fileset)
bos.mp 5.2.0.105 (not installed; requisite
fileset)
bos.mp 5.2.0.95 (not installed; requisite
fileset)
bos.mp64 5.2.0.105 (not installed; requisite
fileset)
bos.mp64 5.2.0.95 (not installed; requisite
fileset)
bos.net.tcp.client 5.2.0.95 (not installed; requisite
fileset)
bos.net.tcp.client 5.2.0.105 (not installed; requisite
fileset)
bos.net.tcp.server 5.2.0.105 (not installed; requisite
fileset)
bos.perf.perfstat 5.2.0.95 (not installed; requisite
fileset)
bos.perf.tools 5.2.0.105 (not installed; requisite
fileset)
bos.rte.console 5.2.0.95 (not installed; requisite
fileset)
bos.rte.devices 5.2.0.95 (not installed; requisite
fileset)
bos.rte.filesystem 5.2.0.95 (not installed; requisite
fileset)
bos.rte.libcfg 5.2.0.95 (not installed; requisite
fileset)
bos.rte.security 5.2.0.95 (not installed; requisite
fileset)

suma -x -a RqType=Fileset -a RqName=bos.64bit -a RqLevel=5.2.0.95 -a
DLTarget=/data/tmp/fixes

And nothing gets downloaded.

Any Ideas?

Ted Fiedler

..
..

>
> suma -x -a RqType=Fileset -a RqName=bos.64bit -a RqLevel=5.2.0.95 -a
> DLTarget=/data/tmp/fixes
>
> And nothing gets downloaded.

accoring to fix central this version does not exist
http://www-1.ibm.com/support/docview...UTF-8&lang=all


>
> Any Ideas?
>
> Ted Fiedler
>
> .
> .

I had this problem but did not properly document the solution. I
believe it was one of two things, but they're very different from each
either (either way have your mksysb's ready to revert to!):

1) Have IBM send latest 5.2 level media, then use that to upgrade.
2) Also from latest 5.2 level media, replace your customized ODM
database w/ the default one from the CD/DVD -- manually restore OS
config.

Apologies for not remembering more for you... I did post about this
back then, and there were some helpful hints:

http://groups.google.com/group/comp.... 848716485b97

Tyler

On Mar 26, 8:16*am, "fiedl...@gmail.com" <fiedl...@gmail.com> wrote:
> when running updates to 5200-08 I get an error:
>
> 0503-409 installp: *bosboot verification starting...
> 0503-497 installp: *An error occurred during bosboot verification
> processing.
>
> So I try
>
> bosboot -ad /dev/hdisk0 and I get
>
> 0301-154 bosboot: missing proto file: /tmp/bosboot_786560_13680/
> boot_ODM/CuData
>
> Then lppchk -v reports
>
> lppchk: *The following filesets need to be installed or corrected to
> bring
> * * * * *the system to a consistent state:
>
> * bos.64bit 5.2.0.95 * * * * * * * * * * *(not installed; requisite
> fileset)
> * bos.adt.include 5.2.0.105 * * * * * * * (not installed; requisite
> fileset)
> * bos.adt.include 5.2.0.95 * * * * * * * *(not installed; requisite
> fileset)
> * bos.mp 5.2.0.105 * * * * * * * * * * * *(not installed; requisite
> fileset)
> * bos.mp 5.2.0.95 * * * * * * * * * * * * (not installed; requisite
> fileset)
> * bos.mp64 5.2.0.105 * * * * * * * * * * *(not installed; requisite
> fileset)
> * bos.mp64 5.2.0.95 * * * * * * * * * * * (not installed; requisite
> fileset)
> * bos.net.tcp.client 5.2.0.95 * * * * * * (not installed; requisite
> fileset)
> * bos.net.tcp.client 5.2.0.105 * * * * * *(not installed; requisite
> fileset)
> * bos.net.tcp.server 5.2.0.105 * * * * * *(not installed; requisite
> fileset)
> * bos.perf.perfstat 5.2.0.95 * * * * * * *(not installed; requisite
> fileset)
> * bos.perf.tools 5.2.0.105 * * * * * * * *(not installed; requisite
> fileset)
> * bos.rte.console 5.2.0.95 * * * * * * * *(not installed; requisite
> fileset)
> * bos.rte.devices 5.2.0.95 * * * * * * * *(not installed; requisite
> fileset)
> * bos.rte.filesystem 5.2.0.95 * * * * * * (not installed; requisite
> fileset)
> * bos.rte.libcfg 5.2.0.95 * * * * * * * * (not installed; requisite
> fileset)
> * bos.rte.security 5.2.0.95 * * * * * * * (not installed; requisite
> fileset)
>
> suma -x -a RqType=Fileset -a RqName=bos.64bit -a RqLevel=5.2.0.95 -a
> DLTarget=/data/tmp/fixes
>
> And nothing gets downloaded.
>
> Any Ideas?
>
> Ted Fiedler
>
> .
> .

The fix ended up being fairly simple

edit /usr/sbin/bosboot

right after the
#!/usr/bin/ksh

add the line
exit 0

To bypass the bosboot checks completely.

Then smit update_all. When finished - check /usr/sbin/bosboot - make
sure that the exit 0 line gets removed ( if the update process did not
already replace bosboot )

check your level ( oslevel -r ) Perform a bosboot, and reboot.

Thanks
Ted

On Mar 26, 11:47*am, slad...@gmail.com wrote:
> I had this problem but did not properly document the solution. *I
> believe it was one of two things, but they're very different from each
> either (either way have your mksysb's ready to revert to!):
>
> 1) Have IBM send latest 5.2 level media, then use that to upgrade.
> 2) Also from latest 5.2 level media, replace your customized ODM
> database w/ the default one from the CD/DVD -- manually restore OS
> config.
>

Wow that's exactly what I did... I remember it now.

On Mar 26, 10:57*am, "fiedl...@gmail.com" <fiedl...@gmail.com> wrote:
> The fix ended up being fairly simple
>
> edit /usr/sbin/bosboot
>
> right after the
> #!/usr/bin/ksh
>
> add the line
> exit 0
>
> To bypass the bosboot checks completely.
>
> Then smit update_all. When finished - check /usr/sbin/bosboot - make
> sure that the exit 0 line gets removed ( if the update process did not
> already replace bosboot )
>
> check your level ( oslevel -r ) Perform a bosboot, and reboot.
>
> Thanks
> Ted
>
> On Mar 26, 11:47*am, slad...@gmail.com wrote:
>
>
>
> > I had this problem but did not properly document the solution. *I
> > believe it was one of two things, but they're very different from each
> > either (either way have your mksysb's ready to revert to!):
>
> > 1) Have IBM send latest 5.2 level media, then use that to upgrade.
> > 2) Also from latest 5.2 level media, replace your customized ODM
> > database w/ the default one from the CD/DVD -- manually restore OS
> > config.- Hide quoted text -
>
> - Show quoted text -