How to Remove a Disk Drive

Use this procedure to remove a disk drive from a storage arrays. Perform the steps in this procedure in conjunction with the procedures in the 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.

1. Is the disk drive you are removing a quorum device?

   # scstat -q

   • If no, proceed to Step 2.

   • If yes, choose and configure another device to be the new quorum device. Then remove the old quorum device.

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

2. 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.

3. Identify the disk drive that needs to be removed. Identify the slot from which the disk drive needs to be removed.

   If the disk error message reports the drive problem by DID, use the scdidadm -l command to determine the Solaris device name.

   # scdidadm -l deviceID # cfgadm -al

4. Remove the disk drive.

   For more the procedure about how to remove a disk drive, see the Sun StorEdge MultiPack Storage Guide.

5. On all nodes, remove references to the disk drive.

   # cfgadm -c unconfigure cN::dsk/cNtXdY # devfsadm -C # scdidadm -C

How to Add a Storage Array

Use this procedure to install a storage array in a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster software installation documentation and your server hardware manual.

This procedure uses an updated method for setting the scsi-initiator-id. This new method must be used with the StorEdge PCI Dual Ultra3 SCSI host adapter. If you are adding this storage array to a cluster configuration that uses the previous method of setting the scsi-initiator-id, you will need to update the nvramrc script and set the scsi-initiator-id by using this procedure. The previous method relied on setting each node's scsi-initiator-id for shared storage in the nvramrc script.

Note - To determine if the cluster configuration uses the previous method of setting the scsi-initiator-id, run the following command on the two nodes that you plan to connect to this storage array.

# eeprom scsi-initiator-id

If scsi-initiator-id equals 7 on both nodes, you must update the nvramrc script and set the scsi-initiator-id for each node that connects to this storage array.

For conceptual information on multi-initiator SCSI and device IDs, see the Sun Cluster concepts documentation.

The single-ended SCSI specifications specify that bus lengths are based on speed and number of devices. The bus lengths in the following table outline a typical implementation of the single-ended SCSI specifications for Sun hardware. For details, see your host adapter and storage documentation.

Table 1-3 Typical Single-Ended, Wide SCSI Bus Lengths

¹ Devices include both targets and initiators.

If you exceed these specifications, you might experience SCSI errors. The host adapter or the driver might recover from these errors by retrying the request. If this action does not succeed, the host adapter or the driver might recover by renegociating to a less demanding mode of operation. In some cases, the host adapter or the driver might not be able to recover from these errors, and I/O might fail. You experience delays in I/O if the host adapter or the driver needs to perform this recovery.

If your configuration uses UltraSCSI and requires the 6-meter bus length, use the host adapter driver's scsi-options property to limit the speed negotiation to FastSCSI operation. Use the following /kernel/drv/glm.conf file as an example to set the scsi-options property.

name="glm" parent="/pci@1f,4000" unit-address="2" scsi-options=0x3f8;

This example uses specific hardware. Change this example to accommodate the hardware in your configuration. In this example, the scsi-options property sets the following support.

• Disconnect/reconnect

• Synchronous transfer

• Parity

• Fast SCSI

• Wide SCSI

For more information, see your isp(7D), glm(7D) or other host adapter driver man page and documentation on http://sunsolve.sun.com.

1. Shut down and power off Node 1.

   For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.

2. Install the host adapters in Node 1.

   For the procedure about how to install a host adapter, see the documentation that shipped with your host adapter and node.

3. Connect the appropriate SCSI cable between the node and the storage arrays, as shown in Figure 1-5.

   To cable the storage arrays correctly, adhere to the bus length restrictions listed in the documentation that shipped with your host adapter. In a Sun Cluster environment, this cable length measurement includes the cables to both nodes. This cable length measurement also includes the bus length that is internal to each storage array, node, and host adapter.

   Figure 1-5 Adding a Storage Arrays Mirrored Pair Configuration: Part I

   

4. Install a terminator on the SCSI IN port of the second storage arrays as shown in Figure 1-5. This terminator is temporary.

5. Connect each storage arrays of the mirrored pair to different power sources.

6. Ensure that each device in the SCSI chain has a unique SCSI address.

   To avoid SCSI-chain conflicts, this procedure instructs you to reserve SCSI address 7 for one host adapter in the SCSI chain and change the other host adapter's global scsi-initiator-id to an available SCSI address. Then the procedure instructs you to change the scsi-initiator-id for local devices back to 7.

   ---

   Note - A slot in the storage array might not be in use. However, do not set the scsi-initiator-id to a SCSI address for that disk slot. This precaution minimizes future complications if you install additional disk drives.

   ---

   1. If necessary, power on the storage devices.

      For the procedure on powering on a storage device, see the service manual that shipped with your storage device.

   2. If necessary, power on a node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.

   3. Set the scsi-initiator-id for one node to 6.

      {1} ok setenv scsi-initiator-id 6 scsi-initiator-id = 6

   4. Find the paths to the host adapters that connect to the local disk drives.

      {0} ok show-disks

      Use this information to change the SCSI addresses in the nvramrc script. Do not include the /sd directories in the device paths.

   5. Edit the nvramrc script to set the scsi-initiator-id for the local devices on the first node to 7.

      For a full list of commands, see the OpenBoot 2.x Command Reference Manual.

      ---

      Caution - Insert exactly one space after the first double quote and before scsi-initiator-id.

      ---

      {0} ok nvedit 0: probe-all 1: cd /pci@1f,4000/scsi@2 2: 7 " scsi-initiator-id" integer-property 3: device-end 4: cd /pci@1f,4000/scsi@3 5: 7 " scsi-initiator-id" integer-property 6: device-end 7: install-console 8: banner[Control C] {0} ok

   6. Store the changes.

      The changes you make through the nvedit command are recorded on a temporary copy of the nvramrc script. You can continue to edit this copy without risk. After you complete your edits, save the changes. If you are not sure about the changes, discard them.

      • To store the changes, type:

        {0} ok nvstore {1} ok

      • To discard the changes, type:

        {0} ok nvquit {1} ok

   7. Verify the contents of the nvramrc script that you created, as shown in the following example.

      If the contents of the nvramrc script are incorrect, use the nvedit command to make corrections.

      {0} ok printenv nvramrc nvramrc = probe-all cd /pci@1f,4000/scsi@2 7 " scsi-initiator-id" integer-property device-end cd /pci@1f,4000/scsi@3 7 " scsi-initiator-id" integer-property device-end install-console banner {1} ok

   8. Instruct the OpenBoot PROM (OBP) Monitor to use the nvramrc script, as shown in the following example.

      {0} ok setenv use-nvramrc? true use-nvramrc? = true {1} ok

7. Perform a reconfiguration boot to create the new Solaris device files and links.

8. On all nodes, verify that the DIDs have been assigned to the disk drives in the storage arrays.

   # scdidadm -l

9. Shut down and power off Node 2.

   For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.

10. Install the host adapters in Node 2

    For the procedure about how to install a host adapter, see the documentation that shipped with your host adapter and node.

11. Remove the SCSI terminator that you installed in Step 4.

12. Connect the storage arrays to the host adapters by using SCSI cables, as shown in Figure 1-6.

    Figure 1-6 Adding a Mirrored Pair Configuration: Part II

    

13. Verify that the scsi-initiator-id is set correctly on the second node.

    1. If necessary, power on the second node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.

    2. Verify that the scsi-initiator-id for each host adapter on the second node is set to 7

       Use the show-disks command to find the paths to the host adapters that are connected to these enclosures. Select each host adapter's device tree node, and display the node's properties to confirm that the scsi-initiator-id for each host adapter is set to 7.

       {0} ok cd /pci@6,4000/pci@3/scsi@5 {0} ok .properties scsi-initiator-id 00000007 ...

14. Perform a reconfiguration boot on Node 2 to create the new Solaris device files and links.

15. On all nodes, verify that the DIDs have been assigned to the disk drives in the storage arrays.

    # scdidadm -l

16. Perform volume management administration to add the disk drives to the volume management configuration. These disk drives resize in the storage arrays.

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