Urgent.News

What's breaking now, across thousands of outlets.

Tech

Proxmox on a 5400rpm HDD: why every reboot gave me 15 minutes of 502s

On 28 August 2026 I couldn't log into my AI agent's dashboard. While I was looking into it, the Proxmox node it runs on patched itself and rebooted. Which turned out to be handy, because it showed me the actual problem, and it wasn't the dashboard. What happened At 09:05:37 the node ran apt-get dist-upgrade . That's my deliberate patching path, not an accident. It took Proxmox VE from 9.2.2 to…

On 28 August 2026, the author could not log into their AI agent's dashboard on a Proxmox node. The issue was discovered when the node rebooted after patching itself at 09:05:37, moving from version 9.2.2 to 9.2.11. The dashboard took about 15 minutes to serve a single request, while the agent's server showed a hung state with processes in the D state, waiting on the disk.

The author identified the issue as heavy I/O contention on a single 5400rpm HDD hosting five containers. Stopping the heaviest container, Langfuse, resolved the issue, with the dashboard coming back up in 21 seconds. A slow boot also led to issues with the gateway watchdog and systemd-journal-flush service. The author's main takeaway is to avoid running heavy guests on a single spinning disk and to test watchdogs under slow boot conditions.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Wednesday 18 November →