Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1395234.1
Update Date:2018-05-17
Keywords:
Solution Type  Technical Instruction Sure

Solution  1395234.1 :   How to replace an internal disk in a volume under LSI RAID controller  

Related Items 
    

  • Sun SPARC Enterprise T5120 Server
    •  
  • Sun SPARC Enterprise T5220 Server
    •  
  • Sun SPARC Enterprise T5220 Server
    •  
  • Sun SPARC Enterprise T5120 Server
    •  
Related Categories 
    

  • PLA-Support>Sun Systems>SPARC>Usx/Blade/Netra>SN-SPARC: USx
    •  
  • _Old GCS Categories>Sun Microsystems>Servers>CMT Servers
    •  




Replacing an internal disk of the on-board raid volume is simple, but it requires attention ensuring completion of each step.

Applies to:

Sun SPARC Enterprise T5120 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise T5220 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun SPARC Enterprise T5120 Server
Sun SPARC Enterprise T5220 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

To assist customers and technicians on replacing internal disks that are part of a RAID volume.

Solution

1. Once a volume failure has been identified, list its disks via 'raidctl' in order to identify the failed disk. 

root@Server-T5120 # raidctl
Controller: 1
  Volume:c1t0d0
    Disk: 0.0.0
    Disk: 0.1.0

root@Server-T5120 # raidctl -l c1t0d0
Volume                  Size    Stripe  Status   Cache  RAID
       Sub                     Size                    Level
               Disk
----------------------------------------------------------------
c1t0d0                 136.6G   N/A     DEGRADED  OFF  RAID1
               0.0.0  136.6G           GOOD
                 N/A  136.6G           FAILED

2. Locate the defective disk in the chassis following Server's specific documentation. Pay careful attention. Removing the incorrect disk may result in a total loss of the volume. 

Please keep in mind, when there are no raid volumes, the sas addressing (persistent mapping: enabled, physical mapping type: direct attach) is as follow:

- c.id.l hdd
  0.0.0  0
  0.1.0  1

and if there are raid volumes, the sas addressing might change and there is no direct relationship between the c.id.l (target) and hdd location, for more information look at below doc:

- Troubleshooting guide to find the faulty disk in a Raid Volume for systems who contains LSI 1064/1064E/1068/1068E SAS Controller (Doc ID 1499897.1)

3. Remove the defective disk.

4. Make sure the removal of the disk has been acknowledged by Solaris checking '/var/adm/messages' for reports on the removal of the disk.

Jan 16 15:30:41 Server-T5120 scsi: [ID 107833 kern.notice] /pci@0/pci@0/pci@2/scsi@0 (mpt0):
Jan 16 15:30:41 Server-T5120 Physical disk (target 1) is |missing|
Jan 16 15:30:41 Server-T5120 scsi: [ID 107833 kern.notice] /pci@0/pci@0/pci@2/scsi@0 (mpt0):
Jan 16 15:30:41 Server-T5120 Physical disk (target 1) is |out of sync||missing|
Jan 16 15:30:41 Server-T5120 scsi: [ID 107833 kern.notice] /pci@0/pci@0/pci@2/scsi@0 (mpt0):
Jan 16 15:30:41 Server-T5120 Volume 0 is |enabled||degraded|

Jan 16 15:30:55 Server-T5120 ipmievd: [ID 702911 daemon.notice] Entity Presence sensor #0x1f /HDD1/PRSNT - Device Absent
Jan 16 15:31:04 Server-T5120 SC Alert: [ID 928961 daemon.notice] IPMI | minor: ID = 1 : 01/16/2012 : 17:30:53 : Entity Presence : /HDD1/PRSNT : Device Absent
Jan 16 15:31:13 Server-T5120 SC Alert: [ID 940327 daemon.error] Chassis | major: Hot removal of HDD1

Notice both Solaris and ipmi/SC logs are printed and please keep in mind that "Physical disk (target x)" doesn't always point to the hdd location

5. Following that, insert the new disk. See the volume resync started.

Jan 16 16:30:55 Server-T5120 ipmievd: [ID 702911 daemon.notice] Entity Presence sensor #0x1f /HDD1/PRSNT - Device Present
Jan 16 16:31:04 Server-T5120 SC Alert: [ID 928961 daemon.notice] IPMI | minor: ID = 1 : 01/16/2012 : 18:30:53 : Entity Presence : /HDD1/PRSNT : Device Present
Jan 16 16:31:13 Server-T5120 SC Alert: [ID 940327 daemon.error] Chassis | major: Hot insertion of HDD1

Jan 16 16:30:41 Server-T5120 scsi: [ID 107833 kern.notice] /pci@0/pci@0/pci@2/scsi@0 (mpt0):
Jan 16 16:30:41 Server-T5120 Physical disk (target 1) is |online|
Jan 16 16:30:41 Server-T5120 scsi: [ID 107833 kern.notice] /pci@0/pci@0/pci@2/scsi@0 (mpt0):
Jan 16 16:30:41 Server-T5120 Physical disk (target 1) is |out of sync||online|
Jan 16 16:30:41 Server-T5120 scsi: [ID 107833 kern.notice] /pci@0/pci@0/pci@2/scsi@0 (mpt0):
Jan 16 16:30:41 Server-T5120 Volume 0 is |enabled||resyncing||optimal|
Jan 16 16:30:41 Server-T5120 scsi: [ID 107833 kern.notice] /pci@0/pci@0/pci@2/scsi@0 (mpt0):
Jan 16 16:30:41 Server-T5120 Volume 0 is |enabled||optimal|

Notice both Solaris and ipmi/SC logs are printed and please keep in mind that "Physical disk (target x)" doesn't always point to the hdd location

6. Follow the resync process until confirmed its completion.

root@Server-T5120 # raidctl
Controller: 1
  Volume:c1t0d0
    Disk: 0.0.0
    Disk: 0.1.0

root@Server-T5120 # raidctl -l c1t0d0
Volume                  Size    Stripe  Status   Cache  RAID
       Sub                     Size                    Level
              Disk
----------------------------------------------------------------
c1t0d0                 136.6G   N/A     SYNC     OFF  RAID1
               0.0.0  136.6G           GOOD
               0.1.0  136.6G           GOOD

root@Server-T5120 # raidctl -l c1t0d0
Volume                  Size    Stripe  Status   Cache  RAID
       Sub                     Size                    Level
               Disk
----------------------------------------------------------------
c1t0d0                 136.6G   N/A     OPTIMAL  OFF  RAID1
               0.0.0  136.6G           GOOD
               0.1.0  136.6G           GOOD

Attachments 
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback