Asset ID:	1-71-1010565.1
Update Date:	2011-04-26
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1010565.1 :   BOOT: Explanation of the "FATAL: system is not bootable, boot command is disabled" OBP message  


PreviouslyPublishedAs
214538

Description
This Technical Instruction explains what the "FATAL: system is not bootable, boot command is isabled" OBP (open boot PROM) message indicates and what can be done to get the system to boot up.

Steps to Follow
This type of a warning can appear on systems such as a Sun Fire[TM] V880.
In most cases, this warning occurs at the OBP "ok" prompt if the power-up initialization (right after the banner was displayed) was aborted. Usually, this is done by using the Stop-A keystroke (XIR Reset). If after such an occurrence "boot" command is executed, the system displays the following error:

{1} ok boot
FATAL: OpenBoot initialization sequence prematurely terminated.
FATAL: system is not bootable, boot command is disabled 

The system at that point does not boot. In most cases, this just means that since the proper initialization of the machine wasn't allowed to complete, the system is unable to boot. This is done to make sure that OS deamons (such as picld) do not have problems as they start up during boot (because of the improperly initialized memory, etc.). To get the machine to boot properly, issue the "reset-all" command. If for whatever reason there is a need for the "boot" command to be executed manually, please run the following command sequence at the "ok" prompt:

ok  setenv auto-boot? false
ok  reset-all  

Now, the machine will reset. Allow it to fully initialize. It will then give the ok prompt without booting automatically. At this point if the "boot" command is manually executed, it should work without errors. Also, before running the manual boot, the "auto-boot?" variable could be set back to "true". This way, the system will again be set back to its original setting for the next time it is reset or power cycled. NOTE: Seeing the "FATAL: system is not bootable ..." message even after following the above procedure most likely indicates a real problem (possibly a hardware problem) with that machine. Another possibility may be an invalid setting. If you suspect this you can use the following procedure. This procedure resets all parameters to factory default settings, so use caution.

ok  printenv         ### save this information ###
ok  set-defaults     ### to reset all parameters to factory default settings ###
ok  reset-all

Reference Technical Instruction to create any custom boot device aliases.

Product
Sun Fire V440R Server
Sun Fire V440 Server
Sun Fire V880 Server
Netra 440 Server

Internal Comments
For Internal Sun use only

This doc was created from info in bug 4856266 and radiance case 63759923
Since Engineering will not change the OBP FATAL message, this document
should assist TSEs and Customers in better understanding of the situation.
OBP, error, fatal, boot
Previously Published As
72173

Change History
Date: 2010-12-21
User name: Dencho Kojucharov
Action: Currency check
Comments: audited by Entry-Level SPARC Content Lead
made updates in the doc and the links

Date: 2006-01-17
User Name: 18392
Action: Update Canceled
Comment: *** Restored Published Content *** SSH Audit
Version: 0
Date: 2006-01-17
User Name: 18392
Action: Update Started
Comment: SSH Audit
Version: 0


Attachments

This solution has no attachment