How to update the boot_archive when system is failing to boot with: The file just loaded does not appear to be executable - or - WARNING: The following files in / differ from the boot archive
(Doc ID 1431744.1)
Last updated on JANUARY 06, 2023
Applies to:
Solaris Operating System - Version 10 10/08 U6 and laterOracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (32-bit)
Oracle Solaris on x86 (32-bit)
Symptoms
If a Solaris system fails to boot with messages similar to the following are encountered, the system will need to be booted from alternate Oracle Solaris media ( e.g. the failsafe archive, cd / dvd media, or an install image over the network) in order to update the boot_archive:
Changes
The boot_archive can become out of sync with the files on the file system if the files have changed, but the boot_archive was not updated.
Normally the boot_archive is updated during a system reboot.
If for some reason the boot_archive is not updated, the system may fail to boot and the boot_archive will need to be manually updated while booted from alternate media.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| To update the boot_archive while booted to alternate media |
| x86 |
| References |