Sun Fire T2000 Server
 
Sun Fire T1000 Server
 

GCS>Sun Microsystems>Servers>CMT Servers
 

Examples of the error messages (can be seen on the console or /var/adm/messages):

Example #1:

Aug  1 08:05:23 crdww502 scsi: /pci@780/pci@0/pci@9/scsi@0 (mpt0):
Aug  1 08:05:23 crdww502        mpt0: unknown event 16 received
..........................

Example #2:

# raidctl -c c1t2d0 c1t3d0
Creating RAID volume c1t2d0 will destroy all data on member disks, proceed (yes/no)  Yes
config_change_state: Bad address

Example #3:

Boot device:
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@0,0:a  File and args: -r
SunOS Release 5.10 Version Generic_118822-30 64-bit
Copyright 1983-2005 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
WARNING: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0 (sd0):
Corrupt label - bad geometry

Cannot mount root on
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@0,0:a fstype ufs
panic[cpu0]/thread=180e000: vfs_mountroot: cannot mount root  

Please validate that each troubleshooting step below is true for your environment. 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 Hardware RAID is enabled on the server by checking the system configuration and required patch levels (to avoid errors seen in example #1 and example #2).  Refer to <Document: 1012950.1> : Enabling Hardware RAID on Sun Fire[TM] T1000/T2000.

2. Verify proper procedure and commands being used for configuring the RAID volumes. Refer to Managing Disk Volumes in the Sun Fire T1000 Administration Guide, Sun Fire T2000 Administration Guide, and <Document: 1009346.1> : Hardware RAID usage on the Sun Fire[TM] T2000.

3. Ensure that after RAID volume creation, a valid Solaris label is applied so that the new volume can be recognized correctly by the OS (to avoid errors, such as shown in  example #3).

Due to the volume initialization that occurs on the disk controller when a new volume is created, properties of the volume such as geometry and size are unknown. RAID volumes created using the hardware controller must be configured and labeled using prior to use with the Solaris Operating System. For detailed steps refer to To Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System and to <Document: 1002561.1> : Labeling volumes and drives when working with Sun Fire[TM] T2000 RAID. When creating a volume (IM or IS) containing the default boot drive, ensure that  the volume is configured and labeled using the 'format' utility, prior to installing Solaris OS. Due to this limitation, 'raidctl' blocks the creation of a hardware RAID volume if any of the member disks currently have a file system mounted.

4. In case of a problem, verify the RAID volume status and the DISK status, using the 'raidctl' command:

# raidctl -l
Controller: 0
        Volume:c0t2d0
        Disk: 0.0.0
        Disk: 0.1.0
        Disk: 0.2.0
        Disk: 0.3.0

# raidctl -l 0
Controller      Type            Version
----------------------------------------------------------------
c0              LSI_1064EE      1.09.00.00

# raidctl -l c0t2d0
Volume                  Size    Stripe  Status   Cache  RAID
        Sub                     Size                    Level
                Disk
----------------------------------------------------------------
c0t2d0                  68.2G   N/A     SYNC     OFF    RAID1
                0.3.0   68.2G           GOOD
                0.2.0   68.2G           GOOD

The volume (RAID) status can be:

The Disk status can be:

Refer to the Sun Fire T1000/T2000 Administration Guides at the provided links for more details:

Sun Fire T1000 Administration Guide (Managing Disk Volumes)

Sun Fire T2000 Administration Guide (Managing Disk Volumes)

Note: During a RAID volume creation, any disk that is part of the volume  looses  the last 64MB of it's disk capacity. This disk space is used by the LSI1064 controller firmware to store the RAID configuration information (meta data). This will result in the loss of existing data.

Note for IM (integrated mirror) raid volumes:

The disk controller synchronizes IM volumes one at a time.  If you create a second IM volume before the first IM volume completes its synchronization, the first volume's RAID status will indicate RESYNCING, and the second volume's RAID status will indicate OK. Once the first volume has completed, its RAID status changes to OK, and the second volume automatically starts synchronizing (status of RESYNCING).

At this point, if the customer has validated that each troubleshooting step above is true for their environment, and the issue still exists, further troubleshooting is required.  Gather the needed data from 'format', 'iostat', 'raidctl' and error messages, or if possible by running explorer -w default,Tx000.  See <Document: 1018946.1> : Using Sun[TM] Explorer on the Tx000 Series Systems. For additional support contact My Oracle Support .

 Gather the needed data from 'format', 'iostat',
'raidctl' and console error messages, or if possible by
running
explorer -w
default,Tx000. See <Document: 1018946.1> : Using Sun[TM] Explorer on the Tx000 Series Systems. 

REFERENCES:

Sun Fire T1000 platform-specific patches

Sun Fire T2000 platform-specific patches

Sun Fire T1000 Administration Guide (Managing Disk
Volumes)

Sun Fire T2000 Administration Guide (Managing Disk
Volumes)

<Document: 1009346.1> : Hardware RAID usage on the Sun Fire[TM] T2000

<Document: 1002561.1> : Labeling volumes and drives when working with Sun Fire[TM] T2000 RAID

<Document: 1008139.1> : How to delete a RAID volume on the Sun Fire[TM] T2000 at the OBP level

This document contains normalized content and is managed by the the Domain Lead
(s) of the respective domains. To notify content owners of a knowledge gap 
contained in this document, and/or prior to updating this document, please 
contact the domain engineers that are managing this document via the “Document 
Feedback” alias(es) listed below:

Domain Lead: [email protected]
Feedback Alias: [email protected]

This solution has no attachment