From e2af0b5a7549cad199c4a19443b8e1551008bfbe Mon Sep 17 00:00:00 2001 From: counterweight Date: Sat, 21 Feb 2026 12:16:31 +0100 Subject: [PATCH] new zfs article --- public/writings/replacing-a-failed-disk-in-a-zfs-mirror.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/public/writings/replacing-a-failed-disk-in-a-zfs-mirror.html b/public/writings/replacing-a-failed-disk-in-a-zfs-mirror.html index 238c640..a884e5f 100644 --- a/public/writings/replacing-a-failed-disk-in-a-zfs-mirror.html +++ b/public/writings/replacing-a-failed-disk-in-a-zfs-mirror.html @@ -55,7 +55,7 @@ errors: No known data errors 
SMART overall-health self-assessment test result: PASSED

If this says anything other than PASSED, stop and deal with that first. You don't want to discover your only remaining copy of data is on a failing drive while you're in the middle of hardware work.

Once you've got your reference snapshots, shut down the server gracefully:

- 
shutdown -h now
+ 
shutdown now

Physical installation

I won't write a hardware installation tutorial, every case and drive bay is different. But a few practical tips for homelabbers doing this for the first time:

@@ -188,7 +188,7 @@ dmesg -T | grep -E 'ata[0-9]+\.[0-9]+: ATA-|ata[0-9]+: SATA link up' smartctl -H /dev/disk/by-id/<surviving-disk-id> # Shut down -shutdown -h now +shutdown now # --- After boot with new drive ---