You must select Start Recovery in the Grid Management Interface to configure the recovery Storage Node so that the grid recognizes it as a replacement for the failed node.
Before you begin
- You must be signed in to the Grid Management Interface using a supported browser.
- You must have a service laptop.
- You must have Maintenance or Root Access
permissions.
- You must have the provisioning passphrase.
- You must have deployed and configured the node you are recovering.
- Take note of the start date of any repair jobs for erasure-coded data, and verify that the node has not been rebuilt within the last 15 days.
Steps
- From the Grid Management Interface, select .
- Select the grid node you want to recover in the Pending Nodes list.
Nodes appear in the list after they fail, but are not selectable unless they have been reinstalled and are ready for recovery.
- Enter the Provisioning Passphrase.
- Click Start Recovery.

- Monitor the progress of the recovery in the Recovering Grid Node table.
Note: At any point during the recovery, you can click Reset to start a new recovery.
Linux: If you reset the recovery, you must also manually restart the node by running the command storagegrid node force-recovery <node-name> on the Linux host.
VMware/OpenStack: If you reset the recovery, you must manually delete the deployed virtual grid node. To restart the recovery, re-deploy the virtual grid node using the steps in the section titled "Deploying the recovery grid node."

- When the Storage Node reaches the stage "Waiting for Manual Steps" stage, move on to the next task in the recovery procedure, to remount and reformat storage volumes.