Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1011671.1
Update Date:2010-08-10
Keywords:

Solution Type  Technical Instruction Sure

Solution  1011671.1 :   Procedure to Relocate a Disk from One Sun StorEdge[TM] A3x00/A1000 Array to Another  


Related Items
  • Sun SPARCstorage RSM Array 2000
  •  
  • Sun Storage A3000 Array
  •  
  • Sun Storage A1000 Array
  •  
  • Sun Storage A3500 SCSI Array
  •  
  • Sun Netra st A1000 Array
  •  
  • Sun Storage A3500 FC Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - Other
  •  

PreviouslyPublishedAs
215998


Description
Moving disks between A3x00/A1000 arrays without following correct procedures is likely to create problems and may even destroy data. This document attempts to describe processes to minimize the possibility of problems when moving drives between these arrays.

Steps to Follow
Note: This procedure will destroy any data on the disk being moved.
Note: The functionality to relocate a disk was not designed into this product.These arrays were designed to have a set of disks which never get removed but only added to, so this procedure is not always 'clean', and instead of deleting the removed disk from the original array, the Raid Manager 6 GUI (RM6) may list the disk as "not responsive".
Note: Because the rm6 config is stored on the disks, you MUST pull the disk from the original array and install it into the new array HOT (i.e. the arrays are fully powered up).
Note: It is strongly recommended that you update the Raid Manager software, drive firmware, and array controller firmware and NVSRAM to the most recent revisions before attempting this procedure.


1- Make sure that the disk is not used by any LUN. If it is a member of a LUN, that LUN must be deleted first.
2- Locate the correct disk by using the rm6 GUI if necessary. Bring up the configuration GUI and select the "Unused" pool to flash the disk lights.
3- Pull the disk out of the array. With RM6 rev 6.1.1 update 1 and above, if the disk was unused, the controller should eventually recognize that the disk was removed and delete it from the GUI.
4- Insert the disk in the new array. Remember you must do this with the array powered up.
5- Allow time for the drive to spin up (approximately 30 seconds). When the disk spins up, the array controller will recognize it and add it to the unused pool. You can watch this happen in the RM6 configuration GUI.
6- Run a health check to insure that the drive is not defective.
In the RM6 GUI,
1) Choose Status
2) Select the RAID Module
3) Click Health Check
4) If the health results are not Optimal, click on Show Details
7- On arrays running older firmware or older versions of RM6, potential issues exist which require additional steps in the procedure. These steps are not required if you are using Raid Manager 6.22.1 and all drive and controller firmwares are at the latest revisions. Using the drivutil command or the manual recovery functions in the RM6 GUI, manually fail the drive then revive the drive to update DacStore (the configuration region) on the drive. In the RM6 GUI,
1) Choose Recovery
2) Select the RAID Module
3) Click Options->Manual Recovery->Drives
4) Highlight the drive you just installed
5) Click Fail, then OK
6) Click Options->Manual Recovery->Drives
7) Highlight the drive just installed
8) Click Reconstruct, then OK



Product
Sun StorageTek A3500 Array
Netra st A1000 Array
SPARCstorage RSM Array 2000
Sun StorEdge A1000 Array
Sun StorageTek A3500 FC Array
Sun StorageTek A3000

Internal Comments
For the internal use of Sun employee's.

Reference < Solution: 200114 > RM6 may detect a non-existent 2MB dacstore on factory formatted hard disk drives

for more information about the issues related to step 7.
A1000, A3000, A3500, RSM2000, RSM 2000, sonoma
Previously Published As
21312

Change History
E-mailed author concerning FINs I0782 as well as Sun[TM] Alert 23762. These two
references seem to no longer exist in our database.

Date: 2005-05-19
User Name: 7058
Action: Approved
Comment: Proper trademarking was added to title. Rest of doc OK.
Updated review date.
Republishing.
Version: 3
Date: 2005-05-18
User Name: 7058
Action: Accept
Comment:
Version: 0

Date: 2009-12-09
User: DeCotis
Comment: Updated Title, Product List, and Internal section to reference the IBIS article ID's.

Attachments

This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback