From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mathias Mueller <raidfail@gmx.de>
Subject: Re: broken raid level 5 array caused by user error
Date: Wed, 11 Nov 2015 18:53:08 +0100
Message-ID: <a7d58e8e4c319c320bc531b8d2bf11e7@pingofdeath.de>
References: <3c05d813e42324cdf95989784f6d7b17@pingofdeath.de>
 <56426499.8000205@turmel.org>
 <ceee2de5aba3ca77efc1146e19896b90@pingofdeath.de>
 <564284F5.9080409@turmel.org>
 <b0cdddd4394bbc1356980bb61ac199c3@pingofdeath.de>
 <56429326.5030405@turmel.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-raid-owner@vger.kernel.org>
In-Reply-To: <56429326.5030405@turmel.org>
Sender: linux-raid-owner@vger.kernel.org
To: Phil Turmel <philip@turmel.org>
Cc: Linux raid <linux-raid@vger.kernel.org>
List-Id: linux-raid.ids

Hi Phil,

> So, I fully expected one of those first four combinations to work.  I
> don't know why they didn't.
> 
> The fsck version dates to 2013, so it might be something related to
> that.  My next step would be to try all of this after booting into a
> modern environment, like the rescue cd from sysrescuecd.org.  Recheck
> serial numbers and device names again, if you do that.

I tried the first four combinations with latest sysrescuecd, but the 
results are the same.

Mathias