Home Lab · · 2 min read
Building a home NAS on OpenMediaVault and ZFS RAID-Z1
Why I chose ZFS, what RAID-Z1 does and doesn’t protect you from, and the habits that keep a home NAS trustworthy.
Every home lab eventually needs somewhere safe to put data. Mine is a network-attached storage server running OpenMediaVault on a ZFS RAID-Z1 pool, with remote access and automated backups. It’s the foundation the rest of my lab — including self-hosted family photos — sits on.
Why OpenMediaVault for a home NAS?
OpenMediaVault is a Debian-based NAS distribution with a clean web interface for shares, users, services and monitoring. It stays out of the way, runs well on modest hardware, and when you need something the UI doesn’t offer, it’s still just Linux underneath. ZFS support comes via the plugin ecosystem.
Why use ZFS?
ZFS is a filesystem and volume manager in one, and it’s built around a single idea: never trust the disk.
- Checksums on everything. Every block is checksummed, so silent corruption (“bit rot”) is detected instead of quietly served back to you.
- Self-healing. With redundancy, a corrupted block is repaired from a good copy automatically.
- Copy-on-write snapshots. Near-instant, space-efficient snapshots make “I deleted the wrong folder” a non-event.
- Compression that is usually a free win in both space and throughput.
What does RAID-Z1 protect you from, and what doesn’t it?
RAID-Z1 stripes data across disks with one disk’s worth of parity. You can lose any single disk and keep running. With n disks you get roughly n − 1 disks of usable capacity — a good balance of space and safety for a home lab.
It’s important to be clear-eyed about the trade-offs:
- One failure of tolerance. While a failed disk is being replaced and the pool rebuilds (“resilvers”), a second failure means data loss. With very large disks, resilvers take a long time, which is why bigger pools often move to RAID-Z2.
- RAID is not a backup. Redundancy protects against a disk dying. It does nothing against accidental deletion, ransomware, a failed power supply taking out several disks, or a house fire.
How do you keep a home NAS trustworthy?
The filesystem is only half the story. The other half is operational discipline, the same as in production:
- Scheduled scrubs read every block and verify checksums, catching problems while redundancy can still fix them.
- Automatic snapshots on a schedule, with retention, for fast local recovery.
- Backups off the box for the data that matters — snapshots and parity live on the same hardware they’re protecting.
- Disk health monitoring with SMART alerts, so a failing disk is replaced before it fails completely.
- Test restores. A backup you’ve never restored is a hope, not a backup.
The takeaway
Durability is a process, not a product.
That’s as true for a home NAS as it is for a company’s production database. Choosing ZFS was the easy part. Scrubs, snapshots, off-site copies and tested restores are what make the data actually safe.