linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Spelic <spelic@shiftmail.org>
To: Jean de Largentaye <jean@largentaye.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Aliens ate my superblock!
Date: Fri, 24 Dec 2010 19:43:30 +0100	[thread overview]
Message-ID: <4D14E9D2.6000702@shiftmail.org> (raw)
In-Reply-To: <AANLkTimzJEdHDgnKbA5rk1Jwf7471Tib-JW3akEuWbwE@mail.gmail.com>

On 12/24/2010 06:44 PM, Jean de Largentaye wrote:
> Hi folks,
>
> I have a case where I lost the last ~2000 sectors of my hard drives*.
> As that's where the 0.90 superblock is stored, those disks are no
> longer automatically recognized by md. Apart from that part, my disks
> and other hardware is fine.
>
> This is a RAID6 with 6 disks, 3 of which were chomped
>    

Hi Jean
Is the chomped part writable? Otherwise you will first have to copy 
those drives elsewhere.

I think the only way would be to recreate the RAID over the drives with 
--assume-clean so that no resync is made.
(resync would destroy your data)
Be sure to make it same size (don't use smaller partitions) and same 
superblock type.
When recreating the array you have to correctly guess the order of 
devices to make it identical to the first time you created it. Then it 
will become readable.
For the 3 still readable devices you can read their position number via 
mdadm --examine /dev/device  (it's called Array Slot)
If you have 3 devices with unknown position number (array slot) in the 
array you can try all combinations, which are 6.
At each iteration you can try to mount readonly and see if you see 
something.
When you have something readable you can try xfs_repair to fix it 
better. But better to ask in the xfs mailing list first.
If xfs is not repairable an extreme measure is to extract data with 
photorec.
See also older posts in this ML mentioning the --assume-clean trick for 
array recovery, many are from Neil Brown himself.

Merry Christmas to everybody

  reply	other threads:[~2010-12-24 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-24 17:44 Aliens ate my superblock! Jean de Largentaye
2010-12-24 18:43 ` Spelic [this message]
2010-12-27 15:51   ` Jean de Largentaye

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=4D14E9D2.6000702@shiftmail.org \
    --to=spelic@shiftmail.org \
    --cc=jean@largentaye.org \
    --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).