counterweight/pablohere
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

stuffy stuff

Browse source
This commit is contained in:
counterweight 2026-05-16 16:47:31 +02:00
parent 9a39fb33d5
commit 1f8608f25f
Signed by: counterweight
GPG key ID: 883EDBAA726BD96C
25 changed files with 69 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
public/writings/replacing-a-failed-disk-in-a-zfs-mirror.html
View file

@ -17,6 +17,7 @@
<p><a href="../index.html">back to home</a></p>
<section>
<h2>Replacing a Failed Disk in a ZFS Mirror</h2>
<p><em>Published: 2026-02-21</em></p>
<p>If you've been following along, you know the story: I set up a <a href="why-i-put-my-vms-on-a-zfs-mirror.html">ZFS mirror for my Proxmox VMs</a>, then one of the drives <a href="a-degraded-pool-with-a-healthy-disk.html">started acting flaky</a>, and I <a href="fixing-a-degraded-zfs-mirror.html">diagnosed and fixed what turned out to be a bad SATA connection</a>.</p>
<p>Well, the connection wasn't the whole story. A few weeks after that fix, the same drive, AGAPITO1, started dropping off again. Same symptoms: link resets, speed downgrades, kernel giving up on the connection. I went through the cable swap dance again, tried different SATA ports on the motherboard, tried different cables. Nothing helped. The SATA PHY on the drive itself was failing.</p>
<p>I contacted PcComponentes (where I bought it), RMA'd the drive, and ran degraded on AGAPITO2 alone for about two weeks. Then the replacement arrived. This article covers the process of physically installing a new drive and getting it into the ZFS mirror, from "box on the desk" to "pool healthy, mirror whole."</p>