Kubelet cannot mount the volume onto the node
Production Risk
Stateful pod cannot start; data is inaccessible until the mount issue is resolved.
VolumeMountError is a lower-level error than FailedMount, indicating that kubelet successfully located the volume but failed when actually mounting it onto the node filesystem. This typically points to filesystem-level issues: wrong filesystem type, corrupted volume, missing kernel modules, or access permission problems on the mount path.
- 1Volume has an incompatible filesystem type for the node OS (e.g., XFS on a node without xfsprogs)
- 2Block volume is already attached to another node (ReadWriteOnce constraint)
- 3Mount path permissions prevent kubelet from mounting the volume
- 4NFS server access rules deny the node's IP address
Pod stuck in ContainerCreating; events show a specific mount error message.
kubectl describe pod mypod | grep -A 20 "Events:" # Warning FailedMount kubelet MountVolume.SetUp failed for volume "my-pv": # mount failed: exit status 32 # Mounting command: mount # Mounting arguments: -t ext4 /dev/sdb /var/lib/kubelet/pods/.../volumes/...
expected output
Warning FailedMount ... MountVolume.SetUp failed for volume "my-pv": mount failed: exit status 32
Fix 1
Check if volume is attached to another node
WHEN PV is ReadWriteOnce
kubectl describe pv my-pv | grep -E "Claim|Node Affinity|Status" # If attached to a different node, drain that node or delete the old pod first
Why this works
ReadWriteOnce PVs can only be mounted on one node at a time; releasing the old attachment resolves the conflict.
Fix 2
Inspect kubelet logs for the mount error
WHEN Mount error details are needed
journalctl -u kubelet --since "5 minutes ago" | grep -i "mount|volume"
Why this works
kubelet logs contain the raw mount command output and OS-level error message.
Kubernetes Documentation
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev