From ae87f3838c564c39b87305fde5e8cf637d0b5fbd Mon Sep 17 00:00:00 2001
From: counterweight <counterweightoperator@protonmail.com>
Date: Sun, 4 Jan 2026 01:13:15 +0100
Subject: [PATCH] zfs writings

---
 public/index.html                             |  12 ++
 .../a-degraded-pool-with-a-healthy-disk.html  | 133 +++++++++++++
 .../fixing-a-degraded-zfs-mirror.html         | 188 ++++++++++++++++++
 .../why-i-put-my-vms-on-a-zfs-mirror.html     | 120 +++++++++++
 4 files changed, 453 insertions(+)
 create mode 100644 public/writings/a-degraded-pool-with-a-healthy-disk.html
 create mode 100644 public/writings/fixing-a-degraded-zfs-mirror.html
 create mode 100644 public/writings/why-i-put-my-vms-on-a-zfs-mirror.html
diff --git a/public/index.html b/public/index.html
index e4c5a83..1c18d0d 100644
--- a/public/index.html
+++ b/public/index.html
@@ -147,6 +147,18 @@
       <h2 id="writings-header">Writings</h2>
       <p>Sometimes I like to jot down ideas and drop them here.</p>
       <ul>
+        <li>
+          <a href="writings/fixing-a-degraded-zfs-mirror.html" target="_blank"
+            rel="noopener noreferrer">Fixing a Degraded ZFS Mirror: Reseat, Resilver, and Scrub</a>
+        </li>
+        <li>
+          <a href="writings/a-degraded-pool-with-a-healthy-disk.html" target="_blank"
+            rel="noopener noreferrer">A degraded pool with a healthy disk</a>
+        </li>
+        <li>
+          <a href="writings/why-i-put-my-vms-on-a-zfs-mirror.html" target="_blank"
+            rel="noopener noreferrer">Why I Put My VMs on a ZFS Mirror</a>
+        </li>
         <li>
           <a href="writings/a-note-for-the-future-the-tax-bleeding-in-2025.html" target="_blank"
             rel="noopener noreferrer">A note for the future: the tax bleeding in 2025</a>
diff --git a/public/writings/a-degraded-pool-with-a-healthy-disk.html b/public/writings/a-degraded-pool-with-a-healthy-disk.html
new file mode 100644
index 0000000..521b7cc
--- /dev/null
+++ b/public/writings/a-degraded-pool-with-a-healthy-disk.html
@@ -0,0 +1,133 @@
+<!DOCTYPE HTML>
+<html>
+
+<head>
+    <title>Pablo here</title>
+    <meta charset="utf-8">
+    <meta viewport="width=device-width, initial-scale=1">
+    <link rel="stylesheet" href="../styles.css">
+</head>
+
+
+<body>
+    <main>
+        <h1>
+            Hi, Pablo here
+        </h1>
+        <p><a href="../index.html">back to home</a></p>
+        <section>
+            <h2>A degraded pool with a healthy disk</h2>
+            <p><em>Part 2 of 3 in my "First ZFS Degradation" series. See also <a href="why-i-put-my-vms-on-a-zfs-mirror.html">Part 1: The Setup</a> and <a href="fixing-a-degraded-zfs-mirror.html">Part 3: The Fix</a>.</em></p>
+            <h3>The "Oh Shit" Moment</h3>
+            <p>I wasn't even looking for trouble. I was clicking around the Proxmox web UI, exploring some storage views I hadn't noticed before, when I saw it: my ZFS pool was in <strong>DEGRADED</strong> state.</p>
+            <p>I opened the details. One of my two mirrored drives was listed as <strong>FAULTED</strong>.</p>
+            <p>I was very surprised. This box and disks were brand new and didn't even have three months of running on them. I was not expecting HW issues to come at me that fast. I SSH'd into the server and ran the command that would become my best friend over the next 24 hours:</p>
+            <pre><code>zpool status -v proxmox-tank-1</code></pre>
+            <p>No glitch. The pool was degraded. The drive had racked up over 100 read errors, 600+ write errors, and 129 checksum errors. ZFS had given up on it.</p>
+            <pre><code>  NAME                                 STATE     READ WRITE CKSUM
+  proxmox-tank-1                       DEGRADED     0     0     0
+    mirror-0                           DEGRADED     0     0     0
+      ata-ST4000NT001-3M2101_WX11TN0Z  FAULTED    108   639   129  too many errors
+      ata-ST4000NT001-3M2101_WX11TN2P  ONLINE       0     0     0</code></pre>
+            <p>The good news: <code>errors: No known data errors</code>. ZFS was serving all my data from the healthy drive. Nothing was lost yet.</p>
+            <p>The bad news: I was running on a single point of failure. If AGAPITO2 decided to have a bad day too, I'd be in real trouble.</p>
+            <p>I tried the classic IT move: rebooting. The system came back up and ZFS immediately started trying to resilver (rebuild) the degraded drive. But within minutes, the errors started piling up again and the resilver stalled.</p>
+            <p>Time to actually figure out what was wrong.</p>
+            <h3>The Diagnostic Toolbox</h3>
+            <p>When a ZFS drive acts up, you have two main sources of truth: what the <strong>kernel</strong> sees happening at the hardware level, and what the <strong>drive itself</strong> reports about its health. This can be looked up with <code>dmesg</code> and <code>smartctl</code>.</p>
+            <h4>dmesg: The Kernel's Diary</h4>
+            <p>The Linux kernel maintains a ring buffer of messages about hardware events, driver activities, and system operations. The <code>dmesg</code> command lets you read it. For disk issues, you want to grep for SATA-related keywords:</p>
+            <pre><code>dmesg -T | egrep -i 'ata[0-9]|sata|reset|link|i/o error' | tail -100</code></pre>
+            <p>The <code>-T</code> flag gives you human-readable timestamps instead of seconds-since-boot.</p>
+            <p>What I saw was... weird. Here's an excerpt:</p>
+            <pre><code>[Fri Jan  2 22:25:13 2026] ata4.00: exception Emask 0x50 SAct 0x70220001 SErr 0xe0802 action 0x6 frozen
+[Fri Jan  2 22:25:13 2026] ata4.00: irq_stat 0x08000000, interface fatal error
+[Fri Jan  2 22:25:13 2026] ata4.00: failed command: READ FPDMA QUEUED
+[Fri Jan  2 22:25:13 2026] ata4: hard resetting link
+[Fri Jan  2 22:25:14 2026] ata4: SATA link down (SStatus 0 SControl 300)</code></pre>
+            <p>Let me translate: the kernel tried to read from the drive on <code>ata4</code>, got a "fatal error," and responded by doing a hard reset of the SATA link. Then the link went down entirely. The drive just... disappeared.</p>
+            <p>But it didn't stay gone. A few seconds later:</p>
+            <pre><code>[Fri Jan  2 22:25:24 2026] ata4: link is slow to respond, please be patient (ready=0)
+[Fri Jan  2 22:25:24 2026] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)</code></pre>
+            <p>The drive came back! At full speed! But then...</p>
+            <pre><code>[Fri Jan  2 22:25:29 2026] ata4.00: qc timeout after 5000 msecs (cmd 0xec)
+[Fri Jan  2 22:25:29 2026] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
+[Fri Jan  2 22:25:29 2026] ata4: limiting SATA link speed to 3.0 Gbps</code></pre>
+            <p>It failed again. The kernel, trying to be helpful, dropped the link speed from 6.0 Gbps to 3.0 Gbps. Maybe a slower speed would be more stable?</p>
+            <p>It wasn't. The pattern repeated: connect, fail, reset, reconnect at a slower speed. 6.0 Gbps, then 3.0 Gbps, then 1.5 Gbps. Eventually:</p>
+            <pre><code>[Fri Jan  2 22:27:06 2026] ata4.00: disable device</code></pre>
+            <p>The kernel gave up entirely.</p>
+            <p>This wasn't what a dying drive looks like. A dying drive throws read errors on specific bad sectors. This drive was connecting and disconnecting like someone was jiggling the cable. The kernel was calling it "interface fatal error", emphasis on <em>interface</em>.</p>
+            <h4>smartctl: Asking the Drive Directly</h4>
+            <p>Every modern hard drive has S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) — basically a built-in health monitor. The <code>smartctl</code> command lets you get info out of it.</p>
+            <p>First, the overall health check:</p>
+            <pre><code>smartctl -H /dev/sdb</code></pre>
+            <pre><code>SMART overall-health self-assessment test result: PASSED</code></pre>
+            <p>Okay, that looks great. But if the disk is healthy, what the hell is going on, and where are all those errors that ZFS was spotting coming from?</p>
+            <p>Let's dig deeper with the extended info:</p>
+            <pre><code>smartctl -x /dev/sdb</code></pre>
+            <p>The key attributes I was looking for:</p>
+            <table>
+                <thead>
+                    <tr>
+                        <th>Attribute</th>
+                        <th>Value</th>
+                        <th>What it means</th>
+                    </tr>
+                </thead>
+                <tbody>
+                    <tr>
+                        <td>Reallocated_Sector_Ct</td>
+                        <td>0</td>
+                        <td>Bad sectors the drive has swapped out. Zero is good.</td>
+                    </tr>
+                    <tr>
+                        <td>Current_Pending_Sector</td>
+                        <td>0</td>
+                        <td>Sectors waiting to be checked. Zero is good.</td>
+                    </tr>
+                    <tr>
+                        <td>UDMA_CRC_Error_Count</td>
+                        <td>0</td>
+                        <td>Data corruption during transfer. Zero is good.</td>
+                    </tr>
+                    <tr>
+                        <td>Number of Hardware Resets</td>
+                        <td>39</td>
+                        <td>Times the connection has been reset. Uh...</td>
+                    </tr>
+                </tbody>
+            </table>
+            <p>All the sector-level health metrics looked perfect. No bad blocks, no pending errors, no CRC errors. The drive's magnetic platters and read/write heads were fine.</p>
+            <p>But 39 hardware resets? That's not normal. That's the drive (or its connection) getting reset nearly 40 times.</p>
+            <p>I ran the short self-test to be sure:</p>
+            <pre><code>smartctl -t short /dev/sdb
+# Wait a minute...
+smartctl -l selftest /dev/sdb</code></pre>
+            <pre><code># 1  Short offline       Completed without error       00%</code></pre>
+            <p>The drive passed its own self-test. The platters spin, the heads move, the firmware works, and it can read its own data just fine.</p>
+            <h3>Hypothesis</h3>
+            <p>At this point, the evidence was pointing clearly away from "the drive is dying" and toward "something is wrong with the connection."</p>
+            <p>What the kernel logs told me: the drive keeps connecting and disconnecting. Each time it reconnects, the kernel tries slower speeds. Eventually it gives up entirely. This is what you see with an unstable physical connection.</p>
+            <p>What SMART told me: the drive itself is healthy. No bad sectors, no media errors, no signs of wear. But there have been dozens of hardware resets — the connection keeps getting interrupted.</p>
+            <p>The suspects, in order of likelihood:</p>
+            <ol>
+                <li><strong>SATA data cable</strong>: the most common culprit for intermittent connection issues. Cables go bad, or weren't seated properly in the first place.</li>
+                <li><strong>Power connection</strong>: if the drive isn't getting stable power, it might brown out intermittently.</li>
+                <li><strong>SATA port on the motherboard</strong>: less likely, but possible.</li>
+                <li><strong>PSU</strong>: power supply issues could affect the power rail feeding the drive. Unlikely, since both disks where feeding from the same cable tread, but still an option.</li>
+            </ol>
+            <p>Given that I had just built this server a few weeks earlier, and a good part of that happened after midnight... I was beginning to suspect that perhaps I simply might not have plugged in the disk properly.</p>
+            <h3>The Verdict</h3>
+            <p>I was pretty confident now: the drive was fine, but the connection was bad. Most likely the SATA data cable, and most probably simply not connected properly.</p>
+            <p>The fix would require shutting down the server, opening the case, and reseating (or replacing) cables. Before doing that, I wanted to take the drive offline cleanly and document everything.</p>
+            <p>In <a href="fixing-a-degraded-zfs-mirror.html">Part 3</a>, I'll walk through exactly how I fixed it: the ZFS commands, the physical work, and the validation to make sure everything was actually okay afterward.</p>
+            <p><em>Continue to <a href="fixing-a-degraded-zfs-mirror.html">Part 3: The Fix</a> →</em></p>
+            <p><a href="../index.html">back to home</a></p>
+        </section>
+    </main>
+
+</body>
+
+</html>
+
diff --git a/public/writings/fixing-a-degraded-zfs-mirror.html b/public/writings/fixing-a-degraded-zfs-mirror.html
new file mode 100644
index 0000000..e8f1f0a
--- /dev/null
+++ b/public/writings/fixing-a-degraded-zfs-mirror.html
@@ -0,0 +1,188 @@
+<!DOCTYPE HTML>
+<html>
+
+<head>
+    <title>Pablo here</title>
+    <meta charset="utf-8">
+    <meta viewport="width=device-width, initial-scale=1">
+    <link rel="stylesheet" href="../styles.css">
+</head>
+
+
+<body>
+    <main>
+        <h1>
+            Hi, Pablo here
+        </h1>
+        <p><a href="../index.html">back to home</a></p>
+        <section>
+            <h2>Fixing a Degraded ZFS Mirror: Reseat, Resilver, and Scrub</h2>
+            <p><em>Part 3 of 3 in my "First ZFS Degradation" series. See also <a href="why-i-put-my-vms-on-a-zfs-mirror.html">Part 1: The Setup</a> and <a href="a-degraded-pool-with-a-healthy-disk.html">Part 2: Diagnosing the Problem</a>.</em></p>
+            <h3>The Game Plan</h3>
+            <p>By now I was pretty confident about what was wrong: not a dying drive, but a flaky SATA connection. The fix should be straightforward. Just take the drive offline, shut down, reseat the cables, bring it back up, and let ZFS heal itself.</p>
+            <p>But I wanted to do this methodically. ZFS is forgiving, but I didn't want to make things worse by rushing.</p>
+            <p>Here was my plan:</p>
+            <ol>
+                <li>Take the faulty drive offline in ZFS (tell ZFS "stop trying to use this drive")</li>
+                <li>Power down the server</li>
+                <li>Open the case, inspect and reseat cables</li>
+                <li>Boot up, verify the drive is detected</li>
+                <li>Bring the drive back online in ZFS</li>
+                <li>Let the resilver complete</li>
+                <li>Run a scrub to verify data integrity</li>
+                <li>Check SMART one more time</li>
+            </ol>
+            <p>Let's walk through each step.</p>
+            <h3>Step 1: Taking the Drive Offline</h3>
+            <p>Before touching hardware, I wanted ZFS to stop trying to use the problematic drive.</p>
+            <p>First, I set up some variables to avoid typos with that long disk ID:</p>
+            <pre><code>DISKID="ata-ST4000NT001-3M2101_WX11TN0Z"
+DISKPATH="/dev/disk/by-id/$DISKID"</code></pre>
+            <p>Then I took it offline:</p>
+            <pre><code>zpool offline proxmox-tank-1 "$DISKID"</code></pre>
+            <p>Checking the status afterward:</p>
+            <pre><code>zpool status -v proxmox-tank-1</code></pre>
+            <pre><code>  NAME                                 STATE     READ WRITE CKSUM
+  proxmox-tank-1                       DEGRADED     0     0     0
+    mirror-0                           DEGRADED     0     0     0
+      ata-ST4000NT001-3M2101_WX11TN0Z  OFFLINE    108   639   129
+      ata-ST4000NT001-3M2101_WX11TN2P  ONLINE       0     0     0</code></pre>
+            <p>The state changed from FAULTED to OFFLINE. ZFS knows I intentionally took it offline rather than it failing on its own. The error counts are still there as a historical record, but ZFS isn't actively trying to use the drive anymore.</p>
+            <p>Time to shut down and get my hands dirty.</p>
+            <h3>Step 2: Opening the Case</h3>
+            <p>I powered down the server and opened up the Fractal Node 804. This case has a lovely design with drive bays accessible from the side, which I love. No reaching out into weird corners in the case, just unscrew a couple screws, slide the drive bay out and there they are, handy and reachable.</p>
+            <p>I located AGAPITO1 (I had handwritten labels on the drives, lesson learned after many sessions of playing "which drive is which") and inspected the connections.</p>
+            <p>Here's the honest truth: everything looked fine. The SATA data cable was plugged in. The power connector was plugged in. Nothing was obviously loose or damaged. There was a bit of tension in the cable as it moved from one area of the case (where the motherboard is) to the drives area, but I really didn't think that was affecting the connection to either the drive or the motherboard itself.</p>
+            <p>But "looks fine" doesn't mean "is fine". So I did a full reseat:</p>
+            <ul>
+                <li>Unplugged and firmly replugged the SATA data cable at both ends (drive and motherboard).</li>
+                <li>Unplugged and firmly replugged the power connector.</li>
+                <li>While I was in there, checked the connections on the other disk of the mirror as well.</li>
+            </ul>
+            <p>I made sure each connector clicked in solidly. Then I closed up the case and hit the power button.</p>
+            <h3>Step 3: Verifying Detection</h3>
+            <p>The server booted up. Would Linux see the drive?</p>
+            <pre><code>ls -l /dev/disk/by-id/ | grep WX11TN0Z</code></pre>
+            <pre><code>lrwxrwxrwx 1 root root  9 Jan  2 23:15 ata-ST4000NT001-3M2101_WX11TN0Z -> ../../sdb</code></pre>
+            <p>The drive was there, mapped to <code>/dev/sdb</code>.</p>
+            <p>I opened a second terminal and started watching the kernel log in real time:</p>
+            <pre><code>dmesg -Tw</code></pre>
+            <p>This would show me immediately if the connection started acting flaky again. For now, it was quiet, showing just normal boot messages, the drive being detected successfully, etc. Nothing alarming.</p>
+            <h3>Step 4: Bringing It Back Online</h3>
+            <p>Moment of truth. I told ZFS to start using the drive again:</p>
+            <pre><code>zpool online proxmox-tank-1 "$DISKID"</code></pre>
+            <p>Immediately checked the status:</p>
+            <pre><code>zpool status -v proxmox-tank-1</code></pre>
+            <pre><code>  pool: proxmox-tank-1
+ state: DEGRADED
+status: One or more devices is currently being resilvered.
+action: Wait for the resilver to complete.
+  scan: resilver in progress since Fri Jan  2 23:17:35 2026
+        0B resilvered, 0.00% done, no estimated completion time
+
+    NAME                                 STATE     READ WRITE CKSUM
+    proxmox-tank-1                       DEGRADED     0     0     0
+      mirror-0                           DEGRADED     0     0     0
+        ata-ST4000NT001-3M2101_WX11TN0Z  DEGRADED     0     0     0  too many errors
+        ata-ST4000NT001-3M2101_WX11TN2P  ONLINE       0     0     0</code></pre>
+            <p>Two things to notice: the drive's error counters are now at zero (we're starting fresh), and ZFS immediately started resilvering. It shows "too many errors" as the reason for the degraded state, which is historical, it remembers why the drive was marked bad before.</p>
+            <p>I kept watching both the status and the kernel log. No errors, no link resets.</p>
+            <h3>Step 5: The Resilver</h3>
+            <p>Resilvering is ZFS's term for rebuilding redundancy. Copying data from the healthy drive to the one that fell behind. In my case, the drive had been desynchronized for who knows how long (the pool had drifted 524GB out of sync before I noticed), so there was a lot to copy.</p>
+            <p>I shut down my VMs to reduce I/O contention and let the resilver have the disk bandwidth. Progress:</p>
+            <pre><code>scan: resilver in progress since Fri Jan  2 23:17:35 2026
+      495G / 618G scanned, 320G / 618G issued at 100M/s
+      320G resilvered, 51.78% done, 00:50:12 to go</code></pre>
+            <p>The kernel log stayed quiet the whole time. Everything was indicating the cable reseat had worked.</p>
+            <p>I went to bed and let it run overnight. The next morning:</p>
+            <pre><code>scan: resilvered 495G in 01:07:58 with 0 errors on Sat Jan  3 00:25:33 2026</code></pre>
+            <p>495 gigabytes resilvered in about an hour, zero errors. But the pool still showed DEGRADED with a warning about "unrecoverable error." I was very confused about this, but I solved that with some research. Apparently, ZFS is cautious and wants human acknowledgement before declaring everything healthy again.</p>
+            <pre><code>zpool clear proxmox-tank-1 ata-ST4000NT001-3M2101_WX11TN0Z</code></pre>
+            <p>This command clears the error flags. Immediately:</p>
+            <pre><code>  pool: proxmox-tank-1
+ state: ONLINE
+  scan: resilvered 495G in 01:07:58 with 0 errors on Sat Jan  3 00:25:33 2026
+
+    NAME                                 STATE     READ WRITE CKSUM
+    proxmox-tank-1                       ONLINE       0     0     0
+      mirror-0                           ONLINE       0     0     0
+        ata-ST4000NT001-3M2101_WX11TN0Z  ONLINE       0     0     0
+        ata-ST4000NT001-3M2101_WX11TN2P  ONLINE       0     0     0</code></pre>
+            <p>Damn, seeing this felt nice.</p>
+            <h3>Step 6: The Scrub</h3>
+            <p>A resilver copies data to bring the drives back in sync, but it doesn't verify that all the existing data is still good. For that, you run a scrub. ZFS reads every block on the pool, verifies checksums, and repairs anything that doesn't match.</p>
+            <pre><code>zpool scrub proxmox-tank-1</code></pre>
+            <p>I let this run while I brought my VMs back up (scrubs can run in the background without blocking normal operations, though performance takes a hit). A few hours later:</p>
+            <pre><code>scan: scrub repaired 13.0M in 02:14:22 with 0 errors on Sat Jan  3 11:03:54 2026
+
+    NAME                                 STATE     READ WRITE CKSUM
+    proxmox-tank-1                       ONLINE       0     0     0
+      mirror-0                           ONLINE       0     0     0
+        ata-ST4000NT001-3M2101_WX11TN0Z  ONLINE       0     0   992
+        ata-ST4000NT001-3M2101_WX11TN2P  ONLINE       0     0     0</code></pre>
+            <p>Interesting. The scrub repaired 13MB of data and found 992 checksum mismatches on AGAPITO1. From what I read, checksum errors are typically a sign of the disk being in terrible shape and needing a replacement ASAP. That sounds scary, but I took the risk and assumed those were blocks that had been written incorrectly (or not at all) during the period when the connection was flaky, and not an issue with the disk itself. ZFS detected the bad checksums and healed them using the good copies from AGAPITO2.</p>
+            <p>I cleared the errors again and the pool was clean:</p>
+            <pre><code>zpool clear proxmox-tank-1 ata-ST4000NT001-3M2101_WX11TN0Z</code></pre>
+            <h3>Step 7: Final Validation with SMART</h3>
+            <p>One more check. I wanted to see if SMART had anything new to say about the drive after all that activity:</p>
+            <pre><code>smartctl -x /dev/sdb | egrep -i 'overall|Reallocated|Pending|CRC|Hardware Resets'</code></pre>
+            <pre><code>SMART overall-health self-assessment test result: PASSED
+  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
+197 Current_Pending_Sector  -O--C-   100   100   000    -    0
+199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    0
+0x06  0x008  4              41  ---  Number of Hardware Resets</code></pre>
+            <p>Still passing. The hardware reset count went from 39 to 41 — just the reboots I did during this process.</p>
+            <p>For completeness, I ran the long self-test. The short test only takes a minute and does basic checks, the long test actually reads every sector on the disk, which for a 4TB drive takes... a while.</p>
+            <pre><code>smartctl -t long /dev/sdb</code></pre>
+            <p>The estimated time was about 6 hours. In practice, it took closer to 12. Running VMs in parallel probably didn't help.</p>
+            <p>But eventually:</p>
+            <pre><code>SMART Self-test log structure revision number 1
+Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
+# 1  Extended offline    Completed without error       00%      1563         -
+# 2  Short offline       Completed without error       00%      1551         -
+# 3  Short offline       Completed without error       00%      1462         -</code></pre>
+            <p>The extended test passed. Every sector on the disk is readable. The drive is genuinely healthy — it was just the connection that was bad.</p>
+            <h3>Lessons Learned</h3>
+            <ul>
+                <li><strong>ZFS did exactly what it's supposed to do:</strong> Despite 524+ gigabytes of desync and nearly a thousand checksum errors, I lost zero data and was back on action while keeping my VMs running. The healthy drive kept serving everything while the flaky drive was acting up, and once the connection was fixed, ZFS healed itself automatically. Also, I was operating for an unknown amount of time with only one drive. In this case it seems it was due to stupid me messing up cable management, but I'm very happy knowing if the disk had been genuinely faulty, services would have continued just fine.</li>
+                <li><strong>Physical connections matter:</strong> It's easy to not pay that much attention when building a new box. Well, it bites back.</li>
+                <li><strong>Monitor your pools.</strong> I only found this issue by accident, clicking around in the Proxmox UI. The pool had been degraded for who knows how long before I noticed. I'm already working in setting up a monitor to my Uptime Kuma instance so that next time the pool status stops being ONLINE I get notified immediately.</li>
+            </ul>
+            <p>I'm happy I was able to test out recoverying from a faulty disk with such a tiny issue. I learned a lot fixing it, and now I'm even more happy than before having decided to go for this ZFS pool setup.</p>
+            <h3>Quick Reference: The Commands</h3>
+            <p>For future me (and anyone else who ends up here with a degraded pool):</p>
+            <pre><code># Check pool status
+zpool status -v <pool>
+
+# Watch kernel logs in real time
+dmesg -Tw
+
+# Check SMART health
+smartctl -H /dev/sdX
+smartctl -x /dev/sdX
+
+# Take a drive offline before physical work
+zpool offline <pool> <device-id>
+
+# Bring a drive back online
+zpool online <pool> <device-id>
+
+# Clear error flags after recovery
+zpool clear <pool> <device-id>
+
+# Run a scrub to verify all data
+zpool scrub <pool>
+
+# Run SMART self-tests
+smartctl -t short /dev/sdX  # Quick test (~1 min)
+smartctl -t long /dev/sdX   # Full surface scan (hours)
+smartctl -l selftest /dev/sdX  # Check test results</code></pre>
+            <p><em>Thanks for reading! This was <a href="fixing-a-degraded-zfs-mirror.html">Part 3: The Fix</a>. You might also enjoy <a href="why-i-put-my-vms-on-a-zfs-mirror.html">Part 1: The Setup</a> and <a href="a-degraded-pool-with-a-healthy-disk.html">Part 2: Diagnosing the Problem</a>.</em></p>
+            <p><a href="../index.html">back to home</a></p>
+        </section>
+    </main>
+
+</body>
+
+</html>
+
diff --git a/public/writings/why-i-put-my-vms-on-a-zfs-mirror.html b/public/writings/why-i-put-my-vms-on-a-zfs-mirror.html
new file mode 100644
index 0000000..77301cb
--- /dev/null
+++ b/public/writings/why-i-put-my-vms-on-a-zfs-mirror.html
@@ -0,0 +1,120 @@
+<!DOCTYPE HTML>
+<html>
+
+<head>
+    <title>Pablo here</title>
+    <meta charset="utf-8">
+    <meta viewport="width=device-width, initial-scale=1">
+    <link rel="stylesheet" href="../styles.css">
+</head>
+
+
+<body>
+    <main>
+        <h1>
+            Hi, Pablo here
+        </h1>
+        <p><a href="../index.html">back to home</a></p>
+        <section>
+            <h2>Why I Put My VMs on a ZFS Mirror</h2>
+            <p><em>Part 1 of 3 in my "First ZFS Degradation" series. Also read <a href="a-degraded-pool-with-a-healthy-disk.html">Part 2: Diagnosing the Problem</a> and <a href="fixing-a-degraded-zfs-mirror.html">Part 3: The Fix</a>.</em></p>
+            <h3>Why This Series Exists</h3>
+            <p>A few weeks into running my new homelab server, I stumbled upon something I wasn't expecting to see that early: my ZFS pool was in "DEGRADED" state. One of my two mirrored drives had gone FAULTED.</p>
+            <p>This was the first machine I had set up with a ZFS mirror, precisely to be able to deal with disk issues smoothly, without losing data and having downtime. Although it felt like a pain in the ass to spot the problem, I was also happy because it gave me a chance to drill the kind of disk maintenance I was hoping to do in this new server.</p>
+            <p>But here's the thing: when I was in the middle of it, I couldn't find a single resource that walked through the whole experience in detail. Plenty of docs explain what ZFS <em>is</em>. Plenty of forum posts have people asking "help my pool is degraded." But nothing that said "here's what it actually feels like to go through this, step by step, with all the commands and logs and reasoning behind the decisions."</p>
+            <p>So I wrote it down. I took a lot of notes during the process and crafted a more or less organized story from them. This three-part series is for fellow amateur homelabbers who are curious about ZFS, maybe a little intimidated by it, and want to know what happens when things go sideways. I wish I had found a very detailed log like this when I was researching ZFS initially. Hope it helps you.</p>
+            <h3>The server and disks</h3>
+            <p>My homelab server is a modest but capable box I built in late 2025. It has decent consumer hardware, but nothing remarkable. I'll only specify that I have currently three disks on it:</p>
+            <ul>
+                <li><strong>OS Drive</strong>: Kingston KC3000 512GB NVMe. Proxmox lives here.</li>
+                <li><strong>Data Drives</strong>: Two Seagate IronWolf Pro 4TB drives (ST4000NT001). This is where my Proxmox VMs get their disks stored.</li>
+            </ul>
+            <p>The two IronWolf drives are where this story takes place. I labeled them AGAPITO1 and AGAPITO2 because... well, every pair of drives deserves a silly name. I have issues remembering serial numbers.</p>
+            <p>The server runs Proxmox and hosts most of my self-hosted life: personal services, testing VMs, and my Bitcoin infrastructure (which I share over at <a href="https://bitcoininfra.contrapeso.xyz" target="_blank" rel="noopener noreferrer">bitcoininfra.contrapeso.xyz</a>). If this pool goes down, everything goes down.</p>
+            <h3>Why ZFS?</h3>
+            <p>I'll be honest: I didn't overthink this decision. ZFS is the default storage recommendation for Proxmox, it has a reputation for being rock-solid, and I'd heard enough horror stories about silent data corruption to want something with checksumming built in.</p>
+            <p>What I was most interested in was the ability to define RAID setups in software and deal easily with disks going in and out of them. I had never gone beyond the naive "one disk for the OS, one disk for data" setup in previous servers. After having disks failing on me in previous boxes, I decided it was time to gear up and do it proper this time. My main concern initially was just saving time: it's messy when a "simple" host has disk issues, and I hoped mirroring would allow me to invest less time in cleaning up disasters.</p>
+            <h3>Why a Mirror?</h3>
+            <p>When I set up the pool, I had two 4TB drives. That gave me a few options:</p>
+            <ol>
+                <li><strong>Single disk</strong>: Maximum space (8TB usable), zero redundancy. One bad sector and you're crying.</li>
+                <li><strong>Mirror</strong>: Half the space (4TB usable from 8TB raw), but everything is written to both drives. One drive can completely die and you lose nothing.</li>
+                <li><strong>RAIDZ</strong>: Needs at least 3 drives, gives you parity-based redundancy. More space-efficient than mirrors at scale.</li>
+            </ol>
+            <p>I went with the mirror for a few reasons.</p>
+            <p>First, I only had two drives to start with, so RAIDZ wasn't even an option yet.</p>
+            <p>Second, mirrors are <em>simple</em>. Data goes to both drives. If one dies, the other has everything. No parity calculations, no write penalties, no complexity.</p>
+            <p>Third (and this is the one that sold me), <strong>mirrors let you expand incrementally</strong>. With ZFS, you can add more mirror pairs (called "vdevs") to your pool later. You can even mix sizes: start with two 4TB drives, add two 8TB drives later, and ZFS will use all of it. RAIDZ doesn't give you that flexibility; once you set your vdev width, you're stuck with it.</p>
+            <h4>When Would RAIDZ Make More Sense?</h4>
+            <p>If you're starting with 4+ drives and you want to maximize usable space, RAIDZ starts looking attractive:</p>
+            <table>
+                <thead>
+                    <tr>
+                        <th>Configuration</th>
+                        <th>Drives</th>
+                        <th>Usable Space</th>
+                        <th>Fault Tolerance</th>
+                    </tr>
+                </thead>
+                <tbody>
+                    <tr>
+                        <td>Mirror</td>
+                        <td>2</td>
+                        <td>50%</td>
+                        <td>1 drive</td>
+                    </tr>
+                    <tr>
+                        <td>RAIDZ1</td>
+                        <td>3</td>
+                        <td>~67%</td>
+                        <td>1 drive</td>
+                    </tr>
+                    <tr>
+                        <td>RAIDZ1</td>
+                        <td>4</td>
+                        <td>75%</td>
+                        <td>1 drive</td>
+                    </tr>
+                    <tr>
+                        <td>RAIDZ2</td>
+                        <td>4</td>
+                        <td>50%</td>
+                        <td>2 drives</td>
+                    </tr>
+                    <tr>
+                        <td>RAIDZ2</td>
+                        <td>6</td>
+                        <td>~67%</td>
+                        <td>2 drives</td>
+                    </tr>
+                </tbody>
+            </table>
+            <p>RAIDZ2 is popular for larger arrays because it can survive <em>two</em> drive failures, which matters more as you add drives (more drives = higher chance of one failing during a resilver).</p>
+            <p>But for a two-drive homelab that might grow to four drives someday, I felt a mirror was the right call. I can always add another mirror pair later.</p>
+            <h3>The Pool: proxmox-tank-1</h3>
+            <p>My ZFS pool is called <code>proxmox-tank-1</code>. Here's what it looks like when everything is healthy:</p>
+            <pre><code>  pool: proxmox-tank-1
+ state: ONLINE
+config:
+
+    NAME                                 STATE     READ WRITE CKSUM
+    proxmox-tank-1                       ONLINE       0     0     0
+      mirror-0                           ONLINE       0     0     0
+        ata-ST4000NT001-3M2101_WX11TN0Z  ONLINE       0     0     0
+        ata-ST4000NT001-3M2101_WX11TN2P  ONLINE       0     0     0</code></pre>
+            <p>That's it. One pool, one mirror vdev, two drives. The drives are identified by their serial numbers (the <code>WX11TN0Z</code> and <code>WX11TN2P</code> parts), which is important — ZFS uses stable identifiers so it doesn't get confused if Linux decides to shuffle around <code>/dev/sda</code> and <code>/dev/sdb</code>.</p>
+            <p>All my Proxmox VMs store their virtual disks on this pool. When I create a new VM, I point its storage at <code>proxmox-tank-1</code> and ZFS handles the rest.</p>
+            <h3>What Could Possibly Go Wrong?</h3>
+            <p>Everything was humming along nicely. VMs were running fine and I was feeling pretty good about my setup.</p>
+            <p>Then, a few weeks in, I was poking around the Proxmox web UI and noticed something that caught my eye.</p>
+            <p>The ZFS pool was DEGRADED. One of my drives — AGAPITO1, serial <code>WX11TN0Z</code> — was FAULTED.</p>
+            <p>In <a href="a-degraded-pool-with-a-healthy-disk.html">Part 2</a>, I'll walk through how I diagnosed what was actually wrong. Spoiler: the drive itself was fine. The problem was much dumber than that.</p>
+            <p><em>Continue to <a href="a-degraded-pool-with-a-healthy-disk.html">Part 2: Diagnosing the Problem</a></em></p>
+            <p><a href="../index.html">back to home</a></p>
+        </section>
+    </main>
+
+</body>
+
+</html>
+

Attribute	Value	What it means
Reallocated_Sector_Ct	0	Bad sectors the drive has swapped out. Zero is good.
Current_Pending_Sector	0	Sectors waiting to be checked. Zero is good.
UDMA_CRC_Error_Count	0	Data corruption during transfer. Zero is good.
Number of Hardware Resets	39	Times the connection has been reset. Uh...
Configuration	Drives	Usable Space	Fault Tolerance
Mirror	2	50%	1 drive
RAIDZ1	3	~67%	1 drive
RAIDZ1	4	75%	1 drive
RAIDZ2	4	50%	2 drives
RAIDZ2	6	~67%	2 drives