|
Wednesday April 20, 2005
Workaround for "FATAL: system is not bootable, boot command is disabled" on an obp
Poor error messages are a major source of annoyance. I hit this one today, for the first time in a few years. Background info - a v210 was rather abruptly powered down and feeling somewhat ill. So I logged onto the sc and got to my console, and type boot as one does.
{1} ok boot
FATAL: system is not bootable, boot command is disabled
Which is about as helpful as someone telling me the box is currently a brick. Which I know already.
Anyway just in case you happen to hit this the fix/workaround is to set auto-boot? to false, reset the box, and then set it to true and finally boot as shown below.
{1} ok setenv auto-boot? false
auto-boot? = false
{1} ok reset-all
SC Alert: Host System has Reset
Sun Fire V210, No Keyboard
Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.11.4, 4096 MB memory installed, Serial #xxxxxxxx.
Ethernet address 0:3:ba:xx:xx:xx, Host ID: 83xxxxxx.
{1} ok setenv auto-boot? true
auto-boot? = true
{1} ok boot
.......... lots of output ........
volume management starting.
The system is ready.
xxxxxx console login:
(2005-04-19 20:31:07.0)
Permalink
And Nicky V. is onboard....
One of the other folks in my group, Nicky Veitch, has started his blog, joining Sean, Gleb and myself. Of interest straight away are his notes on filebench - a benchmark that will be released soon onto sourceforge ( Richard leads the design and development off filebench).
I kinda like the current parking spot for his bike as well ;).
(2005-04-19 19:55:57.0)
Permalink
|
