# Pods Are Displaying FailedAttachVolume or FailedMount Errors

You may run into a problem where the PCD management plane pods are not functioning or running due to PVC mount failures, specifically displaying "FailedAttachVolume" or "FailedMount" errors.

{% tabs %}
{% tab title="Pod Event Section" %}

```ruby
Warning  FailedMount         5h32m (x31004 over 6h27m)  kubelet                  MountVolume.WaitForAttach failed for volume "pvc-[pvc-id]" : volume attachment is being deleted

Warning  FailedAttachVolume  5h30m (x36 over 6h27m)     attachdetach-controller  AttachVolume.Attach failed for volume "pvc-[pvc-id]" : volume attachment is being deleted
```

{% endtab %}
{% endtabs %}

## Most common causes

* The storage backend is unreachable.
* The underlying host does not have sufficient resources to run these pods.
* CSI Driver itself is not configured correctly or has some errors.
* Calico network pods are not working as expected.

## Steps to Troubleshoot

{% stepper %}
{% step %}
**Check pods in init state**

Check the number of pods in the `Init` state to identify any pod stuck in initialization. The failure of PVC mount attachments can cause pods to remain in an `Init` state.

{% tabs %}
{% tab title="Command" %}

```bash
$ kubectl get pods -A | grep -i "init"
```

{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
**Get CSI drivers**

Run the following command to list CSI drivers (storage backend).

{% tabs %}
{% tab title="Command" %}

```bash
$ kubectl get csidrivers
```

{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
**Verify CSI driver pods are running**

Verify if the CSI driver pods are running. The pods can either be in a dedicated namespace or inside the `kube-system` namespace. In this example the NetApp backend uses the `trident` namespace to host its storage backend pods.

{% tabs %}
{% tab title="Command" %}

```bash
$ kubectl get pods -n <CSI-driver-namespace>/<kube-system>

E.g.
$ kubectl get pods -n trident
trident           trident-controller-pod    0/6     ContainerCreating   0                 6h44m
trident           trident-node-linux-pod    0/2     CrashLoopBackOff    20 (5h33m ago)    23m
trident           trident-node-linux-pod    0/2     CrashLoopBackOff    15 (5d4h ago)     23d
trident           trident-node-linux-pod    0/2     CrashLoopBackOff    34 (5d3h ago)     23d
```

{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
**Inspect Calico pods**

As Calico provides pod networking, review all Calico pods and determine why these pods are in a "CrashLoopBackOff/ContainerCreating/OOMKilled/Pending/Error" state; check the events from the describe output.

{% tabs %}
{% tab title="Command" %}

```bash
$ kubectl describe <pod-name> -n <calico-namespace>
```

{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
**Check logs for failing pods**

Get more information on the failure from the pod logs.

{% tabs %}
{% tab title="Command" %}

```bash
$ kubectl logs <pod-name> -n <CSI-driver-namespace>/<kube-system>
```

{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}
**When to escalate**

If these steps don't resolve the issue, please contact your Backend Storage Provider or reach out to the Platform9 Support Team for additional assistance.

* Platform9 Support Team: <https://support.platform9.com/hc/en-us>
  {% endstep %}
  {% endstepper %}


---

# Agent Instructions: 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/2026.1/getting-started/self-hosted/troubleshooting-and-log-files/pods-are-displaying-failedattachvolume-or-failedmount-errors.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.