From: James <LinuxKernel@jamesplace.net>
To: linux-kernel@vger.kernel.org
Cc: Neil Brown <neilb@suse.de>
Subject: Re: Problem recovering a failed RIAD5 array with 4-drives. --RESOLVED
Date: Thu, 12 Jul 2007 19:49:08 -0500 [thread overview]
Message-ID: <200707121949.08662.LinuxKernel@jamesplace.net> (raw)
In-Reply-To: <18070.46997.541325.761868@notabene.brown>
> >
> > 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
>
>
I don't understand how the order of --detail was different than the command
line on my system, however....
YOU ARE A LIFE SAVER!!!
After going through 21 combinations, beginning to lose all hope and plummeting
into eternal despair, combo 22 worked. The array is up and working. All the
data (1.3Tb) is there and I'm probably the happiest character on the mail
list today.
Thanks a bunch for your help.
next prev parent reply other threads:[~2007-07-13 0:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 13:49 Problem recovering a failed RIAD5 array with 4-drives James
2007-07-12 16:44 ` Lennart Sorensen
2007-07-12 20:21 ` James
2007-07-12 21:41 ` Phil Turmel
2007-07-12 22:48 ` Neil Brown
2007-07-12 23:10 ` James
2007-07-12 23:21 ` Neil Brown
2007-07-13 0:49 ` James [this message]
2007-07-16 15:04 ` Problem recovering a failed RIAD5 array with 4-drives. --RESOLVED David Greaves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707121949.08662.LinuxKernel@jamesplace.net \
--to=linuxkernel@jamesplace.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox