I’ve already written about my PDU suddenly dying — and in that post I explained that I was going to do some changes to the homelab power layout. It’s time to do those changes 🙂
Another ZFS pool expansion
It’s time for another ZFS pool expansion. When I last expanded; I doubled the capacity of my 2nd vdev — going from 16 TB to 32 TB raw capacity. This time I’m doubling again — replacing the last limiting drive, and fully utilizing the all the 8 TB drives 😃
Scheduled S.M.A.R.T. scans
I’ve been planning to enable scheduled S.M.A.R.T. scans ever since I built my file server, but it was just one of those things that I never got around to do.
Well — when one of the 8 TB drives suddenly started reporting S.M.A.R.T. errors, the scheduled scans got back on the agenda. So let’s do that now 👇
The homelab PDU died!
My homelab PDU suddenly died! It’s dead, D-E-D, dead! There are few things worse than a server rack suddenly going completely silent…
The PDU has had an error since the power outage last summer — F11 means Power fail on auxiliary 1. Which is an odd error for a PDU with only one input. And; it wasn’t possible to clear or reset it it 😕
PowerWalker UPS, NUT, and Home Assistant
I’m using a Raspberry Pi to communicate with the power equipment in my homelab rack; the UPS, ATS and PDU. For the UPS, I’m using NUT (Network UPS Tools), and for the ATS and PDU; my own PowerWalker Python library.
In this post I’ll be going through how I’ve set up the NUT server to communicate with my PowerWalker VI 1500 RT HID UPS, and NUT clients running on all other physical machines in the rack.