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 your Sun Cluster system administration documentation and your server hardware manual.
For conceptual information on quorum, quorum devices, global devices, and device IDs, see your Sun Cluster concepts documentation.
Note the target number of the empty disk slot that you plan to add the disk drive to.
Identify the disk slot in the JBOD storage array for the disk drive that you are adding and note the target number. Refer to the documentation that shipped with your storage array.
Install the disk drive.
For the procedure about how to install a disk drive, see the Sun StorEdge 3310 SCSI Array Installation, Operation, and Service Manual.
On all nodes attached to the JBOD storage array, configure the disk drive into the cluster.
# cfgadm -c configure cN # devfsadm
If necessary, use the format(1M) command or the fmthard(1M) command to partition and label the disk drive.
From any node, update the global device namespace.
# scgdevs
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.
On one node, verify that a device ID (DID) has been assigned to the disk drive.
# scdidadm -L
Perform volume management administration to add the new disk drive to the configuration.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
If you want this new disk drive to be a quorum device, add the quorum device.
For procedures about how to add and remove quorum devices, see your Sun Cluster system administration documentation.
How to Remove a Disk Drive
Use this procedure to remove a disk drive from a JBOD storage array in a running cluster. Perform the steps in this procedure in conjunction with the procedures in your Sun Cluster system administration documentation and the Sun StorEdge 3310 SCSI Array Installation, Operation, and Service Manual.
For conceptual information on quorum, quorum devices, global devices, and device IDs, see your Sun Cluster concepts documentation.
Identify the disk drive that you are removing. Identify the slot that the disk drive needs to be removed from.
If the disk error message reports the drive problem by DID, use the scdidadm -l command to determine the Solaris device name. To list all configurable hardware information, use the cfgadm -al command.
# scdidadm -l deviceID # cfgadm -al
Is the disk drive a quorum device? This disk drive is the disk drive that you are removing.
# scstat -q
If no, proceed to Step 3.
If yes, relocate that quorum device to another suitable JBOD storage array.
For procedures about how to add and remove quorum devices, see your Sun Cluster system administration documentation.
If possible, back up the metadevice or volume.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
Perform volume management administration to remove the disk drive from the configuration.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
On all nodes, unconfigure the disk drive. Remove references to the disk drive from the operating system and clustering environment.
# cfgadm -c unconfigure cN::dsk/cNtXdY
Remove the disk drive.
For the procedure about how to remove a disk drive, see the Sun StorEdge 3310 SCSI Array Installation, Operation, and Service Manual.
On both nodes, remove the paths to the LUN that you are deleting.
# devfsadm -C
On both nodes, remove all obsolete device IDs (DIDs).
# scdidadm -C
How to Replace a Disk Drive
Use this procedure to replace a disk drive in a JBOD storage array. Perform the steps in this procedure in conjunction with the procedures in your Sun Cluster system administration documentation and the Sun StorEdge 3310 SCSI Array Installation, Operation, and Service Manual.
For conceptual information on quorum, quorum devices, global devices, and device IDs, see your Sun Cluster concepts documentation.
Identify the failed disk drive.
# scdidadm -o diskid -l cNtXdY
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.
If possible, back up the metadevice or volume.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
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.
Replace the failed disk.
Determine which node owns the device group.
# scstat -D
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
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.
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.
Switch the primary for the device group.
# scswitch -z -D disk-device-group -h node
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
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.
When prompted to proceed with the disk replacement, enter y to proceed.
Warning messages might display. These messages can be ignored.
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
Label the new disk drive by using the format command.
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
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.
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
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.
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.