Kubernetes Storage & Volume Errors
Every Kubernetes persistent-storage failure in one place: a PVC that never binds, a volume stuck multi-attached to a dead node, mounts that time out, CSI drivers that miss their deadline. Each guide opens with the direct answer, then the exact `kubectl` and CSI commands to confirm and fix it. Start with the fastest path below, or paste your own error into the assistant.
Fix your error now
Paste the error or logs and let the Incident Assistant diagnose it, or run a guided triage prompt with AI — no copy-paste.
Every guide in this cluster
12 guides-
'pod has unbound immediate PersistentVolumeClaims' PVC Pending
Fix unbound PersistentVolumeClaims in Kubernetes: resolve missing StorageClass, WaitForFirstConsumer binding, storageClassName mismatch, and CSI provisioner failures.
-
'FailedAttachVolume' Multi-Attach Stuck Pod
Fix the FailedAttachVolume Multi-Attach error: detach volumes stuck on a dead node, switch RWO to RWX where needed, and unblock pods that hang in ContainerCreating.
-
code = DeadlineExceeded' CSI Attach/Mount Timeout
Fix 'rpc error: code = DeadlineExceeded, context deadline exceeded' in Kubernetes CSI attach/mount: slow cloud APIs, throttling, and stuck VolumeAttachments.
-
'Warning FailedMount' MountVolume.SetUp Failed Event
Fix the 'Warning FailedMount ... MountVolume.SetUp failed for volume' event in Kubernetes by finding the missing secret, configmap, subPath, or permission behind it.
-
'DiskPressure True' Node Condition and Eviction Taint
Fix Kubernetes DiskPressure: kubelet nodefs/imagefs eviction thresholds, image garbage collection, the disk-pressure taint, and pods evicted or refused scheduling.
-
'failed to provision volume with StorageClass' RPC Error
Fix 'failed to provision volume with StorageClass: rpc error' in Kubernetes: decode CSI provisioner failures from zone/topology mismatch, quota, and IAM.
-
'MountVolume.SetUp failed for volume' Storage Mount Failures
Fix 'MountVolume.SetUp failed' in Kubernetes: missing Secrets/ConfigMaps, stuck CSI volume attachments, fsGroup permission errors, subPath issues, and cache timeouts.
-
'node(s) had untolerated taint' Pod Won't Schedule
Fix the Kubernetes FailedScheduling error 'node(s) had untolerated taint' and 'didn't match node affinity/selector': taints, tolerations, nodeSelector, and affinity.
-
'node(s) had volume node affinity conflict' — Fix Pod Scheduling
Fix the 'node(s) had volume node affinity conflict' scheduling failure in Kubernetes: zonal PVs, topology-bound StorageClasses, cordoned zones, and pods pinned away from their volume.
-
'persistentvolumeclaim not found' StatefulSet Pod
Fix a StatefulSet pod stuck because its volumeClaimTemplates PVC is missing — deleted claims, retain policy mismatches, and ordinal-bound storage.
-
'Unable to attach or mount volumes: timed out waiting for the condition'
Fix 'Unable to attach or mount volumes ... timed out waiting for the condition' in Kubernetes by decoding unmounted vs unattached volume lists and the stuck CSI step.
-
The Volume That Wouldn't Let Go: A Kubernetes PVC War Story
A 2 a.m. Kubernetes war story — a Multi-Attach error on an RWO PersistentVolumeClaim took a service down. The real fix, and where devopsaitoolkit.com came from.
Kubernetes & Helm AI prompts
Copy-paste, production-safe prompts for this stack.
Kubernetes & Helm command center
Top errors, validators, and runbooks for the whole stack.
Frequently asked questions
Why is my PersistentVolumeClaim stuck in Pending?
Pending when nothing can bind it: no PersistentVolume matches its size/access mode, its StorageClass has no working dynamic provisioner, or the provisioner is throwing errors. Run kubectl describe pvc <name> and read the events — they name the exact reason. See the PVC not bound guide.What does "Multi-Attach error for volume" mean?
ReadWriteOnce volume can attach to only one node at a time. The error appears when a pod is rescheduled to a new node while the old node still holds the attachment (commonly after a node goes NotReady). Fix it by clearing the stale VolumeAttachment or letting the old node release it — see the multi-attach guide.Can I diagnose these with AI instead of reading every guide?
kubectl describe output into the Incident Assistant at the top of this page, or click "Run the triage prompt with AI" to open a guided storage-troubleshooting prompt in the Prompt Workspace.