Maintaining Storage Arrays

This section contains the procedures for maintaining a storage array. The following table list these procedures.

Table 1-1 Task Map: Maintaining a Storage Array

How to Add a Disk Drive

Use this procedure to add a disk drive to a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster system administration documentation and your server hardware manual. Example--Adding a Disk Drive shows how to apply this procedure.

For conceptual information on quorum, quorum devices, global devices, and device IDs, see your Sun Cluster concepts documentation.

1. Locate an empty disk slot in the storage array for the disk drive you are adding.

   Identify the disk slot in the storage array for the disk drive that you are adding and note the target number. See the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual or the Netra st A1000/D1000 Installation and Maintenance Manual.

2. Install the disk drive.

   For the procedure on installing a disk drive, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual or theNetra st A1000/D1000 Installation and Maintenance Manual and the Netra st A1000/D1000 Product Notes.

3. On all nodes that are attached to the storage array, configure the disk drive.

   # cfgadm -c configure cN # devfsadm

4. On all nodes, verify that entries for the disk drive have been added to the /dev/rdsk directory.

   # ls -l /dev/rdsk

5. If necessary, use the format(1M) command or the fmthard(1M) command to partition the disk drive.

6. From any node, update the global device namespace.

   If a volume management daemon such as vold is running on your node, and you have a CD-ROM drive that is connected to the node, a device busy error might be returned even if no disk is in the drive. This error is an expected behavior.

   # scgdevs

7. On all nodes, verify that a device ID (DID) has been assigned to the disk drive.

   # scdidadm -l

   ---

   Note - As Example--Adding a Disk Drive shows, DID 35, which is assigned to the new disk drive, might not be in sequential order in the storage array.

   ---

8. Perform volume management administration to add the new disk drive to the configuration.

   For more information, see your Solstice DiskSuite™ or VERITAS Volume Manager documentation.

Example--Adding a Disk Drive

The following example shows how to apply the procedure for adding a disk drive in a storage array.

# scdidadm -l
16       phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16    
17       phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17    
18       phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18    
19       phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19    
...
26       phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26    
30       phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30    
31       phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31    
32       phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32    
33       phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33    
34       phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34    
8190     phys-circinus-3:/dev/rmt/0     /dev/did/rmt/2
# cfgadm -c configure c1 
# devfsadm
# scgdevs
Configuring DID devices
Could not open /dev/rdsk/c0t6d0s2 to verify device id.
        Device busy
Configuring the /dev/global directory (global devices)
obtaining access to all attached disks
reservation program successfully exiting
# scdidadm -l
16       phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16    
17       phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17    
18       phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18    
19       phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19    
...
26       phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26    
30       phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30    
31       phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31    
32       phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32    
33       phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33    
34       phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34    
35       phys-circinus-3:/dev/rdsk/c2t13d0 /dev/did/rdsk/d35    
8190     phys-circinus-3:/dev/rmt/0     /dev/did/rmt/2       

Where to Go From Here

To configure a disk drive as a quorum device, see your Sun Cluster system administration documentation for the procedure on adding a quorum device.

How to Replace a Disk Drive

Use this procedure to replace a disk drive in a storage array. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster system administration documentation and your server hardware manual. Use the procedures in your server hardware manual to identify a failed disk drive.

For conceptual information on quorum, quorum devices, global devices, and device IDs, see your Sun Cluster concepts documentation.

1. Identify the failed disk drive.

   # scdidadm -o diskid -l cNtXdY

2. Determine if the disk drive you want to replace is a quorum device.

   # scstat -q

   • If the disk is not a quorum device, skip this step.

   • If the disk drive you want to replace is a quorum device, add a new quorum device on a different storage device and remove the old quorum device.

     For the procedure on how to add and remove a quorum device, see your Sun Cluster system administration documentation.

3. If possible, back up the metadevice or volume.

   For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.

4. If you are using Solstice DiskSuite/Solaris Volume Manager as your volume manager, save the disk partitioning for use when you partition the new disk drive.

   # prtvtoc /dev/rdsk/cNtXdYsZ > filename

   ---

   Note - Do not save this file under /tmp because you will lose this file when you reboot. Instead, save this file under /usr/tmp.

   ---

5. Replace the failed disk.

   1. Determine which node owns the device group.

      # scstat -D

   2. If you are using VERITAS Volume Manager, remove the LUNs from the VERITAS Volume Manager control on a node that does not have ownership of the device group.

      # vxdisk offline cNtXdY # vxdisk rm cNtXdY

   3. On a node that does not have ownership of the device group, suspend activity on the SCSI bus.

      # cfgadm -x replace_device cX::disk/cXtYdZ

      When prompted, enter y to suspend activity on the SCSI bus.

   4. After SCSI bus activity stops, replace the disk and enter y at the prompt.

      After replacing the disk, warning messages might display. These messages can be ignored.

   5. Switch the primary for the device group.

      # scswitch -z -D disk-device-group -h node

   6. If you are using VERITAS Volume Manager, remove the LUNs from the VERITAS Volume Manager control on a node that does not have ownership of the device group.

      # vxdisk offline cNtXdY # vxdisk rm cNtXdY

   7. Suspend activity on the device group's original primary.

      # cfgadm -x replace_device cX::disk/cXtYdZ

      When prompted, enter y to suspend activity on the SCSI bus.

   8. When prompted to proceed with the disk replacement, enter y to proceed.

      Warning messages might display. These messages can be ignored.

6. On all nodes that that are attached to the storage device, run the devfsadm(1M) command to probe all devices and to write the new disk drive to the /dev/rdsk directory.

   Depending on the number of devices connected to the node, the devfsadm command can require at least five minutes to complete.

   # devfsadm

7. Label the new disk drive by using the format command.

8. If you are using Solstice DiskSuite/Solaris Volume Manager as your volume manager, from any node that is connected to the storage device, partition the new disk drive by using the partitioning you saved.

   If you are using VERITAS Volume Manager, skip this step.

   # fmthard -s filename /dev/rdsk/cNtXdYsZ

9. From all nodes that are connected to the disk drive, update the DID database and driver.

   # scdidadm -R deviceID

   ---

   Note - After running scdidadm --R on the first node, each subsequent node that you run the command on might display a warning. This warning can be ignored.

   ---

10. From any node, confirm that the failed disk drive has been replaced by comparing the new physical DID to the physical DID that was identified at the beginning of this procedure.

    If the new physical DID is different, you successfully replaced the failed disk drive with a new disk drive.

    # scdidadm -o diskid -l cNtXdY

11. Perform volume management administration to add the disk drive back to its diskset or disk group.

    For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.

12. If you want this new disk drive to be a quorum device, add the quorum device.

    For procedures on how to add quorum devices, see your Sun Cluster system administration documentation.