> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pcd/storage/how-to-reset-volume-states.md). # How To Reset Volume States ## Problem Private Cloud Director block storage volumes can be in the following states: "reserved", “error”, “creating”, “deleting”, “in-use”, “attaching”, “detaching”, “error\_deleting” or “maintenance”. Sometimes the volumes might be in a state that does not reflect their present condition. For example, a failed live migration might set the volume state to "error". However, it is possible to access and edit the data inside the volume. In such a case, it becomes necessary to reset the volume state to reflect its actual condition. ## Environment * Private Cloud Director Virtualization - v2025.4 and Higher * Self-Hosted Private Cloud Director Virtualization - v2025.4 and Higher * Self-Hosted Private Cloud Director Kubernetes - v2025.4 and Higher ## Procedure 1. These steps can only be run as admin. Source the RC file with the admin credentials. ```bash $ source ``` 2. Get the UUID of the volume whose status that needs to be changed. ```bash $ openstack volume list ``` 3. Change the status using the following command. ```bash $ openstack volume set --state ``` ## Validation Verify if the volume state has changed. ```bash $ openstack volume show ``` ## Additional Information * [Set other volume properties](https://docs.openstack.org/python-openstackclient/ocata/command-objects/volume.html?#volume-set) --- # 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://platform9.com/kb/pcd/storage/how-to-reset-volume-states.md?ask=&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.