Kubernetes FailedMount
Kubernetes could not attach, prepare or mount one or more volumes required by the Pod.
Unable to attach or mount volumesAlso searched as: FailedMount · FailedAttachVolume
What it means
The failure may sit at the Pod specification, Secret or ConfigMap, PVC binding, storage topology, cloud attachment, CSI controller, node plugin or filesystem layer. The event chain identifies the failing stage.
Typical trigger conditions
- Missing Secret, ConfigMap or PVC
- Volume attachment still held by another node
- CSI controller or node plugin failure
- Zone, access-mode or filesystem mismatch
First diagnostic checks
Read chronological Pod events
Preserve the complete CSI or kubelet message, including referenced object and RPC status.
kubectl describe pod <pod> -n <namespace>
Inspect PVC and VolumeAttachment
Confirm binding, access mode, storage class and attachment target.
kubectl get pvc -n <namespace>; kubectl get volumeattachments
Check CSI components
Inspect the relevant controller and node-driver logs for the same volume identifier.
Version and platform notes
Available CSI sidecars and feature behaviour depend on the Kubernetes and driver versions; check both support matrices.
Follow Kubernetes failures and fixes
One useful weekly email with new error references, tools, integration notes and production lessons. No daily noise.