<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Raid on blog.iankulin.com</title><link>https://blog.iankulin.com/tags/raid/</link><description>Recent content in Raid on blog.iankulin.com</description><generator>Hugo</generator><language>en-AU</language><lastBuildDate>Tue, 04 Apr 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.iankulin.com/tags/raid/index.xml" rel="self" type="application/rss+xml"/><item><title>RAID Rescue</title><link>https://blog.iankulin.com/raid-rescue/</link><pubDate>Tue, 04 Apr 2023 00:00:00 +0000</pubDate><guid>https://blog.iankulin.com/raid-rescue/</guid><description>&lt;p&gt;I&amp;rsquo;m in the process of shuffling disks around as I move towards my 3-2-1 storage arrangements. I thought after my extensive rsync adventures I&amp;rsquo;d mirrored everything everywhere, but then realised, with a sinking (no pun) feeling, after I&amp;rsquo;d repurposed a drive out of the 2 drive Synology as a USB caddy drive and wiped it, that I&amp;rsquo;d forgotten my audio book directory. All my rsync fiddling around had been on the video subdirectory of the media folder, not the whole media directory that included my audiobooks.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s not the end of the world if I&amp;rsquo;d wiped them, I&amp;rsquo;ve just been working through downloading them from Audible and de-drming, so I could do that again in the few days I&amp;rsquo;ve got left till my subscription cancellation date comes around. That was a painful and slow process, so I don&amp;rsquo;t really want to.&lt;/p&gt;
&lt;p&gt;I still had one of the RAID drives that hadn&amp;rsquo;t been wiped, so in theory it should have a full copy of the data, and if I put it back in the Synology by itself it should work. That would be the same situation as if one drive in the RAID pool had died completely.&lt;/p&gt;
&lt;p&gt;A few screws, and a drive swap later and I&amp;rsquo;m looking at this:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://blog.iankulin.com/images/screen-shot-2023-03-31-at-4.35.40-pm-copy.jpg" alt=""&gt;&lt;/p&gt;
&lt;p&gt;There must be a tiny bit of storage in the Synology, so it knows I&amp;rsquo;ve been fiddling around. I hit &lt;em&gt;Recover&lt;/em&gt;, and it did the ten minute thing that I assume is it downloading and installing the new DSM.&lt;/p&gt;
&lt;p&gt;During this process, it started beeping in a plaintive way. I couldn&amp;rsquo;t access with the old Tailscale address, so I fired up the IP address to the web interface, logged in with the old credentials and was greeted with this:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://blog.iankulin.com/images/screen-shot-2023-03-31-at-4.08.58-pm.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;It was not happy working in the degraded state, but the files were all still there, I was able to mount it to the other NAS and copy my files out. A success. The Tailscale package was still installed, so perhaps that business at the beginning was not really a new install of DSM, but some sort of checking.&lt;/p&gt;
&lt;p&gt;This was a good experience, it is worthwhile to test these scenarios, and I&amp;rsquo;m reassured to discover the audible beeping when the RAID pool was degraded. At the moment while I get everything sorted I&amp;rsquo;m in the web interfaces a lot, but the dream is this learning and setup time comes to an end and I just consume my self-hosted services without much manual intervention. In that scenario, some un-ignorable beeping when the NAS needs attention is a good thing.&lt;/p&gt;</description></item></channel></rss>