> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/5.8/instances/virtual-machines-delete-volume-block-from-instance.md).

# Detach Volume/Block Storage from Instance

You may detach a volume from an instance that is not active or has crashed. The detached volume is available to be attached to another instance. You cannot detach volumes from virtual machines that are in ‘Error’ state.

You must be a self-service user or an administrator to perform this operation.

To detach a volume from an instance, follow the steps given below.

1\. Log in to Clarity.

2\. Click Instances in the left panel.

3\. Select the checkbox for the instance to which you want to attach a volume.

4\. Click More>Manage Volumes on the toolbar seen above the list of instances.

<figure><img src="https://2491133324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTp3vmrOuO3dQilOzN2fE%2Fuploads%2Fgit-blob-d3843ec8dbd9f218601320320cde5643af3cc411%2F1605214391.png?alt=media" alt=""><figcaption></figcaption></figure>

5\. Click Detached for the volume you wish to attach.

6\. Click Update Volumes.

The volume is detached and available to be attached to other instances.


---

# 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.platform9.com/managed-openstack/5.8/instances/virtual-machines-delete-volume-block-from-instance.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.
