> 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/private-cloud-director/storage/troubleshooting-and-log-files.md).

# Troubleshooting And Log Files

## Troubleshooting Block Storage Service Problems

If your <code class="expression">space.vars.product\_name</code> Service Health dashboard is reporting that the block storage service is unhealthy, or if you are running into unexpected issues when performing block storage service operations such as volume creation, attachment etc, this likely means:

1. One or more hosts assigned with Block Storage role may be offline or unavailable
2. The hosts with Block Storage role assigned may be online but the service components may be offline or experiencing error connecting to or working with your specific storage backend.

Refer to the block storage service [Log Files](#log-files) to debug the issues further.

## Troubleshooting Guides

The following guides address the most common operational problems with block storage:

* [Troubleshooting Cinder Issues](/private-cloud-director/storage/troubleshooting-and-log-files/troubleshooting-cinder-issues.md) — general service diagnostics, volume creation and deletion flows, log reference.
* [Volume Attach / Detach Troubleshooting](/private-cloud-director/storage/troubleshooting-and-log-files/volume-attach-detach-troubleshooting.md) — volumes stuck in `detaching`, `attaching`, or `reserved`; stale attachment cleanup; Nova BDM inconsistency recovery.
* [Volume Migration and Retype Troubleshooting](/private-cloud-director/storage/troubleshooting-and-log-files/volume-migration-retype-troubleshooting.md) — failed or stuck migrations (`migration_status=error`), incompatible drivers, NFS capacity imbalance, recovery steps.
* [Persistent Storage Service Backend Selection and Tuning](/private-cloud-director/storage/troubleshooting-and-log-files/backend-selection-and-tuning.md) — how the storage scheduler selects a backend pool, why a backend is skipped, and how to influence placement with volume types and extra specs.
* [Boot-from-Volume Provisioning and Failure Recovery](/private-cloud-director/storage/troubleshooting-and-log-files/boot-from-volume-troubleshooting.md) — creating VMs from boot volumes, diagnosing VM-from-volume failures, recovering from partial creation.
* [Tenant Teardown: Storage Cleanup](/private-cloud-director/storage/troubleshooting-and-log-files/tenant-teardown-storage-cleanup.md) — safe workflow for deleting tenants or backends that have resident volumes, snapshots, or images.

## Log Files

* The log file that corresponds to all block storage attach / detach operations is located at `/var/log/pf9/cindervolume-base.log`.This file contains information about:
  * Storage backend driver used
  * Whether the Block Storage Service could connect to the storage backend being used
  * Any errors when creating volumes, copying volumes, and attaching/detaching volumes to virtual machines
* Look at the compute service log file `/var/log/pf9/ostackhost.log` file for further details when debugging any issues related to volume attachment to virtual machines.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.platform9.com/private-cloud-director/storage/troubleshooting-and-log-files.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.