Boot archive error or corrupt

A few weeks ago, I got a little problem with my solaris box, namely solaris won't boot because the boot archive was corrupt, *sigh*. Anyway the boot archive in solaris 10 was contain kernel module and configuration file was needed for solaris to startup the system.

Error:

module /platform/i86pc/boot_archive error 3 bad or corrupt data while decompressing file

Workaround:

Boot up your solaris in "solaris failsafe mode", next solaris image will mount with writeable mode on "/a" mount point

sh> rm -f /a/platform/i86pc/boot_archive
sh> bootadm update-archive -R /a
sh> reboot
Printed from: http://sysinfo.bascomp.org/2009/05/boot-archive-error-or-corrupt/ .
© 2010.

12 Comments   »

  • Patrick says:

    Thanks very much for this info. It was the first link that came up in google and it worked perfectly!

  • Hendrawan says:

    You're welcome Patrick.
    Thanks for the feedback.

    *untungnya ni postingan dah gue ganti jadi make bahasa inggris, ;d*

  • Ediel says:

    Many many thanks Hendrawan,

    I also got that error but its resolved.

  • Francisco says:

    hello Hendrawan

    Thanks a lot for you help it was cool

  • Hendrawan says:

    @all: You're welcome guys, eniwey thanks for your feedback.

  • Ganesh Krishnaa says:

    Thank you very much Hendrawan!!!You rocks:)

  • Evie says:

    I started off with the same error (system was unable to completely update the boot-archive due to an issue with disk space), so I removed/rebuilt the boot-archive in failsafe mode. I still can't boot - instead of the initial O/S load message, the cursor just blinks and hangs. Any ideas?

  • Hendrawan says:

    @Evie: whether the problem with the disk space was already completed, for example removing unused files

  • Praveen says:

    Thanks a lot Hendrawan

  • Sam says:

    Boot up your solaris in “solaris failsafe mode”, next solaris image will mount with writeable mode on “/a” mount point
    sh> rm -f /a/platform/i86pc/boot_archive
    sh> bootadm update-archive -R /a
    sh> reboot

    Above steps resolved the issue but when I restarted server, error persist
    Can somebody suggest permanent solution.
    Thanks in advance

  • Hendrawan says:

    @praveen
    You're welcome, it's good if it can work

  • Hendrawan says:

    @Sam
    I write this things, cause this work for permanent solution, not for temporary (refer to bootadm update-archive -R),
    other things, please check your root space

RSS feed for comments on this post , TrackBack URI

Leave a Reply

  • Search