From: Wols Lists <antlists@youngman.org.uk>
To: Peter Sanders <plsander@gmail.com>, linux-raid@vger.kernel.org
Cc: Phil Turmel <philip@turmel.org>, NeilBrown <neilb@suse.com>
Subject: Re: RAID 6, 6 device array - all devices lost superblock
Date: Sun, 28 Aug 2022 10:54:41 +0100 [thread overview]
Message-ID: <dc24b476-2f0a-8406-f1c0-e33b5b0eb388@youngman.org.uk> (raw)
In-Reply-To: <70e2ae22-bbba-77a4-c9bc-4c02752f4cb7@youngman.org.uk>
On 28/08/2022 10:14, Wols Lists wrote:
>> Currently I have no /dev/md* devices.
>> I have access to the old mdadm.conf file - have tried assembling with
>> it, with the default mdadm.conf, and with no mdadm.conf file in /etc
>> and /etc/mdadm.
>
> It looks like the drives weren't partitioned :-( I think you're into
> forensics.
Whoops - my system froze while I was originally writing my reply, and I
forgot to put this into my rewrite ...
Look up overlays in the wiki. I've never done it myself, but a fair few
people have said the instructions worked a treat.
You're basically making the drives read-only (all writes get dumped into
the overlay file), and then re-creating the array over the top, so you
can test whether you got it right. If you don't, you just ditch the
overlays and start again, if you did get it right you can recreate the
array for real.
Cheers,
Wol
next prev parent reply other threads:[~2022-08-28 9:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 2:00 RAID 6, 6 device array - all devices lost superblock Peter Sanders
2022-08-28 9:14 ` Wols Lists
2022-08-28 9:54 ` Wols Lists [this message]
2022-08-28 16:47 ` Phil Turmel
[not found] ` <CAKAPSkJAQYsec-4zzcePbkJ7Ee0=sd_QvHj4Stnyineq+T8BXw@mail.gmail.com>
2022-08-28 17:16 ` Wols Lists
2022-08-28 18:45 ` John Stoffel
2022-08-28 19:36 ` Phil Turmel
2022-08-28 19:49 ` John Stoffel
2022-08-28 23:24 ` Peter Sanders
2022-08-29 13:12 ` Peter Sanders
2022-08-29 21:45 ` John Stoffel
2022-08-29 22:29 ` Eyal Lebedinsky
2022-08-29 23:53 ` Peter Sanders
2022-08-30 13:27 ` Peter Sanders
2022-08-30 18:03 ` Wols Lists
2022-08-31 17:48 ` Peter Sanders
2022-08-31 20:37 ` John Stoffel
2022-09-02 14:56 ` Peter Sanders
2022-09-02 18:52 ` Peter Sanders
2022-09-02 19:12 ` John Stoffel
2022-09-03 0:39 ` Peter Sanders
2022-09-03 5:51 ` Peter Sanders
2022-09-05 19:36 ` John Stoffel
2022-09-05 20:16 ` Peter Sanders
2022-09-05 19:25 ` John Stoffel
2022-08-28 15:10 ` John Stoffel
2022-08-28 17:11 ` Andy Smith
2022-08-28 17:22 ` Andy Smith
2022-08-28 17:34 ` Peter Sanders
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=dc24b476-2f0a-8406-f1c0-e33b5b0eb388@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=philip@turmel.org \
--cc=plsander@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox