linux-kernel - Re: Problem recovering a failed RIAD5 array with 4-drives.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <18070.46997.541325.761868@notabene.brown>
Date:	Fri, 13 Jul 2007 09:21:57 +1000
From:	Neil Brown <neilb@...e.de>
To:	LinuxKernel@...esplace.net
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Problem recovering a failed RIAD5 array with 4-drives.

On Thursday July 12, LinuxKernel@...esplace.net wrote:
> 
> I don't know the original order of the array before all the problems started. 
> 
> Is there a way to determine the original order? 

No, unless you have some old kernel logs of the last time it assembled
the array properly.
The one thing that "--create" does destroy is the information about
any previous array that the drives were a part of.

> 
> The order that --detail is showing now is the order that appeared after 
> issuing the command is it is in the email. (ie: a b c d)

Odd.  I cannot reproduce it.
I suggest you try different arrangements (of the 3 good drives and the
word 'missing') until you find one that 'fsck -n' likes.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/