<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>RAID on Endemics blog</title><link>https://endemics.github.io/tags/raid/</link><description>Recent content in RAID on Endemics blog</description><generator>Hugo -- 0.164.0</generator><language>en-gbh</language><lastBuildDate>Mon, 08 Jun 2026 10:58:28 +0000</lastBuildDate><atom:link href="https://endemics.github.io/tags/raid/index.xml" rel="self" type="application/rss+xml"/><item><title>Bringing a Degraded mdadm RAID1 Back From the Brink</title><link>https://endemics.github.io/posts/raid1-recovery/</link><pubDate>Mon, 08 Jun 2026 10:58:28 +0000</pubDate><guid>https://endemics.github.io/posts/raid1-recovery/</guid><description>&lt;p&gt;A war story about a failed RAID1 mirror, a stubborn superblock, a colon in an array name, a cable knocked loose mid-rebuild, and five bad sectors hiding in — of all things — a rescue image. If you&amp;rsquo;ve ever stared at &lt;code&gt;add new device failed ... Invalid argument&lt;/code&gt; and wondered what you broke, this one&amp;rsquo;s for you.&lt;/p&gt;
&lt;p&gt;Claude helped a lot, both during the diagnostic, and to write down this post. At this stage, hallucinations are shared and unvoluntary.&lt;/p&gt;</description></item></channel></rss>