<?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>Raid5 on BAFM</title><link>https://christian.blog.pakiheim.de/tags/raid5/</link><description>Recent content in Raid5 on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Mon, 29 Dec 2008 17:55:17 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/raid5/index.xml" rel="self" type="application/rss+xml"/><item><title>More MD weirdness</title><link>https://christian.blog.pakiheim.de/posts/2008-12-29_more-md-weirdness/</link><pubDate>Mon, 29 Dec 2008 17:55:17 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1337</guid><description>&lt;p&gt;Well, at last I&amp;rsquo;m getting somewhere with my troubles. This only seems to be happening when creating an RAID5 multiple device with four disks, this doesn&amp;rsquo;t happen with three.&lt;/p&gt;
&lt;p&gt;Now, the next thing I tried was to create a three disk array, and then adding the fourth disk as spare and then extending the array with that fourth disk. After that, all these errors seem to appear again &lt;em&gt;&lt;strong&gt;yuck&lt;/strong&gt;&lt;/em&gt; So I either possess rather faulty disks, or something else is fishy, since I&amp;rsquo;m having another four disk RAID5 array with the old disks &amp;hellip;&lt;/p&gt;</description></item></channel></rss>