From: Wols Lists <antlists@youngman.org.uk>
To: Glenn Greibesland <glenngreibesland@gmail.com>,
linux-raid@vger.kernel.org
Cc: Phil Turmel <philip@turmel.org>, NeilBrown <neilb@suse.com>
Subject: Re: Raid6 recovery
Date: Fri, 20 Mar 2020 19:15:07 +0000 [thread overview]
Message-ID: <5E75163B.2050602@youngman.org.uk> (raw)
In-Reply-To: <CA+9eyijuUEJ7Y8BuxkKaZ=v8zbPpwixOezngPjtJzaLsBd+A4Q@mail.gmail.com>
On 19/03/20 19:55, Glenn Greibesland wrote:
> After a bit of digging in the manual and on different forums I have
> concluded that the next step for me is to recreate the array using
> –assume-clean and –data-offset=variable.
> I have tried a dry run of the command (answering no to “Continue
> creating array”), and mdadm accepts the parameters without any errors:
Oh my god NO!!!
Do NOT use --create unless someone rather more experienced than me tells
you to!!!
The obvious thing is to somehow get the sixteen drives that you know
should be okay, re-assembled in a forced manner. The --re-add should not
have done any real damage because, as mdadm keeps complaining, you
didn't have enough drives so it won't have touched the data on that
drive. Unfortunately, my fu isn't good enough to tell you how to get
that drive back in.
What's wrong with the two failed drives? Can you ddrescue them? They
might be enough to get you going again.
You say you've read the web page "Raid recovery" - which says it's
obsolete and points you at "When things go wrogn" - but you don't appear
to have read that! PLEASE read "asking for help" and in particular you
NEED to run lsdrv and give us that information. Without that, if you DO
run --create, you will be in for a world of hurt.
I know you may feel it's asking for loads of information, and the
resulting email will be massive, but trust me - the experts will look at
it and they will probably be able to come up with a plan of action. At
present, they don't have much to go on, and nor will you if carry on as
you're going ...
Cheers,
Wol
next prev parent reply other threads:[~2020-03-20 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 19:55 Raid6 recovery Glenn Greibesland
2020-03-20 19:15 ` Wols Lists [this message]
[not found] ` <CA+9eyigMV-E=FwtXDWZszSsV6JOxxFOFVh6WzmeH=OC3heMUHw@mail.gmail.com>
2020-03-21 0:06 ` antlists
2020-03-21 11:54 ` Glenn Greibesland
2020-03-21 19:24 ` Phil Turmel
2020-03-21 22:12 ` Glenn Greibesland
2020-03-22 0:32 ` Phil Turmel
2020-03-23 9:23 ` Wols Lists
2020-03-23 12:35 ` Glenn Greibesland
2020-03-22 0:05 ` Wols Lists
-- strict thread matches above, loose matches on Subject: below --
2011-01-14 16:16 raid6 recovery Björn Englund
2011-01-14 21:52 ` NeilBrown
2009-01-15 15:24 Jason Weber
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=5E75163B.2050602@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=glenngreibesland@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=philip@turmel.org \
/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;
as well as URLs for NNTP newsgroup(s).