---
title: "Detach a volume from a node"
description: "Detach a Block Storage volume from a node without losing its data, so you can attach it elsewhere or delete it."
content_type: "how-to"
product: "volumes"
platform: "MyAccount"
url: "/myaccount/volumes/how-to/detach-a-volume/"
topic: ["create"]
relationships: {"requires":["/myaccount/volumes/how-to/attach-a-volume/"]}
---

# Detach a volume from a node

Detaching a volume removes it from a node but keeps the volume and its data. The volume returns to
**Available** and can be attached to another node or deleted. Billing continues until you delete the
volume.

## Before you begin

- A volume attached to a node.
- On the node, anything using the volume is closed, and the volume is unmounted.

## Unmount the volume on the node

Detach once nothing is using the volume, and unmount it in the operating system first to avoid data
loss. On Linux, unmount it and remove its entry from `/etc/fstab`:

```bash
sudo umount /data
```

If the volume is in `/etc/fstab`, remove that line too. Leaving it there can stop the node from
booting properly on its next restart. On Windows, close anything using the drive, then take the
disk **Offline** in Disk Management.

## Detach the volume

1. Open **Storage > Volumes**.
2. Select the volume, open its **Actions** menu, and choose **Detach**.
3. Confirm the detach. Read the confirmation; it lists what happens.

The volume's status returns to **Available**. Detaching also turns off any snapshot scheduling
and snapshot lifecycle you had set for it.

The volume is back to **Available** with its data intact, free to attach to another node, [move](/myaccount/volumes/how-to/move-a-volume-to-another-project/), or [delete](/myaccount/volumes/how-to/delete-a-volume/). A detach that fails, or a node that will not boot afterwards, is covered in [Troubleshooting Volumes](/myaccount/volumes/troubleshooting/volumes/).