From: Phil Turmel <philip@turmel.org>
To: dragos@mpigani.org
Cc: linux-raid@vger.kernel.org
Subject: Re: zeroed superblock on raid6
Date: Sat, 18 Feb 2012 14:26:41 -0500 [thread overview]
Message-ID: <4F3FFB71.9090007@turmel.org> (raw)
In-Reply-To: <20120217153441.761b673b719bce80c9046cdc1b2220df.6d4c8e4316.mailapi@mailapi03.secureserver.net>
Hi Dragos,
On 02/17/2012 05:34 PM, dragos@mpigani.org wrote:
> Hi, Following a reboot my 9 drive raid6 array refused to assemble.
> Mdadm told me that some drives had a zero superblock.
This sounds strange. I don't think mdadm has an error message that
says that. It does have an error message saying that you might need
to perform --zero-superblock in a certain (dangerous) case.
> I use the controller on the motherboard and $20 4-port add-on cards.
> I tried to use some advice found on the net and zeroed all my drives
> superblocks..... What can I do to recover my non-backed-up data?
You got bad advice. "--zero-superblock" discards the details of your
array setup, making it very difficult to figure out the correct
recovery details. It may still be possible, but you've dramatically
reduced the odds of success.
> I will send you all the logs you need, if any. Just let me know which
> please.
In order of importance / usefulness:
1) any copies of "mdadm --detail /dev/mdX" and "mdadm --examine /dev/sdX"
you might have kept from *before* the crisis.
2) contents of boot-up "dmesg" or corresponding syslog from *before* the
crisis.
3) Contents of first failed boot-up dmesg.
4) Output of "lsdrv" script from http://github.com/pturmel/lsdrv
5) Details of all of the commands you attempted after the failed bootup,
in order. Possibly from your shell history.
> Thank you very much for your help.
You're welcome.
Phil
prev parent reply other threads:[~2012-02-18 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 22:34 zeroed superblock on raid6 dragos
2012-02-18 19:26 ` Phil Turmel [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=4F3FFB71.9090007@turmel.org \
--to=philip@turmel.org \
--cc=dragos@mpigani.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.