<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Slash Dot Dash: Repairing a RAID5 software array (Debian Linux)</title>
    <link>http://www.slashdotdash.net/articles/2006/04/12/repairing-a-raid5-software-array-debian-linux</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Rolling on Rails</description>
    <item>
      <title>Repairing a RAID5 software array (Debian Linux)</title>
      <description>&lt;p&gt;&lt;span class="caps"&gt;RAID5&lt;/span&gt; software arrays in Linux are very simple to setup and should run smoothly. Inevitably something will go wrong &amp;#8211; but luckily that&amp;#8217;s why we use &lt;span class="caps"&gt;RAID5&lt;/span&gt; &amp;#8211; there should be no data loss.&lt;/p&gt;


	&lt;p&gt;&lt;a href="http://www.tldp.org/HOWTO/Software-RAID-HOWTO-6.html"&gt;Software &lt;span class="caps"&gt;RAID HOWTO&lt;/span&gt;&lt;/a&gt; is the best reference.&lt;/p&gt;


	&lt;h3&gt;Check the &lt;span class="caps"&gt;RAID&lt;/span&gt;&lt;/h3&gt;


	&lt;p&gt;Identify the problematic disk [UU_]&lt;/p&gt;


&lt;pre&gt;
mdadm --detail /dev/md0
cat /proc/mdstat
&lt;/pre&gt;

	&lt;h3&gt;Remove failed disk&lt;/h3&gt;


&lt;pre&gt;
mdadm /dev/md0 -r /dev/hdg1
&lt;/pre&gt;

	&lt;h3&gt;Add new disk&lt;/h3&gt;


&lt;pre&gt;
mdadm /dev/md0 -a /dev/hdg1
&lt;/pre&gt;

Once rebuilding has started you can check the status via &lt;code&gt;/proc/mdstat&lt;/code&gt; (depending on the array size it may take &lt;em&gt;quite a long time&lt;/em&gt;).
&lt;pre&gt;
cat /proc/mdstat 
Personalities : [raid5] 
md0 : active raid5 hdg1[3] hdc1[0] hde1[1]
      488391680 blocks level 5, 128k chunk, algorithm 2 [3/2] [UU_]
      [&amp;gt;....................]  recovery =  0.8% (2098944/244195840) finish=205.3min speed=19648K/sec
unused devices: &amp;lt;none&amp;gt;
&lt;/pre&gt;</description>
      <pubDate>Wed, 12 Apr 2006 20:35:00 +0100</pubDate>
      <guid isPermaLink="false">urn:uuid:48b60b0aff08cc7904ba7c820cc47b3e</guid>
      <author>ben@slashdotdash.net (Ben)</author>
      <link>http://www.slashdotdash.net/articles/2006/04/12/repairing-a-raid5-software-array-debian-linux</link>
      <category>Linux</category>
      <trackback:ping>http://www.slashdotdash.net/articles/trackback/11</trackback:ping>
    </item>
    <item>
      <title>"Repairing a RAID5 software array (Debian Linux)" by J.Mihai</title>
      <description>&lt;p&gt;ARRAY /dev/md3 level=raid1 num-devices=2 UUID=d283bdbd:59f02745:4c4994b8:108272b3
devices=/dev/hdg1,/dev/hdi1
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=d9eb7b7d:b28c104c:b4cd8d68:1bd6c74a
devices=/dev/hdc5,/dev/hde5
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=3806599e:2c4c79bf:a6f675bc:d44a4561
devices=/dev/hdc6,/dev/hde6&lt;/p&gt;


	&lt;p&gt;Is it the same case ?&lt;/p&gt;</description>
      <pubDate>Wed, 26 Dec 2007 17:09:24 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:c5398e57-b26c-496e-95b0-2d1e9f77c024</guid>
      <link>http://www.slashdotdash.net/articles/2006/04/12/repairing-a-raid5-software-array-debian-linux#comment-322</link>
    </item>
  </channel>
</rss>
