linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Teytelman <dim@dimtel.com>
To: linux-raid@vger.kernel.org
Subject: Re: Can this setup be saved?
Date: Mon, 15 Feb 2010 06:02:56 -0800	[thread overview]
Message-ID: <c98f60c41002150602n1f9d1534of558045d7b7a563e@mail.gmail.com> (raw)
In-Reply-To: <4877c76c1002121813h410900by1c398c80e2aa0635@mail.gmail.com>

Hello all,

On Fri, Feb 12, 2010 at 18:13, Michael Evans <mjevans1983@gmail.com> wrote:
> On Fri, Feb 12, 2010 at 5:56 PM, Dmitry Teytelman <dim@dimtel.com> wrote:
>>
>> However at some point during/after the reconstruction the situation
>> has changed. Now both /dev/sdc2 and /dev/sdd2 are marked as spare
>> drives (see mdadm -E output below) and I cannot start the array. I
>> think /dev/sdd2 should be in sync with /dev/sda2, but how can I bring
>> it back (it used to be device 2)?
>
> It sounds like you've reached the point where you've done something
> silly and need to try to recover what you can.
>
> READ THIS SITE CAREFULLY; perform READ ONLY recovery, and see if you
> can find a permutation that can be mounted read only and READ with
> valid data;

I am back on the air!!! Th critical step was the use of "mdadm
--create" with a missing drive. I knew the proper order for the two
drives that were in sync. One of them (/dev/sdd) was failing, so it
was ddrescue-d onto a new drive prior to any repairs. Performing
"mdadm --create" brought the RAID device back to life. I checked that
the data looked OK (read-only). Then I went ahead and added the third
drive to the array. Soon a fully reconstructed device was up and
running. Failed drives are heading back to Hitachi :)

Thanks to the group for rapid response and critically important bits
of information!

-- 
Dmitry Teytelman

  reply	other threads:[~2010-02-15 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-13  1:56 Can this setup be saved? Dmitry Teytelman
2010-02-13  2:13 ` Michael Evans
2010-02-15 14:02   ` Dmitry Teytelman [this message]
2010-02-13  8:58 ` Giovanni Tessore

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=c98f60c41002150602n1f9d1534of558045d7b7a563e@mail.gmail.com \
    --to=dim@dimtel.com \
    --cc=linux-raid@vger.kernel.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).