linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <djbw@fb.com>
To: chris <tknchris@gmail.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Recovery/Access of imsm raid via mdadm?
Date: Thu, 10 Jan 2013 17:42:54 -0800	[thread overview]
Message-ID: <CAA9_cmfD6GS1Bdg2OKcyBxCRicHvO__wXSYzmSE40mGA=ace8Q@mail.gmail.com> (raw)
In-Reply-To: <CAKnNFz9arLw6NBr4y0E3T+tGc6E5F5CZdGtRjSjwZcSgyyLtgw@mail.gmail.com>

On Thu, Jan 10, 2013 at 12:19 PM, chris <tknchris@gmail.com> wrote:
> Hi Dave,
>
> Thanks for the tip, this has gotten me further
>
> # mdadm --assemble --scan
> # cat /proc/mdstat
> Personalities :
> md127 : inactive sdd[1](S) sdb[0](S)
>       4520 blocks super external:imsm
>
> So atleast now it has created an array of sorts but it only has 2 out
> of the 4 disks it should and also all disks appear to be marked as
> spares.
>
> Would I follow the same logic as typical mdadm recovery where I need
> to create the array again with the right layout and disks in right
> order and gain access to data without wiping it ?
>
> Any advice what direction to go in from here?
>

Backup the disks you have if possible.

Don't recreate the array with all 4 disks be sure to specify a missing
slot.  With mdadm-3.2.5 you do have support for creating imsm arrays
with 'missing' slots [1].  Then you can test some recreations to see
if you can find data.

At a minimum you know that sdb and sdd are in slot 2, 3, so the
question is finding a good candidate for slot 0, or 1.  It's a bit
concerning that the superblocks for those have been lost, or those
disks weren't moved over?  You can look for serial numbers in
/dev/disks/by-id.

--
Dan

[1]: http://marc.info/?l=linux-raid&m=131432484118038&w=2

  reply	other threads:[~2013-01-11  1:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 16:23 Recovery/Access of imsm raid via mdadm? chris
2013-01-10 17:09 ` Dave Jiang
2013-01-10 20:19   ` chris
2013-01-11  1:42     ` Dan Williams [this message]
2013-01-11 17:53       ` chris
2013-01-13 19:00         ` chris
2013-01-13 21:05           ` Dan Williams
2013-01-14  0:56             ` chris
2013-01-14 12:36               ` Dorau, Lukasz
2013-01-14 14:10               ` Dorau, Lukasz
2013-01-14 14:24               ` Dorau, Lukasz
2013-01-14 15:25                 ` chris
2013-01-15 10:25                   ` Dorau, Lukasz
2013-01-16 16:49                     ` chris
2013-01-16 16:53                       ` chris
2013-01-16 22:47                       ` Dan Williams
2013-01-17 15:12                         ` Charles Polisher
2013-01-17 16:07                         ` chris

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='CAA9_cmfD6GS1Bdg2OKcyBxCRicHvO__wXSYzmSE40mGA=ace8Q@mail.gmail.com' \
    --to=djbw@fb.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=tknchris@gmail.com \
    /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).