Sun Cluster 2.2 System Administration Guide

Replacing a Local Non-Boot Disk

This section describes the replacement of a failed local disk that does not contain the Solaris operating environment.

In general, if a local non-boot disk fails, you recover using a backup copy to restore the data to a new disk.

The procedures for restoring a local boot disk are described in "How to Restore a Local Boot Disk From Backup (Solstice DiskSuite)", and in "How to Restore a Local Boot Disk From Backup (VxVM)".

These are the high-level steps to replace a failed local non-boot disk.

How to Replace a Local Non-Boot Disk

These are the detailed steps to replace a failed local non-boot disk. In this example, phys-hahost2 contains the disk that failed.

  1. (Optional) Shut down the Sun Cluster services on the node with the failed disk and halt the node.

    You may not need to perform this step if the node boots from a SPARCstorage Array disk. However, if the disk to be replaced is on the same SCSI bus as the functioning boot disk, you must shut down Sun Cluster and halt the node.


    # scadmin stopnode
    ...
    # halt
    

  2. Perform the disk replacement.

    Use the procedure described in the service manual for your Sun Cluster node.

  3. Start the node in single-user mode.

  4. Run the format(1M) or fmthard(1M) command to repartition the new disk.

    Make sure that you partition the new disk exactly as the disk that was replaced. (Saving the disk format information is outlined in Chapter 1, Preparing for Sun Cluster Administration.)

  5. Run the newfs(1M) command on the new slices to create file systems.

  6. Run the mount(1M) command to mount the appropriate file systems.

    Specify the device and mount points for each file system.

  7. Restore data from a backup copy.

    Use the instructions in you Solaris system administration documentation to perform this step.

  8. Reboot the node.

  9. Start Sun Cluster on the local host.


    phys-hahost1# scadmin startnode
    

  10. Switch back the logical hosts to the default master, if necessary.

    If manual mode is not set, an automatic switchback will occur.


    phys-hahost2# haswitch phys-hahost2 hahost2