Server User Manual

Chapter 1 Configuring the System Console 15
Using these commands results in the loss of all system coherence and state
information. A manual system reset could corrupt the server’s file systems, although
the fsck command usually restores them. Use this method only when nothing else
works.
Caution – Accessing the ok prompt suspends the Solaris OS.
When you access the ok prompt from a functioning server, you are suspending the
Solaris OS and placing the system under firmware control. Any processes that were
running under the operating system are also suspended, and the state of such processes
might not be recoverable.
After a manual system reset the system can be configured to boot automatically if
the OpenBoot auto-boot? configuration variable is set to true. See “System
Console OpenBoot Configuration Variable Settings” on page 17. If the server begins
to boot automatically after a reset, you must abort the boot with the ALOM system
controller break command or perform a graceful shutdown of the Solaris Operating
System after the boot has completed.
The commands you run from the ok prompt have the potential to affect the state of
the system. This means that it is not always possible to resume execution of the
operating system from the point at which it was suspended. Although the go
command will resume execution in most circumstances, in general, each time you
obtain the ok prompt, you should expect to have to reboot the system to get back to
the operating system.
For More Information About OpenBoot Firmware
For more information about the OpenBoot firmware, refer to the OpenBoot 4.x
Command Reference Manual. You can obtain an online version of the manual at
http://www.sun.com/documentation/
Obtaining the ok Prompt
This procedure provides several ways of reaching the ok prompt. For details about
when to use each method, see “OpenBoot ok Prompt” on page 12.