BOOT: Explanation of the "FATAL: system is not bootable, boot command is disabled" OBP message
--------------------------------------------------------------------------------
Keyword(s):OBP, error, fatal, boot
Description Top
This infodoc explains what the "FATAL: system is not bootable, boot command is disabled" OBP
message indicates and what can be done to get the system to boot up.
Document Body Top
This type of a warning can appear on systems such as a Sun Fire 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 occurence "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 or press
"STOP" key and "N" key together while machine is turning on (release both
keys when you see lights flash on keyboard) and allow the machine to boot
up "hands off".
Note: This "Stop + N" combination is only true when keyboard and
monitor/console are attached to the machine.
If for whatever reason the "boot" command has to be entered manually,
execute the following commands at the "ok" prompt:
setenv auto-boot? false
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 can 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 only 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.
Internal Only Top
:mrgreen: :mrgreen:
| sunmarmot 回复于：2004-05-21 20:37:17 |
| 现在好多的机器都有这个毛病 :em08: :em08:
老有人当是主板坏掉，烦S掉了 |
| 吹拂的晨风 回复于：2004-05-21 21:29:03 |
| 好东东，我顶！ |
| iricyan 回复于：2004-05-21 21:37:53 |
| ft，这也能算是精彩帖子？ 翻译成中文没什么价值。 |
| andrewleading_he 回复于：2004-05-25 16:35:20 |
| 我也有碰到这样的情况，
提示说 boot command disabled. 手关掉电源，再放放好光盘就好了 我觉得是数据不正确，系统从光盘那边得不到需要的数据 启动不了，就报这样的问题 |
| Philmoon 回复于：2004-05-25 16:42:19 |
| 本人认为，在ok下遇到错误后，reset一下是个好习惯。
此问题与112186补丁有关吗？ |
| lazyoracle 回复于：2004-05-25 17:42:13 |
| [quote:0c86518c57="iricyan"]ft，这也能算是精彩帖子？ 翻译成中文没什么价值。[/quote:0c86518c57]
有无价值与中文或英文无关 |
| lazyoracle 回复于：2004-05-25 17:53:04 |
| [quote:a6227dc97c="Philmoon"]本人认为，在ok下遇到错误后，reset一下是个好习惯。
此问题与112186补丁有关吗？[/quote:a6227dc97c] Agree. 修改OBP变量如diag-switch, 增加设备别名后,也要reset-all存进NVRAM. |
| bear 回复于：2004-06-02 12:22:46 |
| 今天翻精华看到的，补充两句。
我都是和用户说“系统还没自检完就会出现这个问题，自检完就好了” 其实就是这么回事， 只要大家按STOP+A别太快，等内存自检完boot 设备那行刚出来时按就没事，probe-scsi-all也能正常用，不会报错，boot也能用。 我也是试了几次才找到比较好的中断点的，好多机器中断早了，boot不了，晚了probe-scsi-all用不了，因为不想把auto-boot设成false(懒!) |
延伸阅读
文章来源于领测软件测试网 https://www.ltesting.net/