All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert L Mathews <lists@tigertech.com>
To: linux-raid@vger.kernel.org
Subject: Re: Reassembling RAID1 after good drive was offline [newbie]
Date: Thu, 01 Jan 2015 12:54:33 -0800	[thread overview]
Message-ID: <54A5B409.8040501@tigertech.com> (raw)
In-Reply-To: <20150101174048.GB4840@deb76.aryehleib.com>

On 1/1/15 9:40 AM, Aryeh Leib Taurog wrote:

> I recently made a RAID1 array from a couple of extra usb drives:
> 
> $ mdadm --create --metadata 1.2 --verbose /dev/md/backup --level=mirror -n2 /dev/sd[cd]2

These are sdc2 and sdd2. Okay.


> Personalities : [raid1] 
> md126 : active (auto-read-only) raid1 sdc2[0]
>       943587136 blocks super 1.2 [2/1] [U_]
>       
> md127 : active (auto-read-only) raid1 sdd2[1]
>       943587136 blocks super 1.2 [2/1] [_U]

Still sdc2 and sdd2, although now in two arrays.


> AFAIK both drives are healthy, but since that happened, it refuses to 
> assemble them both in the array:
> 
> $ mdadm --assemble --force /dev/md/backup /dev/sd[db]2
> mdadm: ignoring /dev/sdb2 as it reports /dev/sdd2 as failed

Now you're working on sdb2 and sdd2. Is that intentional? Did sdc2
become sdb2 after a restart or something?


> Is there any way to put the array back together without having to 
> resync?

You should collect more data about what array each partition thinks it's
a member of, etc., before you try anything else. People can probably
help more if you report the output of these to the list:

 mdadm --detail /dev/md*
 mdadm --examine /dev/sd*

-- 
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/

  reply	other threads:[~2015-01-01 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01 17:40 Reassembling RAID1 after good drive was offline [newbie] Aryeh Leib Taurog
2015-01-01 20:54 ` Robert L Mathews [this message]
2015-01-02 11:01   ` Anthonys Lists
2015-01-02 14:02     ` Aryeh Leib Taurog
2015-01-02 13:01   ` Aryeh Leib Taurog
2015-01-02 18:38     ` Robert L Mathews
2015-01-04 10:20       ` Aryeh Leib Taurog
2015-01-04 11:10         ` Peter Grandi
2015-01-04 21:07           ` Aryeh Leib Taurog
2015-01-04 21:45             ` Wols Lists
2015-01-05 17:25               ` Robert L Mathews
2015-01-05 18:54               ` NeilBrown
2015-01-07  8:30                 ` Aryeh Leib Taurog

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=54A5B409.8040501@tigertech.com \
    --to=lists@tigertech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.