public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Roman Mamedov <rm@romanrm.net>,
	Christopher Thomas <youkai@earthlink.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: My superblocks have gone missing, can't reassemble raid5
Date: Mon, 17 May 2021 10:30:13 +0100	[thread overview]
Message-ID: <60A237A5.9020602@youngman.org.uk> (raw)
In-Reply-To: <20210517112844.388d2270@natsu>

On 17/05/21 07:28, Roman Mamedov wrote:
> As for recovery, you really might need to play with --create; to prevent the
> chance of data loss, there's a way to experiment using "overlays", keeping the
> original drives untouched; see [2] for more background on that, and [3]
> provides steps for your actual situation. Don't forget to use "--assume-clean"
> and "--readonly".

Firstly, what I'd do is a hexdump of the fifth kb of each disk (ie
hopefully where the superblock is/was). Post that here and see if anyone
can decode it. It does look like something has created a gpt, so mdadm
is no longer looking at the raw disk for the array.

There MIGHT be enough information lying around for someone to tell you
what --create command to use. Another thing - are those the original
disks used to create the array? Have you modified the array in any way?
If you haven't modified the array, then a plain create using the same
version of mdadm that created the array should just put things back the
way they were. The reason you mustn't just use --create willy nilly is
that any modification of the array might move the data offset, and
different versions of mdadm may have different default settings.

The other option is BACK UP YOUR HARD DRIVES, delete the new gpt, and
then see if it will assemble.

I know I've seen this before, but I've a nasty feeling the previous time
the user had used partitions and the GPT had been trashed so it's not
quite the same. Still, you might well be lucky ...

Cheers,
Wol

  reply	other threads:[~2021-05-17  9:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  4:16 My superblocks have gone missing, can't reassemble raid5 Christopher Thomas
2021-05-17  4:23 ` Christopher Thomas
2021-05-17  6:28 ` Roman Mamedov
2021-05-17  9:30   ` Wols Lists [this message]
     [not found]   ` <CAAMCDec=H=6ceP9bKjSnsQyvmZ0LqTAYzJTDmDQoBOHSJV+hDw@mail.gmail.com>
2021-05-17 13:19     ` Roman Mamedov
2021-05-18 17:47       ` Phil Turmel
2021-05-18 18:31         ` Reindl Harald
2021-05-19 13:20           ` Leslie Rhorer
2021-05-19 13:41             ` Phil Turmel
2021-05-19 16:54               ` Leslie Rhorer
2021-05-20 19:37               ` Nix
2021-06-07  9:52                 ` Leslie Rhorer
2021-05-19 14:20             ` Andy Smith
2021-05-19 14:59               ` Leslie Rhorer
2021-05-19 14:48 ` Leslie Rhorer
2021-05-19 16:41   ` antlists
2021-05-19 17:03     ` Leslie Rhorer
2021-05-19 17:08     ` Leslie Rhorer
2021-05-19 18:00       ` Wols Lists
2021-05-19 19:01         ` Leslie Rhorer
2021-05-19 20:01           ` antlists
2021-05-19 23:45             ` Leslie Rhorer
2021-05-20 20:49               ` Nix
2021-05-21  4:07                 ` Leslie Rhorer
2021-06-07  9:55                   ` Leslie Rhorer
2021-05-20 20:48           ` Nix
2021-05-21  3:56             ` Leslie Rhorer

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=60A237A5.9020602@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.net \
    --cc=youkai@earthlink.net \
    /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