Sun Microsystems Blade 1500 - Page 61

Chapter 3 Basic Troubleshooting 3-7
Can’t open boot device
The device specified for
boot is unavailable.
• For hard drive, check
internal connections. Drive
might be corrupted. See
“Hard Drive Problem” on
page 4-8.
• For optical drive, check that
disc is bootable. Check
internal connections. See
“Optical Drive Problem” on
page 4-25.
• For network, check network
connections. Check boot
server. See “Network
Problem” on page 4-17.
Can’t run OBDIAG from the
device tree node or with the
active instance
Attempt to run OpenBoot
Diagnostics from a selected
device node.
Type:
ok unselect-dev
NOTICE - CPUx Banky DIMMs are
from different vendors.
A pair of DIMMs are each
from different
manufacturers.
Install DIMMs in identical
pairs. See
“Replacing the
DIMMs” on page 11-2.
NOTICE - CPUx Banky DIMMs have
different architectures and
will not be used.
A pair of DIMMs are each
of different architectures.
The DIMMs are not used.
Install DIMMs in identical
pairs. See
“Replacing the
DIMMs” on page 11-2.
Searching for self-test methods
. . . Rejecting alloc-mem!
OpenBoot Diagnostics
failed to start. Some devices
might be tied to other
processes.
Type:
ok unselect-dev
Starting xv-500 self-test
Sun XVR-1200 PROM error. Type:
ok show-devs
search for the text: xvr-1200
The process “cs00.sh” has been
exited with retcode#256
The battery has drained. Replace the battery. See
“Replacing the Battery” on
page 11-22.
Timeout waiting for ARP/RARP
packet
Network connection
problem.
Check network connection.
See
“Network Problem” on
page 4-17.
/usr/bin/ps/getexecname () has
failed
The battery has drained. Replace the battery. See
“Replacing the Battery” on
page 11-22.
TABLE 3-2 OpenBoot PROM Messages and Their Meaning (Continued)
Message Meaning What to Do