Topic
  • 8 replies
  • Latest Post - ‏2015-08-28T18:17:56Z by BIAO
lion55
lion55
8 Posts

Pinned topic Problem in cleaning up a failed installation fileset

‏2009-03-03T09:28:21Z |
Hello ,

Problem in cleaning up a failed installation fileset. please find the error details below.

>installp -C sysmgt.websm.apps
0503-409 installp: bosboot verification starting...
0503-497 installp: An error occurred during bosboot verification processing.

>bootlist -m normal -o
hdisk0 blv=hd5
hdisk1 blv=hd5
>bosboot -ad /dev/hdisk1
0301-154 bosboot: missing proto file: /usr/lib/libisns.a

>bosboot -ad /dev/hdisk0
0301-154 bosboot: missing proto file: /usr/lib/libisns.a

>oslevel -s
5300-06-06-0811

Does anyone knows what causes the problem?
Thanks in Advance.
Updated on 2011-05-27T15:52:17Z at 2011-05-27T15:52:17Z by JimT66
  • Sprellster
    Sprellster
    12 Posts

    Re: Problem in cleaning up a failed installation fileset

    ‏2009-03-03T10:34:05Z  
    Change the /usr/sbin/bosboot script. AFter the "#!/usr/bin/ksh" simply insert "exit 0" so that the top two lines will be

    #!/usr/bin/ksh
    exit 0

    Then do the installp -C command again. Then remove the "exit 0" statement and re-run bosboot.
  • SystemAdmin
    SystemAdmin
    6902 Posts

    Re: Problem in cleaning up a failed installation fileset

    ‏2009-03-03T10:49:50Z  
    Hi,

    Post the output of

    lslpp -L sysmgt.websm.apps
    lppchk -v

    Also you can check any errors for filesystems in errpt and check whether /usr/lib/libisns.a is present.
  • lion55
    lion55
    8 Posts

    Re: Problem in cleaning up a failed installation fileset

    ‏2009-03-03T11:08:54Z  
    Change the /usr/sbin/bosboot script. AFter the "#!/usr/bin/ksh" simply insert "exit 0" so that the top two lines will be

    #!/usr/bin/ksh
    exit 0

    Then do the installp -C command again. Then remove the "exit 0" statement and re-run bosboot.
    By adding exit0 in bosboot script ,I have cleaned up the failed filesets .

    Still i am getting the error while running the bosboot command .

    >bosboot -ad /dev/hdisk0
    0301-154 bosboot: missing proto file: /usr/lib/libisns.a
    >bosboot -ad /dev/hdisk1
    0301-154 bosboot: missing proto file: /usr/lib/libisns.a


    installp -C
    0503-409 installp: bosboot verification starting...
    installp: bosboot verification completed.
    0503-408 installp: bosboot process starting...
    0503-292 This update will not fully take effect until after a
    system reboot.

    * * * A T T E N T I O N * * *
    System boot image has been updated. You should reboot the
    system as soon as possible to properly integrate the changes
    and to avoid disruption of current functionality.

    installp: bosboot process completed.

    installp: Cleaning up software for:
    sysmgt.websm.apps 5.3.8.0
    Installation Summary

    Name Level Part Event Result

    sysmgt.websm.apps 5.3.8.0 USR CLEANUP SUCCESS
  • grukrz1
    grukrz1
    128 Posts

    Re: Problem in cleaning up a failed installation fileset

    ‏2009-03-03T20:21:55Z  
    • lion55
    • ‏2009-03-03T11:08:54Z
    By adding exit0 in bosboot script ,I have cleaned up the failed filesets .

    Still i am getting the error while running the bosboot command .

    >bosboot -ad /dev/hdisk0
    0301-154 bosboot: missing proto file: /usr/lib/libisns.a
    >bosboot -ad /dev/hdisk1
    0301-154 bosboot: missing proto file: /usr/lib/libisns.a


    installp -C
    0503-409 installp: bosboot verification starting...
    installp: bosboot verification completed.
    0503-408 installp: bosboot process starting...
    0503-292 This update will not fully take effect until after a
    system reboot.

    * * * A T T E N T I O N * * *
    System boot image has been updated. You should reboot the
    system as soon as possible to properly integrate the changes
    and to avoid disruption of current functionality.

    installp: bosboot process completed.

    installp: Cleaning up software for:
    sysmgt.websm.apps 5.3.8.0
    Installation Summary

    Name Level Part Event Result

    sysmgt.websm.apps 5.3.8.0 USR CLEANUP SUCCESS
    probably the are more missing files to successfully complete "bosboot" command. The problem is due to broken update I guess.

    I met such problem once, and then I fixed it by copying missing files from other system on the same AIX level or from actual mksysb image (use restore command to extract specific file). Probably when you copy one file the bosboot will complain again for the other file. But there were only a few missing files in my case so I copied them one by one until bosboot run successful. After that, I had rebooted system and then installed successfully new system TL.
  • JimT66
    JimT66
    1 Post

    Re: Problem in cleaning up a failed installation fileset

    ‏2011-05-27T15:52:17Z  
    I had a similar problem doing the SP03 update for AIX7.1.
    Analysis:
    - when I downloaded the update filesets, the FTP session failed at the very end and six filesets did not download properly and were corrupted. I did not notice this until after I tried doing the o/s update.
    • I tried the o/s update on this and six filesets did not update. (sysmgt.cim.*)
    • the installp -C cleanup failed because the bosboot failed.
    • I disabled the bosboot by inserting the "exit 0" as line two, as described in this thread.
    • the installp -C cleanup succeeded -- it took several minutes to complete.
    • I also had to stopsrc -s the cimsys subsystem and that took several minutes.
    • After the cleanup I re-enabled the bosboot script by removing the "exit 0" line.
    • I re-downloaded the SP03 service pack -- let it run overnight. It completed successfully this time.
    • The update failed on the same bosboot error, so I had to disable the bosboot script once again, and this time the o/s update ran successfully.
    • one of the files updated was the bosboot script itself, so at the end of the o/s update the bosboot checking succeeded.
    • I double-checked the bosboot script to verify that it was not disabled.
    • Just to be certain, I ran " bosboot -a -d /dev/hdisk0" manually, and it succeeded.
    • I shutdown and rebooted the server, and it came up successfully and is now fully updated. The oslevel -s command returns:
    7100-00-03-1115

    All of the above was much faster than digging out the mksysb image and restoring it, especially since this is our NIM server that we updated. Everything is updated, including the updates that we had to clean up before we could continue.

    Jim T, Winnipeg
  • sarulanandam
    sarulanandam
    1 Post

    Re: Problem in cleaning up a failed installation fileset

    ‏2014-03-06T09:07:47Z  

    thanks a lot Jim T, for your step by step analysis.

    It helped me save a lot of time as I faced the same issue today :)

  • 58JF_Eduardo_Rascón
    1 Post

    Re: Problem in cleaning up a failed installation fileset

    ‏2015-01-09T22:08:26Z  
    • JimT66
    • ‏2011-05-27T15:52:17Z
    I had a similar problem doing the SP03 update for AIX7.1.
    Analysis:
    - when I downloaded the update filesets, the FTP session failed at the very end and six filesets did not download properly and were corrupted. I did not notice this until after I tried doing the o/s update.
    • I tried the o/s update on this and six filesets did not update. (sysmgt.cim.*)
    • the installp -C cleanup failed because the bosboot failed.
    • I disabled the bosboot by inserting the "exit 0" as line two, as described in this thread.
    • the installp -C cleanup succeeded -- it took several minutes to complete.
    • I also had to stopsrc -s the cimsys subsystem and that took several minutes.
    • After the cleanup I re-enabled the bosboot script by removing the "exit 0" line.
    • I re-downloaded the SP03 service pack -- let it run overnight. It completed successfully this time.
    • The update failed on the same bosboot error, so I had to disable the bosboot script once again, and this time the o/s update ran successfully.
    • one of the files updated was the bosboot script itself, so at the end of the o/s update the bosboot checking succeeded.
    • I double-checked the bosboot script to verify that it was not disabled.
    • Just to be certain, I ran " bosboot -a -d /dev/hdisk0" manually, and it succeeded.
    • I shutdown and rebooted the server, and it came up successfully and is now fully updated. The oslevel -s command returns:
    7100-00-03-1115

    All of the above was much faster than digging out the mksysb image and restoring it, especially since this is our NIM server that we updated. Everything is updated, including the updates that we had to clean up before we could continue.

    Jim T, Winnipeg

    Thanks a lot Jim! it worked, you saved me a lot of time.

     

    Cheers!

     

    >

  • BIAO
    BIAO
    4 Posts

    Re: Problem in cleaning up a failed installation fileset

    ‏2015-08-28T18:17:56Z  

    I have got the similar problem like:

    bosboot -v

    0301-154 bosboot: missing proto file: /tmp/bosboot_14876790_15152/boot_ODM/CuAtDef

    caused by a blue screen on my laptop while the upgrade is running,everything terminated unexpectedly , huge number of inconsistent filesets coming up.

    bosboot  verification will be running right before each try to install or update,so only resort is to skip bosboot verification.

    Super thanks to Jim.

    It worked for me and save me a lot of time.