> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/operation-guide/replace-a-failed-drive.md).

# Replace a failed drive

Replace a failed storage drive and restore cluster redundancy and capacity.

Replace a failed storage drive to restore cluster redundancy and capacity. This procedure does not apply to operating system drives.

### Before you begin

* Obtain a compatible replacement drive.
* Access the cluster CLI with permissions to manage drives.
* Schedule a maintenance window if your server does not support hot swapping.

{% hint style="warning" %}
When rebuild capacity is unavailable, a failed drive reduces data redundancy and protection.
{% endhint %}

### Replace the drive

1. Identify the failed drive and record its UUID and host ID.

   ```bash
   weka cluster drive -F node=invalid -o id,uuid,host,hostname,node,status
   ```

   If the command does not show the failed drive, run:

   ```bash
   weka cluster drive -F status=inactive -o id,uuid,host,hostname,node,status
   ```

   A failed drive displays an invalid process ID and an `INACTIVE` status.
2. Deactivate the failed drive.

   ```bash
   weka cluster drive deactivate <drive-uuid>
   ```
3. Remove the drive from the cluster.

   ```bash
   weka cluster drive remove <drive-uuid>
   ```
4. Replace the physical drive. Follow the server vendor's service procedure.
5. Confirm that the operating system detects the replacement drive.

   ```bash
   lsblk
   ```

   The output shows the new device and devices not used by the data path.
6. Add the replacement drive to the cluster. Use the failed drive's host ID from Step 1.

   ```bash
   weka cluster drive add <host-id> <device-path>
   ```

   For example:

   ```bash
   weka cluster drive add 1 /dev/nvme1n1
   ```
7. Confirm that the drive joins the cluster and monitor recovery.

   ```bash
   weka status
   ```

   When the rebuild completes, the replacement drive becomes `ACTIVE`.

**Related information**

See [Shrink a cluster](/operation-guide/expanding-and-shrinking-cluster-resources/shrinking-a-cluster.md) for drive deactivation and removal details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/operation-guide/replace-a-failed-drive.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.