Back to all scenarios
Scenario #326
Storage
Kubernetes v1.26, Azure Disk CSI
Mount Volume Exceeded Timeout
Pod remained stuck in ContainerCreating state because volume mount operations timed out.
Find this helpful?
What Happened
CSI node plugin had stale cache and attempted mount on incorrect device path. Retry logic delayed pod start by ~15 minutes.
Diagnosis Steps
- 1Described pod: stuck with Unable to mount volume error.
- 2Node CSI logs: device not found.
- 3Saw old mount references in plugin cache.
Root Cause
Plugin did not invalidate mount state properly after a failed mount.
Fix/Workaround
• Cleared plugin cache manually.
• Upgraded CSI driver to fixed version.Lessons Learned
CSI drivers can introduce delays through stale state.
How to Avoid
- 1Keep CSI drivers up-to-date.
- 2Use pre-mount checks to validate device paths.