Technical

Trouble with Node Crashing in Proxmox: A Step-by-Step Diagnostic Checklist

Trouble with Node Crashing in Proxmox: A Step-by-Step Diagnostic Checklist

Trouble with node crashing in Proxmox usually comes down to a few things: bad RAM, a failing disk, or a kernel bug. Work through this checklist and you’ll find it.

Close-up photo of coiled orange and black electrical wires on a wooden utility pole against a gray sky.

Check the logs first

SSH into the node and look at the system journal. The last entries before a crash are the most useful.

journalctl -b -1 -e

That shows the end of the previous boot’s log. If the node hard locked, there might not be anything. But if the kernel panicked, you’ll see the stack trace right there.

Memory problems

Bad RAM is the classic cause of random crashes. Run a memtest from the Proxmox installer ISO. Let it run overnight. If you see errors, replace the stick.

Storage failing

A failing disk can cause I/O errors that hang the whole node. Check SMART data:

smartctl -a /dev/sda

Look for reallocated sectors or pending sectors. Any of those means the drive is on its way out. I’ve had a node crash repeatedly because of a dying SSD that looked fine in the web UI.

A set of black power and data cables neatly arranged on a vivid yellow background.

Kernel issues

Sometimes a kernel update introduces a bug. If crashes started after an update, boot an older kernel from the Proxmox boot menu. If the crashes stop, pin that kernel and report the bug.

Overheating or power

Check temperatures and power supply. A marginal PSU can cause random reboots under load. Clean the dust out and make sure fans are spinning.

My take

Start with logs and RAM. Most of the time it’s one of those. Don’t waste time reinstalling Proxmox until you’ve ruled out hardware. And keep an eye on VPS crashing on Proxmox if it’s a VM that’s crashing, not the whole node.

Leave a comment

Comments are reviewed before they appear. Your email is never published.