Dell PowerVault 770N (Deskside NAS Appliance) - Manual (Page 70)

chkdsk /f q:
where q is the drive letter assigned to your quorum resource.
5. After the chkdsk utility completes, stop MSCS by pressing <Ctrl><c>.
6. Restart the cluster service.
To restart MSCS from the Services console:
a. Click the Start button and select Programs → Administrative Tools→ Services.
b. In the Services window, right-click Cluster Service.
c. In the drop-down menu, click the Start button.
To restart MSCS from the command prompt:
a. Open the second command prompt window that you opened in step 4 a.
b. Type the following:
Net Start Clussvc
The Cluster Service restarts.
See the Microsoft Knowledge Base article 258078 located at the Microsoft Support website at www.microsoft.com for more information on recovering from a
corrupt quorum resource.
Replacing a Cluster Node
This section assumes that you have a recent tape backup of the cluster node that contains the local registry information.
1. Ensure that the replacement cluster node is physically disconnected from the storage system.
2. Ensure that Windows is installed and configured properly.
3. Install the correct NIC drivers, assign the appropriate IP addresses, and install the driver for the HBAs.
4. If applicable, install the necessary tape device drivers and back up application program.
5. Shut down Windows and turn off the system.
6. Connect the fiber optic cables from each HBA to the appropriate ports on the
storage system or Fibre Channel switch.
7. Turn on the replacement cluster node and reassign the LUNs (if applicable).
8. Using the most current tape backup, restore the backup (including the Windows registry files) and restart the system.
If a backup is not available:
a. On the remaining cluster node, start Cluster Administrator.
b. Right-click the failed node and select Evict Node.
c. On the replacement node, install and configure MSCS.
d. Select the option to join an existing cluster.
9. Use Cluster Administrator to verify that the node rejoins the cluster, and check the Windows Event Viewer to ensure errors were not encountered.
NOTICE: If a recent tape backup is not available, all application programs must be reinstalled.
10. Apply any additional service pack.
11. Reinstall any cluster applications (such as Microsoft SQL Server or Exchange Server onto the new node [if required]).
NOTE: You may need to reinstall or configure your cluster applications before moving or testing the failover capabilities of any cluster resources to
the new node.