Sun Netra 1280 Server
 
Sun Fire E2900 Server
 
Sun Fire V1280 Server
 
Sun Netra 1290 Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Exx00
 
_Old GCS Categories>Sun Microsystems>Servers>Entry-Level Servers
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange V and Netra Servers
 

Applies to:

Purpose

 Troubleshooting OS Installation Failure "cannot mount root" on Sun Fire[TM] v1280/E2900 and Netra[TM] n1280/n1290

Troubleshooting Steps

In order to provide the most accurate fix, we need to validate that each statement under the symptoms below are true for your environment.


Symptoms

 

• The operating System (OS) is attempting to be installed on a disk.
• The procedure can result in a continuous panic reboot of the system in question.
• It may be required to issue a setkeyswitch off and then on to get the system to stop a panic reboot cycle.

The procedure may result in errors such as the following:

  

 

System Type and Configuration

While the examples in this document were obtained from a Sun Fire[TM] E2900, this document can be used to troubleshoot the same issue on Sun Fire V1280, Netra 1280 or Netra1290 systems as well.

The following assumptions are made at the very beginning of this troubleshooting document:

• The system is able to get to the ok prompt.
• The system can boot from the DVD/cdrom image to single user mode.
• All internal disks (including desired boot disk) are visible in format in single user mode.
• Solaris[TM] 9 9/05,  Solaris 10[TM] 1/06 or latest Solaris 10[TM] update is attempting to be installed on this system.

Steps to Follow
The listed troubleshooting steps are ordered in the most appropriate sequence to isolate the issue and be certain about the related fix.

Please do not skip a step.
1. Verify this is not a known issue with a "mpt" driver patch.

     Reference Sun Alert 1000804.1 Certain Solaris 9 and 10 "mpt" Driver Patches may Cause a System Panic on Reboot or Fail to Recognize Drives

2. Verify this is not a known issue with Solaris 9 9/05 and PCI+ IB_SSC assemblies.     If booting from Solaris 10, proceed to the next step in this document.

    Reference: Doc ID 1004227.1 E2900/V1280 systems that have the PCI+ IB_SSC IO Assembly will not be able to install or boot from Solaris [TM] 9 Operating System 9/05 DVD or CD

    Reference Field Action Bulletin Document: 1000952.1 E2900/V1280 systems that have the PCI+ IB_SSC IO Assembly will not be able to install or boot from Solaris 9 9/05 DVD or CD

3. Verify this is not resolved by installing the latest Solaris 10 update if practical.

4. Verify that errors relating to a defective disk drive have not been encountered.

    The following error example indicates a potentially defective disk drive:

  

 

    If errors like those shown above are seen on the primary boot disk, attempt to boot off an alternate disk drive to be sure whether the disk is defective or the drive bay, media tray, or any cables or components attached on this device path.

5. Verify that the error messages from a failed boot attempt can be captured and open a MOS Service Request.




Solaris 9 9/05 Information


If the Solaris 10 latest update installation completes
successfully (Step 3 in main document body), but Solaris 9 09/05
still fails with the same panic string and the customer insists on
using Solaris 9[TM] 09/05 then follow the procedure shown below to
correct the situation:

   1.  Go to internal website ftp://figaro.us.oracle.com/pub/dvd0_special/
   and locate the Solaris 9 Update 8 ISO image.

   2.  Download and the burn the Solaris 9 Update 8
   ISO image from figaro onto a CD/DVD.

   3.  Ensure that the checksum is checked after the
   image is burned on the DVD/CD

   4.  Boot from the downloaded ISO image and then feed the
   Solaris 9 Update 5 Installation media so that Update 5 is
   installed but making use of the requisite driver's from the
   Update 8 ISO image.

   Note:  New versions of the S9U5 media should not have any issues,
   but some older versions still exist and have this specific issue.


 

References

This solution has no attachment