Fan Speed Critical / Cooling Redundancy Lost
A cooling fan hits a critical speed/fault or loses redundancy, leading to rising GPU temperatures and thermal throttling if not addressed.
A cooling fan hits a critical speed/fault or loses redundancy, leading to rising GPU temperatures and thermal throttling if not addressed.
What this failure is
Fan Speed Critical / Cooling Redundancy Lost is a Infrastructure failure seen during ML training runs. A cooling fan hits a critical speed/fault or loses redundancy, leading to rising GPU temperatures and thermal throttling if not addressed. Common tags: Fan, Cooling, Thermal, Ipmi.
Is this what broke your run? Paste your log.
You're reading about Fan Speed Critical / Cooling Redundancy Lost. Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.
Want 14 days on the Scale plan?
Request an evaluation code. A verified workplace organization activates up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
Fan hardware failure or bearing wear. Blocked airflow / dust. Cooling redundancy lost. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.
What you'll observe
- GPU temperatures climbing on a node
- Fan fault or critical-speed sensor alarm
- Throughput dropping from thermal throttle
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| Fan Speed Critical (sensor) | Fan hardware failure or bearing wear |
| Fan redundancy lost | Blocked airflow / dust |
| Rising GPU temperature with a fan alarm | Cooling redundancy lost |
Which systems are affected
- Air-cooled GPU servers
- Dense 8-GPU chassis
- Nodes with BMC fan telemetry
How to confirm this is the problem
Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.
- ✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
- ✓Verified signal present: Fan Speed Critical (sensor)
- ✓Verified signal present: Fan redundancy lost
- ✓Verified signal present: Rising GPU temperature with a fan alarm
- ✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.
The fix and the prevention pattern
The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card. Daily allowance follows verified trust tier. Instant access.
Diagnose this failure in VS Code
Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.
Install the free VS Code extensionRelated failures to investigate next
Root cause
- Fan hardware failure or bearing wear
- Blocked airflow / dust
- Cooling redundancy lost
The fix and how to prevent it
Evaluate Denpex on your own logs
Request a Scale evaluation code. A verified workplace organization activates 14 days with up to 50 diagnoses a day. Every account keeps its current diagnosis allowance and gets a verification path. No card or automatic subscription.
Don't just read the fix, diagnose your run
The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.
Related Infrastructure errors
Dual ISP BGP Route Withdrawal Causing Complete GPU Cloud Region Outage
Infrastructure · critical
Routine UPS Maintenance Triggering Cascading Power and Cooling Failure Across GPU Cloud Region
Infrastructure · critical
Remediation Storm Prevention via Circuit Breaker Pattern in AutoClusters
Infrastructure · high
Network Storage Volume Causing Process Hangs on H100 GPU Nodes
Infrastructure · high