Hardware

I cover the groundwork behind my ZFS storage strategy on Proxmox VE, including the hardware I am working with, how I balance performance, reliability, and capacity. The core ZFS concepts that influence my design and outline how different storage tiers serve different workloads in my homelab. This is less about “how to install ZFS” and more about planning thestorage architecture that fits my Proxmox workloads.

Or When SAS Drives Bite Back Or Debugging Slow Burn-In Tests in a Proxmox/ZFS Homelab. The issue I hit during a burn-in process for cheap ex-datacenter SAS HDDs, what I assumed was happening, what was actually happening, and how I confirmed and fixed it

How I fixed the issue with non-intel trasceiver not working with Intel X520 network card. Intel trying to be smart and how to tell the card to get over itself.

I see the need for home automation. Well…I would like to explore this technology and make it work for me. There are so many options and there are some very expensive options, not just cost but in privacy and closed ecosystem risks.

Always use the graceful method unless absolutely necessary.  i.e don’t just yank the power cord out. There is console less method and a CLI method over the network

IPMI is more then a way to access servers over the network without them powered up (lights out, out of band etc). It is an Intelligent Platform Management Interface, it can be used to interface with the hardware layer in ways the OS can’t. Let’s use it to control some fans.

Hosting a virtual machine inside a virtual machine KVM trickery for conceptualisation and testing. If your server/host supports VT-x, it goes to say so should the guests.

After having a running battle with my, what turns out, cheap Chinese CSR clone bluetooth USB adaptor (maybe more on that in another post). I purchased a more expensive adaptor…