Goal

Solution

Tools Needed:

• Key for the front panel to access to the drive.
• Screw driver (if thumbscrew has been tightened).
• "host" connected via one or more of following:
• telnet access to array Firmware Application Menu through ip network.
• in-band with sccli through data path.
• out-of-band with sccli through ip network.
• serial console such as a laptop connected to the serial port.

Steps to Follow:

Step 1 - Checks and preparation.

1. Check and confirm the status of the Logical Drive is NOT Failed or Incomplete.

   From Firmware Application Main Menu:

   1. Choose "view and edit Logical drives".
   2. Under the "#FL" column, the number of failed drives is listed with the associated Logical drive.

   From command line:

   sccli -o <ip address> # via out-of-band connection
# or
sccli /dev/dsk/<c#t#d#s2> # via inband connection

sccli> show logical drives

   If the status of the Logical drive is Failed or Incomplete, or if more than one drive had failed in a RAID 5 Logical Drive, DO NOT ATTEMPT this procedure and contact Oracle Support.
2. Save the NVRAM configuration to disk for safekeeping.

   From Firmware Application Main Menu:

   1. Choose "system Functions".
   2. Then using the arrow keys to scroll down, select "Controller maintenance".
   3. Select "save NVRAM to disks".
   4. Choose "Yes" to confirm when prompted. An "NVRAM Saved" message will be displayed indicating success.
   5. After "NVRAM Saved" message has been displayed, hit escape to exit back to the main menu.

Step 2 - Locate the defective disk drive.

1. Find the SCSI Channel Number and SCSI Target ID of the disk to be replaced.

   From Firmware Application Main Menu:

   1. Select "view and edit scsi Drives".

   From command line:

   sccli -o <ip address> # via out-of-band connection
# or
sccli /dev/dsk/<c#t#d#s2> # via inband connection

sccli> show disks


   Locate the disk drive that has a status of BAD or FAILED in the status column and take note of the Channel Number, SCSI target ID and the associated Logical Drive number.

2. Physically locate the defective disk using the channel and ID numbers. Note: Failure to identify the correct disk drive might result in replacing the wrong disk drive and could cause a loss of data. Be sure that you have identified the correct disk drive.
   Additional information on ID locations can be found in 816-7326 "Sun StorEdge Array Installation, Operation and Service Manual".
3. If you are uncertain of the drive location, you can flash the LED(s) to help in identifying the disk. This method only works if there is no I/O activity.

   From Firmware Application Main Menu:

   1. Select "view and edit scsi Drives".
   2. Highlight the selected drive in question and hit return.
   3. Choose "Identifying scsi drive".
   4. Select "flash all But selected drive" to flash the activity LEDs of all the drives on this channel EXCEPT the problem drive.

Step 3 - Disk removal and replacement.

1. Unseat the failed disk identified above, let it spin down for 20 seconds and remove it from the array.
2. Install the replacement disk.
   Drive removal and installation instructions can be found in the 816-7326 "Sun StorEdge 3000 Family FRU Installation Guide".
3. Check to see if the replaced drive was automatically scanned onto the bus:

   From Firmware Application Main Menu:

   1. Select "view and edit scsi Drives".

   From command line:

   sccli -o <ip address> # via out-of-band connection
# or
sccli /dev/dsk/<c#t#d#s2> # via inband connection

sccli> show disks


   The drive status should show NEW_DRV or USED_DRV.

4. In a 3310 or 3320 array, if the replaced drive was not automatically scanned onto the bus, you may need to manually scan the replacement disk into the configuration. (This does not apply to 3510 and 3511 arrays)

   From Firmware Application Main Menu:

   1. Select "view and edit scsi Drives".
   2. Select any disk in the list, then select "Scan scsi drive".
   3. Select the SCSI Channel Number, then the SCSI Target ID of the replaced disk drive, and confirm "Yes" when prompted.

Step 4 - Decide how the newly replaced drive should be configured.

• RAID 1 or 5, with global or local spare, please proceed to Step 5A.
• RAID 1 or 5, without global or local spare, please proceed to Step 5B.
• RAID 0 or NRAID, please proceed to Step 5C.

Step 5A - Logical Drive in RAID 1 or 5 with Global/Local Spare.

• The newly replaced drive may be assigned as a new local or global spare. See Step 5A-AsSpare.
• The newly replaced drive may be re-integrated into the Logical Drive. See Step 5A-Reintegrate.

Step 5A-AsSpare - Assign the newly replaced drive as a local or global spare.

From Firmware Application Main Menu:

1. Select "view and edit scsi Drives".
2. Select the newly replaced disk drive.
3. Select "add Global spare drive", or "add Local spare drive" and confirm yes when prompted.

From command line:

Step 5A-Reintegrate - Re-integrate the newly replaced disk back into the RAID 1 or 5 Logical Drive.

1. Identify the previous spare disk which is now part of the Logical Drive and is going to be removed in favour of the newly replaced disk.

   From Firmware Application Main Menu:

   1. Select "view and edit Logical drives".
   2. Select the target Logical Drive, then "copy and replace drive".
   3. Select the previous spare drive, then select the replaced disk drive, confirm "yes" when prompted.

   (There is no sccli command line equivalent for "copy and replace drive".)

2. Wait for the copy and replace to complete.
3. Configure the original spare disk back to a local or global spare

Step 5B - Logical Drive in RAID 1 or 5 with no Global/Local Spare.

• To rebuild Logical Drive in RAID 1, refer to <>.
• To rebuild Logical Drive in RAID 5, refer to <>.

Step 5C - Logical Drive in RAID 0 or NRAID.

Previously Published As
78432

Change History

Date: 2010-08-04
User Name: VickieWilliams-Eli

Action: Approved
Comment: Please review.
Version: 0
Product_uuid
3db30178-43d7-4d85-8bbe-551c33040f0d|Sun StorageTek 3310 SCSI Array
58553d0e-11f4-11d7-9b05-ad24fcfd42fa|Sun StorageTek 3510 FC Array

This solution has no attachment