From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Stephen Mueller <stephen@mueller.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RAID array is gone, please help
Date: Thu, 23 Mar 2017 15:59:03 -0400 [thread overview]
Message-ID: <20170323195903.GO14186@csclub.uwaterloo.ca> (raw)
In-Reply-To: <9dcb25dc-52f3-f831-6115-6a7feb07de1c@mueller.org>
On Thu, Mar 23, 2017 at 08:38:08PM +0100, Stephen Mueller wrote:
> Apologies, I should have started this on linux-raid...
>
>
> stephen@fred> sudo gdisk -l /dev/sdc
> GPT fdisk (gdisk) version 1.0.1
>
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT: present
>
> Found valid GPT with protective MBR; using GPT.
> Disk /dev/sdc: 7814037168 sectors, 3.6 TiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 60F1D54C-9D17-4688-BD6E-447F5E7408EB
> Partition table holds up to 128 entries
> First usable sector is 34, last usable sector is 7814037134
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 7814037101 sectors (3.6 TiB)
>
> Number Start (sector) End (sector) Size Code Name
> stephen@fred>
>
> The other disks are all similar.
>
> How do I remove the MBR/GPT tables? So you would do that, and then the
> mdadm --create?
Well at least that seems to confirm that something restored the GPT from
the second copy at the end of the disk, wiping out the md superblock
at 4k.
If you run gdisk /dev/sdc, it has a 'zap' option using the z key to
delete all traces of GPT. That ought to do what you want.
--
Len Sorensen
next prev parent reply other threads:[~2017-03-23 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 16:49 raid
2017-03-23 17:37 ` Lennart Sorensen
2017-03-23 18:09 ` raid
2017-03-23 19:27 ` Lennart Sorensen
2017-03-23 19:38 ` Stephen Mueller
2017-03-23 19:59 ` Lennart Sorensen [this message]
2017-03-23 20:09 ` Stephen Mueller
2017-03-23 21:01 ` Lennart Sorensen
2017-03-23 21:02 ` Stephen Mueller
2017-03-23 21:09 ` Lennart Sorensen
2017-03-23 21:11 ` Stephen Mueller
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=20170323195903.GO14186@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen@mueller.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
all inboxes | Powered by JetHome®