How to replace and assign the new drive in the same location as the failed disk in a raid1 logical drive in Sun StorEdge[TM] 3000 ?

Asset ID:	1-71-1009268.1
Update Date:	2009-12-05
Keywords:

Solution Type Technical Instruction Sure

Solution 1009268.1 : How to replace and assign the new drive in the same location as the failed disk in a raid1 logical drive in Sun StorEdge[TM] 3000 ?

Related Items


Sun Storage 3510 FC Array
 Sun Storage 3310 Array
 Sun Storage 3511 SATA Array
 Sun Storage 3320 SCSI Array

Related Categories


GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays

PreviouslyPublishedAs
212828

Description
This document can be used if there is a failed disk in a RAID 1 logical drive that has a hot spare that replaced the failed HDD.

Steps to Follow
How to replace and assign the new drive in the same location as the failed disk in a raid1 logical drive in Sun StorEdge[TM] 3000 ?

1- Replace the failed HDD.

2- Connect to the Sun StorEdge[TM] 351x/33x0 Array by a serial connection or telnet.

3- Go to view and edit SCSI drives menu and select the new drive, then select to add it as a local spare for the RAID 1 drive or as global spare.

4- Physically remove the disk that was the hot spare and replaced the failed disk.

5- Check that the removed disk is show as BAD and the status of the new disk is not STAND-BY .

The SCSI drives should look like the image within Figure 1.

6- Insert the removed hot spare disk to its place back.

The SCSI drives should look like the image within Figure 2.

The disk is showed as USED DRV due to the roaming disks proberty in the SE3x10.

7- Select the USED DRV disk and add it as a local or global hot spare as it was before the disk failed.

Refer to Figure 3.

Product
Sun StorageTek 3310 SCSI Array
Sun StorageTek 3510 FC Array
Sun StorageTek 3511 SATA Array
Sun StorageTek 3320 SCSI Array

se3310, se3510, se3x10, minnow, se3320, se3511, disk, 3310, 3320, 3510, 3511
Previously Published As
77792

Change History
Date: 2008-01-08
User Name: 95826
Action: Update Canceled
Comment: *** Restored Published Content *** canceling update to allow migration to IBIS
Version: 0
Date: 2008-01-08
User Name: 95826
Action: Reassign
Comment: reassigning document to release it in order to allow migration to IBIS
Version: 0

Attachments

This solution has no attachment