Error Handling Summary - Fujitsu SPARC Enterprise T2000 Administration Manual

degraded boot when a subsystem failure is detected. Both the auto-boot? and
auto-boot-on-error? switches must be set to true to enable an automatic
degraded boot. To set the switches, type:
ok setenv auto-boot? true
ok setenv auto-boot-on-error? true
Note – The default setting for auto-boot-on-error? is false. The system will
not attempt a degraded boot unless you change this setting to true. In addition, the
system will not attempt a degraded boot in response to any fatal nonrecoverable
error, even if degraded booting is enabled. For examples of fatal nonrecoverable
errors, see

Error Handling Summary

Error handling during the power-on sequence falls into one of the following three
cases:
If no errors are detected by POST or OpenBoot firmware, the system attempts to
■
boot if auto-boot? is true.
If only nonfatal errors are detected by POST or OpenBoot firmware, the system
■
attempts to boot if auto-boot? is true and auto-boot-on-error? is true.
Nonfatal errors include the following:
■
■
■
■
■
■
Note – If POST or OpenBoot firmware detects a nonfatal error associated with the
normal boot device, the OpenBoot firmware automatically unconfigures the failed
device and tries the next-in-line boot device, as specified by the boot-device
configuration variable.
36 SPARC Enterprise T2000 Server Administration Guide • April 2007
"Error Handling Summary" on page
SAS subsystem failure. In this case, a working alternate path to the boot disk is
required. For more information, see
Ethernet interface failure.
USB interface failure.
Serial interface failure.
PCI card failure.
Memory failure. Given a failed DIMM, the firmware will unconfigure the entire
logical bank associated with the failed module. Another nonfailing logical
bank must be present in the system for the system to attempt a degraded boot.
36.
"Multipathing Software" on page 42.