How To Replace A Disk In a Sun Storage 3510 FC JBOD.

Asset ID:	1-71-1001837.1
Update Date:	2017-10-05
Keywords:

Solution Type Technical Instruction Sure

Solution 1001837.1 : How To Replace A Disk In a Sun Storage 3510 FC JBOD.

Applies to:

Sun Storage 3510 FC Array - Version Not Applicable and later
All Platforms

Goal

This document explains how to replace a failed disk in a Sun Storage 3510 FC JBOD (Just a Bunch of Disks) array. This document applies ONLY to the jbod configuration of the array.

Solution

For a full list of 3510 FC array supported configurations, see

Sun StorEdge 3510 FC and 3511 SATA Array Release Notes
Sun StorEdge 3000 Family Installation, Operation, and Service Manual (Appendix B: Using a Standalone 3510 JBOD Array)

The Sun StorEdge 3510 JBOD Expansion unit is supported as a single (standalone) array configuration.

Support for volume servers only: 220R, 250, 420R, 450, V120, V280, and V880
Support for Solaris 8, 9 and 10 Operating Systems only
Support for Veritas Volume Manager (VxVm) 3.5, 4.0, 4.1, 5.0 and up.
Support for Solaris Volume Manager (SVM) and Solstice Disksuite (SDS)
Multi-pathing between server and single array via VxVM DMP only (no MPxIO support)
No daisy-chaining of JBODs. A single JBOD connected to single or dual FC 2Gb HBAs only
No hub or switch between server and JBOD
Data only, no booting from a FC JBOD
No cluster support, neither VCS nor Sun Cluster
Consider installing Sun StorEdge SAN 4.4.x, <Patch 10297699> as this contains all the latest drivers for this configuration.

Disk Replacement.

Offline the drive and remove the device links. In this example, we use luxadm and devfsadm to remove c1t27d0 from the 3510 jbod.

# luxadm -e offline /dev/rdsk/c1t27d0s2
# devfsadm -Cv
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s0
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s1
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s2
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s3
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s4
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s5
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s6
   devfsadm[16521]: verbose: removing file: /dev/rdsk/c1t27d0s7
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s0
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s1
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s2
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s3
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s4
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s5
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s6
   devfsadm[16521]: verbose: removing file: /dev/dsk/c1t27d0s7

Replace the disk. Use <Document 1007692.1> Sun Storage 3510 and 3511 Arrays: How to Identify Switch IDs, Disk IDs and Correct Backend Cabling to help locate the drive.
Use devfsadm to discover the drive and create the new device links.

# devfsadm -cV
# luxadm probe
Found Fibre Channel device(s):
Node WWN:20000004cf26d924 Device Type:Disk device
    Logical Path:/dev/rdsk/c1t16d0s2
Node WWN:.........................................
    Logical Path:/dev/rdsk/c1txxdxs2
Node WWN:20000004cf24b7a2 Device Type:Disk device
    Logical Path:/dev/rdsk/c1t27d0s2

If the disk does not show up, you can try a reconfiguration reboot.
If downtime is not possible, contact Oracle Support for further approaches to the problem.

Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

Attachments

This solution has no attachment