Sun Fire E6900 Server
 
Sun Fire 3800 Server
 
Sun Fire 6800 Server
 
Sun Fire E4900 Server
 
Sun Netra 1280 Server
 
Sun Fire 4800 Server
 
Sun Fire E2900 Server
 
Sun Fire V1280 Server
 
Sun Fire 4810 Server
 
Sun Netra 1290 Server
 

GCS>Sun Microsystems>Servers>Midrange V and Netra Servers
 
GCS>Sun Microsystems>Servers>Entry-Level Servers
 
GCS>Sun Microsystems>Servers>Midrange Servers
 

Symptoms:

• The system is attempting to boot off of a hard disk drive but hangs or errors out
• System hangs during the boot process
• System has power but nothing is seen on the console

Sun Shared Shell

If you require assistance in collecting the data recommended in this article or require help in diagnosing a system issue, there is a collaborative service tool called Sun Shared Shell which allows Sun Service engineers to remotely view and diagnose customer's systems. Consider using this option to reduce the problem resolution time.

The steps will provide instructions or a link to a document, for validating the step and taking corrective action  as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

1.  Verify that the system console is working

• Reference <Document: 1011930.1> Sun Fire[TM] (3800-6800) System Controller Application (ScApp) How To's  

2.  For troubleshooting purposes, verify that the OBP parameter   auto-boot   is set to false.

• Once issue has been resolved be sure to change parameter back to its original value.

3.  Verify that we are able to reach the OBP ( ok>  prompt)

• Reference <Document: 1003150.1>  Sun Fire[TM] (3800-6900): Navigating Between Shells on Sun Fire Mid-range Servers   

4.  Verify that the system is not receiving one of the following errors:

     ERROR: Can't open boot-device
Boot device is unknown
Error: improper device path

• Reference <Document: 1004094.1>  Troubleshooting disk boot problems from the OBP (?ok>? prompt) 

5. Verify that the system is not receiving one of the following errors:

     Time out waiting for arp/rarp
Can't open kernel/unix
Can't mount/usr
Cannot create /var/adm/utmp or /utmpx 

• Reference <Document: 1011943.1>  Local Boot Issues, Errors and Resolutions 

6. V erify that the system is not receiving the following error:

     File just loaded does not appear to be executable

• Reference <Document: 1004422.1>  Recovering from a corrupt bootblock/ufsboot: "the file just loaded does not appear to be executable"

7. Verify another boot attempt while capturing console data.

• Reference <Document: 1004222.1>  How to setup console logging and obtain diagnostic data from different types of SPARC servers   

8. If system has a mirrored boot disk, verify that a boot attempt from the mirrored boot disk fails

• Reference <Document: 1005712.1>  Solstice DiskSuite[TM] software - Unable to boot from a DiskSuite-controlled system disk 
• Reference <Document: 1003238.1>  Full and Basic/Functional Unencapsulation of a Volume Manager Encapsulated Root Disk 

9. Verify that the system is  able to boot  to single user from cdrom or from the network.

• Reference <Document: 1009194.1>  Sun Fire[TM] F3800, v1280, E2900, F4800, E4900, F6800 and E6900: Can't boot from cdrom  

10. Booted from cdrom or from the net, verify that format is able to recognize the boot disk

• Reference the format man page for command information

11. Collaborate with the next level of technical support.  

• Collect the following data and collaborate:
• printenv ouput
  
• devalias output
  
• probe-scsi-all output
  
• console data from step 8
• show-disks output

This solution has no attachment