#homelab
- The graphs came back, and that proved nothingI moved Grafana and Prometheus to a new VM and every panel drew straight away. A graph only draws what's there. It can't tell you what's gone.
- A memory limit made Grafana hammer the diskGrafana stalled for minutes while the host had more than 4 GB of memory available. The clue that it was starving for memory was the NVMe reading 1.7 GB a second.
My NAS was doing a server's job, so I bought it a serverMy ZimaBoard was holding my photos, my documents, my monitoring and my AI agents in 7.5 GiB. The agents were the reason the fix had to be a second machine.- Railway shows my request counts but won't export themRailway's dashboard knows how many requests my app served, but there's nothing for Prometheus to scrape. Turning its per-minute figures into a counter goes wrong three ways.
- The 03:37 alert that was never sentMy monitoring pinned a 3am outage on Cloudflare within seconds, and my notes said my phone was paged at 03:37. Nothing had been sent, ever.
- The folder on the RAID that wasn'tMy photo library was on the one drive with no mirror. The obvious folder to move it to, on the mirror, was a symlink straight back to the photos.
- Every site is monitored twiceI set up uptime monitoring for my sites and nearly made every check meaningless. They all sit behind Cloudflare, and a plain HTTP check there proves that Cloudflare answered, not that my app is alive.
- Homepage kept showing My First GroupI replaced the example config on my Homepage dashboard and the page source still showed the examples. It survived a full container recreate, because it was never my config to begin with.
- One character in /etc/shadow locked me outA fresh container refused my SSH key with Permission denied (publickey). The key was right, the sshd config was right, and the account had a single exclamation mark where it needed an asterisk.
- The Tailscale login that could never finishI installed Tailscale in a container, approved the login link, watched the node appear in my tailnet, and then watched it sit offline. It had sixty seconds to log in, and a browser login takes longer than that.
- The ZimaOS update the updater never offeredMy ZimaBoard had been running an eight-month-old alpha since January, and the built-in updater said there was nothing newer. There was. Getting to it meant learning what 100% on the root filesystem actually means on this box.
- When RAID1 saved the data but not the stateA homelab migration filled the system disk and the storage layer lost track of a perfectly healthy array. Here is why I wiped and rebuilt from backup instead of recovering in place.