Problem with volume multi-attach error after node crash

Olivia Gonzalez 20 Reputation points
2026-10-01T17:02:30.13+00:00

We run critical stateful workloads in our corporate environment, and pods get rescheduled across nodes.

Why is it that whenever a worker node crashes, pods in a StatefulSet fail to start with a Multi-Attach error for the volume, the volume stays stuck on the dead node, and Kubernetes can't detach it automatically

How do we clear these stale VolumeAttachment objects and force the release so our pods can mount the volume and recover?

Windows for business | Windows 365 Enterprise
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. HLBui 13,020 Reputation points Independent Advisor
    2026-10-01T18:04:10.1966667+00:00

    Hi Olivia

    I think it caused by a stale VolumeAttachment after an unexpected node failure. Kubernetes still thinks the volume is attached to the failed node, so when the StatefulSet pod gets rescheduled, the storage provider blocks the mount with a Multi-Attach error.

    To recover, first confirm the original node is no longer using the volume, then identify and remove the stale attachment:

    kubectl get volumeattachment

    kubectl delete volumeattachment <volumeattachment-name>

    If the disk is still marked as attached at the infrastructure layer, you may also need to manually detach it there. Once the stale attachment is cleared, Kubernetes should reattach the volume to the new node and the pod should start normally.

    Hope this helps! If you found the answer useful, please hit Accept Answer so it can help others facing the same issue.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.