From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: mdraid <linux-raid@vger.kernel.org>
Subject: Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
Date: Tue, 26 Jul 2016 17:59:57 -0500 [thread overview]
Message-ID: <5797EB6D.2000104@suddenlinkmail.com> (raw)
In-Reply-To: <767a0ad7-bb45-b0b8-5d8b-08f65d346fa9@turmel.org>
On 07/26/2016 05:10 PM, Phil Turmel wrote:
> You won't be able to re-add sdd because as Chris said, "fixing" the
> primary GPT broke mdadm's superblock. After zeroing the beginning 4k of
> sdd, --add it to your array and let it rebuild.
>
> Phil
Thanks Phil, what's the quickest way to zero the 4k, something like
# dd of=/dev/sdd if=/dev/zero bs=1 count=4096
??
--
David C. Rankin, J.D.,P.E.
next prev parent reply other threads:[~2016-07-26 22:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 0:52 GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help? David C. Rankin
2016-07-26 4:18 ` Adam Goryachev
2016-07-26 5:28 ` David C. Rankin
2016-07-26 8:20 ` David C. Rankin
2016-07-26 9:52 ` Adam Goryachev
2016-07-26 17:14 ` Phil Turmel
2016-07-26 20:24 ` David C. Rankin
2016-07-26 20:12 ` David C. Rankin
2016-07-26 20:47 ` Chris Murphy
2016-07-26 22:47 ` David C. Rankin
2016-07-26 23:18 ` Chris Murphy
2016-07-27 7:13 ` SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?] David C. Rankin
2016-07-27 13:04 ` Anthony Youngman
2016-07-27 23:10 ` David C. Rankin
2016-07-28 12:53 ` Anthony Youngman
2016-07-28 20:51 ` Andreas Dröscher
2016-07-28 21:25 ` Phil Turmel
2016-07-27 14:22 ` Phil Turmel
2016-07-27 23:12 ` David C. Rankin
2016-07-27 13:10 ` GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help? Anthony Youngman
2016-07-26 15:19 ` Chris Murphy
2016-07-26 15:55 ` Chris Murphy
2016-07-26 21:12 ` David C. Rankin
2016-07-26 22:10 ` Phil Turmel
2016-07-26 22:59 ` David C. Rankin [this message]
2016-07-26 23:23 ` Chris Murphy
2016-07-27 0:19 ` David C. Rankin
2016-07-26 20:34 ` David C. Rankin
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=5797EB6D.2000104@suddenlinkmail.com \
--to=drankinatty@suddenlinkmail.com \
--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).