From: Phil Turmel <philip@turmel.org>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Paul Richter <iamcomcy@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Is this RAID recoverable???
Date: Tue, 03 Jan 2012 08:26:08 -0500 [thread overview]
Message-ID: <4F0301F0.40206@turmel.org> (raw)
In-Reply-To: <20120103153757.5487e6fa@natsu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Paul, Roman,
On 01/03/2012 04:37 AM, Roman Mamedov wrote:
> On Tue, 3 Jan 2012 10:41:04 +0400
> Paul Richter <iamcomcy@gmail.com> wrote:
>
>> Researched the net as much as possible, added this to wiki page:
>> http://en.wikipedia.org/wiki/Mdadm#Recovering_from_a_loss_of_raid_superblock
>
> Oh, so it was you who originally wrote those instructions? :)
> See http://permalink.gmane.org/gmane.linux.raid/35538
I was going to cite myself ...
> And also you probably mean http://en.wikipedia.org/w/index.php?title=Mdadm&oldid=468952888#Recovering_from_a_loss_of_raid_superblock
> because that part was nuked from the wikipedia page already.
As to the original question: The odds are poor, but not zero. If you
read my advice to Marcin, you know that some information from your
original array is needed. Do you have any of it?
The array size error that mount reports suggests that you are close
to correct. I suspect the original array was created with a different
data offset from the new array. The default for that changed around
mdadm v2.6.9.
HTH,
Phil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8DAe4ACgkQBP+iHzflm3Ad+QCeJa7af9gammN2kGDFd+7qGMsM
rX0An0A0GXfJR3W4J0odv4LE8/rgsa+M
=8TYC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-01-03 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 6:41 Is this RAID recoverable??? Paul Richter
2012-01-03 9:37 ` Roman Mamedov
2012-01-03 13:26 ` Phil Turmel [this message]
2012-01-03 14:22 ` Paul Richter
2012-01-03 14:34 ` Phil Turmel
[not found] ` <CAHw_BJ0NEd_RHQqdONkTiq4HO2RWQD3uHUAbQvqca9OGapgmEg@mail.gmail.com>
[not found] ` <CAHw_BJ26omrNdOzc23mCF5ObEG9z8zwmNFrP5h2dkfg_Pj+BNQ@mail.gmail.com>
[not found] ` <4F031C43.6030601@turmel.org>
[not found] ` <CAHw_BJ2Zzivi25zDvd6zj6=85mKRNExEiUgy8HmHVk94mn_FoQ@mail.gmail.com>
2012-01-03 15:42 ` Phil Turmel
[not found] ` <CAHw_BJ1=z-qNq+KXyjV6ZjBfxRdtQM6x1wVpxDQsiW2b-54O_A@mail.gmail.com>
2012-01-03 13:36 ` Roman Mamedov
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=4F0301F0.40206@turmel.org \
--to=philip@turmel.org \
--cc=iamcomcy@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.ru \
/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).