Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Tim Bostrom <tbostrom@gmail.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID 5 array recovery - two drives errors in external enclosure
Date: Fri, 18 Sep 2009 08:27:08 -0700	[thread overview]
Message-ID: <2267211f0909180827jbfa57acqadd308b4b889058c@mail.gmail.com> (raw)
In-Reply-To: <20090918080706.GB22909@cthulhu.home.robinhill.me.uk>

Is there any mdadm command that would have given any info or metadata
from the previous array?  I have almost 9 months of SSH logging on my
laptop that I use to manage the array.  Maybe there's some useful info
left in the log that might help.

-Tim

On Fri, Sep 18, 2009 at 1:07 AM, Robin Hill <robin@robinhill.me.uk> wrote:
> On Thu Sep 17, 2009 at 09:19:58PM -0700, Tim Bostrom wrote:
>
>> This seemed to work, though I'm still working through the permutations
>> of the drive letters.
>>
>> I noticed that mdadm think that partition sde1 is ext2 filesystem on
>> it.  See below:
>>
>> [root@tera tbostrom]# mdadm -C /dev/md0 -l 5 -n 5 -c 256 /dev/sdb1
>> /dev/sdd1 /dev/sdc1 /dev/sde1 missing
>> mdadm: /dev/sdb1 appears to be part of a raid array:
>>     level=raid5 devices=5 ctime=Thu Sep 17 21:13:21 2009
>> mdadm: /dev/sdd1 appears to be part of a raid array:
>>     level=raid5 devices=5 ctime=Thu Sep 17 21:13:21 2009
>> mdadm: /dev/sdc1 appears to be part of a raid array:
>>     level=raid5 devices=5 ctime=Thu Sep 17 21:13:21 2009
>> mdadm: /dev/sde1 appears to contain an ext2fs file system
>>     size=396408836K  mtime=Mon Sep 21 03:41:16 2026
>> mdadm: /dev/sde1 appears to be part of a raid array:
>>     level=raid5 devices=5 ctime=Thu Sep 17 21:13:21 2009
>> Continue creating array?
>>
>> What gives?  I tried popping sdf1 in there without creating the array
>> - just to see what would happen and it thinks that sdf1 has ext2 as
>> well.
>>
> That would suggest that sde1 is the first disk in the array (I think).
>
>> Still at a loss here.  I haven't worked through all the drive
>> permutations.  In the meantime, I'll try that.  Does it make sense to
>> try sdf1 in the permutation since the drive letters may have changed
>> since moving from the enclosure?  I thought I put them back in the
>> same order as the enclosure.
>>
> Definitely not - we know sdf1 has been re-written when you did the
> initial --create after moving the drives out of the enclosure.  This
> means it _definitely_ has invalid data on it.
>
> Unfortunately, without having the metadata information from the
> _original_ array _after_ it has been moved from the enclosure, there's
> no way of knowing what order the drives should be in.  I _think_ that
> sde1 will be the first disk (as it shows up as an ext2 filesystem), but
> you'll really have to try every possible combination of the 5 devices
> (the 4 partitions and "missing").  You may be best scripting this (or
> searching to see whether someone's already done that) - there's 120
> possible combinations to try.
>
> Cheers,
>    Robin
>
> --
>     ___
>    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
>   / / )      | Little Jim says ....                            |
>  // !!       |      "He fallen in de water !!"                 |
>



-- 
-tim
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-09-18 15:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 20:42 RAID 5 array recovery - two drives errors in external enclosure Tim Bostrom
2009-09-17 21:22 ` Robin Hill
2009-09-17 21:35   ` Majed B.
2009-09-17 21:51     ` Tim Bostrom
2009-09-17 22:11       ` Majed B.
2009-09-17 22:23         ` Tim Bostrom
2009-09-18  7:58         ` Robin Hill
2009-09-17 23:11   ` Tim Bostrom
2009-09-17 23:28     ` Majed B.
2009-09-17 23:54       ` Tim Bostrom
2009-09-18  1:31         ` Guy Watkins
2009-09-18  3:50           ` Tim Bostrom
2009-09-18  4:19           ` Tim Bostrom
2009-09-18  8:07             ` Robin Hill
2009-09-18 15:27               ` Tim Bostrom [this message]
2009-09-18 15:41                 ` Robin Hill
     [not found]                 ` <6b696870909180910q67d8166ay7796321b8cd35809@mail.gmail.com>
     [not found]                   ` <2267211f0909180912p745e4ea0idb5659cb54a6adce@mail.gmail.com>
     [not found]                     ` <6b696870909180923m35f29fa2l857b6f6402eb20be@mail.gmail.com>
     [not found]                       ` <2267211f0909181041o29d6f5eft1e260696c6ab9c57@mail.gmail.com>
     [not found]                         ` <6b696870909181317x777e3c5dsdcf0e7709f9c4979@mail.gmail.com>
2009-09-18 23:30                           ` Tim Bostrom
2009-09-18 23:37                             ` Majed B.
2009-09-19  1:17                               ` Tom Carlson
2009-09-19  1:35                                 ` Guy Watkins
2009-09-21  4:40                                   ` Tim Bostrom
2009-09-21  4:59                                     ` Guy Watkins
2009-09-21  7:05                                     ` Majed B.

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=2267211f0909180827jbfa57acqadd308b4b889058c@mail.gmail.com \
    --to=tbostrom@gmail.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