Sun SPARC Enterprise T5440 Server
 
Sun Fire T2000 Server
 
Sun SPARC Enterprise T5240 Server
 
Sun SPARC Enterprise T5220 Server
 
Sun SPARC Enterprise T2000 Server
 
Sun Fire T1000 Server
 
Sun SPARC Enterprise T5140 Server
 
Sun Netra T2000 Server
 
Sun SPARC Enterprise T5120 Server
 

GCS>Sun Microsystems>Servers>NEBS-Certified Servers
 
GCS>Sun Microsystems>Servers>CMT Servers
 

Applies to:

Purpose

Last Review Date

Instructions for the Reader

Troubleshooting Details

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. This troubleshooting document assumes that a RAID volume has been successfully configured and previously operational. For more details on how to create a RAID volume refer to <Document 1009722.1>  Creating a RAID volume on a Sun Fire[TM] T1000/T2000 and the Sun Fire T1000/T2000 Administration Guides:

Sun Fire T1000 Administration Guide (Managing Disk Volumes)

Sun Fire T2000 Administration Guide (Managing Disk Volumes)

2. Remove all internal disks prior to installing the replacement board (card), install the replacement board, check for and delete any old raid data stored in the RAID disk controller (on the replacement board), and then reinsert the disks.

Note: The replacement board may contain old configuration data on the LSI (RAID) controller that will potentially overwrite any RAID data stored on disks breaking the customers configuration.  To ensure that the correct data is picked up from the disks, you should remove all disks, install the new board, select the LSI disk controller path, check for and delete any old raid volumes, as it may corrupt the existing RAID volume(s), then reinsert the drives from the existing volume.

Set the following NVRAM parameters:

{0} ok  setenv auto-boot? False
{0} ok  setenv fcode-debug? True
{0} ok  reset-all

Select the path to the disk controller (disk node)

For T1000 (dual-disk configuration is necessary for RAID) the path is:

{0} ok select /pci@7c0/pci@0/pci@8/scsi@2

For T2000 with part (model) number 501-6843 using the PCI-X SAS card:

{0} ok select /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2

For T2000 with part (model) number 501-7501 using the onboard 1064 controller:

{0} ok select /pci@780/pci@0/pci@9/scsi@0

{0} ok show-volumes (look for any existing old volumes on replacement board/card)
{0} ok X delete-volume (X is the volume number)
{0} ok show-volumes (ensure that old volume data is deleted)
{0} ok unselect-dev
{0} ok reset-all

Fore more details also refer to <Document 1008139.1> How to delete a RAID volume on the Sun Fire[TM] T2000 at the OBP level.

Re-insert the drives and power cycle the system.

3. In order to reactivate the pre-existing volume after the RAID controller for internal disks is replaced,  the LSI/OBP command 'activate-volume' is required.

Note: When you remove/replace the systemboard or the SAS PCI-X card (for older T2000 systems) the RAID volume will be deactivated.  The reason why the volume goes inactive after replacing the board/card is that the new WWID on the new board  doesn't match the volume configuration (meta) data on the drives and there is no record of the volume in the card's meta data.

Select the path to the disk controller (disk node)

For T1000 (dual-disk configuration) the path is:

{0} ok select /pci@7c0/pci@0/pci@8/scsi@2

for T2000 with part (model) number 501-6843 using the PCI-X SAS card:

{0} ok select /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2

for T2000 with part (model) number 501-7501 using the onboard 1064 controller:

{0} ok select /pci@780/pci@0/pci@9/scsi@0

{0} ok show-volumes ( look for the inactive volume)
{0} ok X activate-volume (X is the volume number)

Example:

{0} ok select /pci@780/pci@0/pci@9/scsi@0 
{0} ok show-volumes 
Volume 0 Target 2  Type IM (Integrated Mirroring) 
Optimal  Enabled   Inactive      2 Members      143112591 Blocks, 73 GB 

.....................

{0} ok 0 activate-volume 
Volume 0 is now activated 

{0} ok unselect-dev
{0} ok probe-scsi-all (to check for disks)
{0} ok reset-all

Restore the NVRAM settings for normal operation:

{0} ok setenv auto-boot? True
{0} ok setenv fcode-debug? False
{0} ok reset-all

Note: The above is assuming there is only a single volume in use, this should be adapted depending on the customers configuration.

For details also reference <Document 1007005.1> How to activate a RAID volume on Sun Fire[TM] T2000

4. Volume migration (relocating all RAID volume disk members from one Sun Fire T2000 chassis to another) is not supported.

This is because the RAID volume configuration data is stored in several places - on the controller card in NVRAM and on the data area of drives that are part of the volumes. See also <Document 1009722.1> Creating a RAID volume on a Sun Fire T1000/T2000.

At this point, if you have validated that each troubleshooting step above is true for your 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 Explorer on the Tx000 Series Systems. For additional support contact My Oracle Support.

This solution has no attachment