> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why is my node drained or cordoned?

A Slurm node enters `drained` state when it stops accepting new jobs. The drain reason (visible in `scontrol show node` or through the `sn`, `dl`, and `dld` aliases on the login Pod) identifies the cause.

For the full drain workflow, the list of common drain reasons (`NHC: [REASON]`, `prolog pre-hook failed`, `scheduler: k8s pod deletion timeout`, `batch job complete failure`, and the `k8s:*` family), the manual undrain procedure, and the `sunk:verify-undrain` automation marker, see [Drain and undrain Slurm nodes](https://docs.coreweave.com/products/sunk/manage_sunk/drain-and-undrain-nodes.md).

If the reason is `NHC: check_file_test: -e /dev/infiniband returned 1` and the node drains, undrains, and drains again, see [Why does my node keep draining for a missing InfiniBand device?](https://docs.coreweave.com/support/sunk/articles/why-does-my-node-keep-draining-for-a-missing-infiniband-device).

[Contact CoreWeave support](https://docs.coreweave.com/support/contact.md) if a node remains drained for an extended period or if the drain reason is not listed in the canonical doc.

***

[Nodes](https://docs.coreweave.com/support/sunk/tags/nodes.md)[Server Errors](https://docs.coreweave.com/support/sunk/tags/server-errors.md)
