From: Phillip Susi <phillsusi@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Kernel says there is not a valid superblock, but there is
Date: Tue, 21 Oct 2014 10:07:07 -0400 [thread overview]
Message-ID: <5446688B.7030405@gmail.com> (raw)
In-Reply-To: <20141021080937.69aaf214@notabene.brown>
On 10/20/2014 5:09 PM, NeilBrown wrote:
> On Mon, 20 Oct 2014 11:09:59 -0400 Phillip Susi <phillsusi@gmail.com> wrote:
>
>> When trying to assemble, the kernel complains:
>
> Which kernel?
> uname -a
> and may as well add
> mdadm -V
>
> as well.
uname -a
Linux hyper1 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
mdadm -V
mdadm - v3.2.5 - 18th May 2012
I managed to hack around with dmsetup to create a linear mapping to the
correct data offset that mdadm -E listed and recover my data and blow
away and recreate the array. I saved a dump of the superblock if you
want them for debugging.
prev parent reply other threads:[~2014-10-21 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 15:09 Kernel says there is not a valid superblock, but there is Phillip Susi
2014-10-20 21:09 ` NeilBrown
2014-10-21 14:07 ` Phillip Susi [this message]
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=5446688B.7030405@gmail.com \
--to=phillsusi@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).