From: Wols Lists <antlists@youngman.org.uk>
To: "Sean R. Funk" <sfunk1x@gmail.com>,
linux-raid@vger.kernel.org, Phil Turmel <philip@turmel.org>,
NeilBrown <neilb@suse.com>
Subject: Re: MDADM RAID 6 Bad Superblock after reboot
Date: Thu, 19 Oct 2017 15:28:27 +0100 [thread overview]
Message-ID: <59E8B68B.8090709@youngman.org.uk> (raw)
In-Reply-To: <E62B1CBC-E39C-41A2-9795-623CF4FFE95F@gmail.com>
On 19/10/17 15:11, Sean R. Funk wrote:
> This is where I've been stuck. I read a post a couple nights ago about zeroing the superblock on the drives that report no superblock, but it seems they are already zeroed? My lack of experience here isn't helping.
Bummer. This is where I'll have to leave it. Did SELinux prevent the
superblocks being written? But in that case it should also have
prevented them being updated. I'm out of my depth.
There's some information out there about doing diagnostics by using hexdump.
https://raid.wiki.kernel.org/index.php/Advanced_data_recovery
This page is currently a work-in-progress, but maybe it'll give you a
few clues.
You'll probably be asked to boot into a rescue CD, if you can.
You'll need to have a copy of the latest mdadm on hand.
Any chance of running lsdrv from a rescue CD?
What I will say is do NOT do anything that will write to the drive
unless an expert is guiding you. You've had a reshape happen. That will
have moved data and stuff around on the disk. If you destroy the
existing superblocks they will be a *nightmare* to recreate, as stuff is
no longer in the default location.
Best of luck.
Cheers,
Wol
next prev parent reply other threads:[~2017-10-19 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a0f0e0b-6b03-8ec1-b02f-b17b0447aff8@gmail.com>
2017-10-18 18:14 ` MDADM RAID 6 Bad Superblock after reboot Sean R. Funk
2017-10-18 19:40 ` Wols Lists
2017-10-19 1:52 ` sfunk1x
2017-10-19 10:58 ` Wols Lists
2017-10-19 14:11 ` Sean R. Funk
2017-10-19 14:28 ` Wols Lists [this message]
2017-10-19 21:17 ` NeilBrown
2017-10-20 0:43 ` sfunk1x
2017-10-20 1:50 ` NeilBrown
2017-10-22 21:00 ` sfunk1x
2017-10-22 22:40 ` NeilBrown
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=59E8B68B.8090709@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=philip@turmel.org \
--cc=sfunk1x@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 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.