Skip to content

Power Supply Failure / Redundancy Lost

A node power supply fails or loses redundancy, risking a hard node-down event mid-training; sensor telemetry gives early warning before the node drops.

Quick answer

A node power supply fails or loses redundancy, risking a hard node-down event mid-training.

Infrastructure#power-supply#psu#ipmi#infrastructure#hardware

What this failure is

Power Supply Failure / Redundancy Lost is a Infrastructure failure seen during ML training runs. A node power supply fails or loses redundancy, risking a hard node-down event mid-training; sensor telemetry gives early warning before the node drops. Common tags: Power Supply, Psu, Ipmi, Infrastructure.

Live diagnosis, no signup

Is this what broke your run? Paste your log.

You're reading about Power Supply Failure / 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.

training_logs.txt
No log to hand? Try one:

3 free diagnoses/day

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.

Evaluate one incident

Why it happens (the mechanism)

PSU hardware failure. Power feed / PDU issue. Thermal or load stress on the supply. 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

  • Node at risk of sudden power loss
  • PSU redundancy lost (running on one supply)
  • Power-related sensor alarms

Common symptoms and what they mean

SymptomWhy it happens
Power Supply Failure detected (BMC/IPMI sensor)PSU hardware failure
PSU redundancy lostPower feed / PDU issue
Voltage/current sensor out of rangeThermal or load stress on the supply

Which systems are affected

  • GPU servers with redundant PSUs
  • Dense power-hungry 8-GPU nodes
  • Clusters with BMC/IPMI 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: Power Supply Failure detected (BMC/IPMI sensor)
  • Verified signal present: PSU redundancy lost
  • Verified signal present: Voltage/current sensor out of range
  • 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 analysis

No 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 extension

Root cause

  • PSU hardware failure
  • Power feed / PDU issue
  • Thermal or load stress on the supply

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.

We send a single-use code tied to that address. Static provider and TLD rules do not reject valid addresses. Account trust determines the benefit after signup.

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.