From: Wols Lists <antlists@youngman.org.uk>
To: Steve Kolk <stevekolk@gmail.com>, anthony <antmbox@youngman.org.uk>
Cc: linux-raid@vger.kernel.org, Phil Turmel <philip@turmel.org>,
NeilBrown <neilb@suse.com>
Subject: Re: Rebuilding mdadm RAID array after OS drive failure
Date: Tue, 18 Oct 2022 08:04:17 +0100 [thread overview]
Message-ID: <6e6fa554-adb4-18f3-894e-e65ebcf9ccef@youngman.org.uk> (raw)
In-Reply-To: <CACZftsgxix6fQQE8dS0nnYvxPOgv10PQE8wt6z=WBeytcOaAdw@mail.gmail.com>
On 17/10/2022 23:46, Steve Kolk wrote:
> I set up 3 of the drives with overlays and tried forcing the assembly,
> but I still get the same error. I haven't tried the steps under
> "Irreversible mdadm failure recovery", is there where I need to go
> next?
>
> ubuntu@ubuntu:~$ echo $OVERLAYS
> /dev/mapper/sda1 /dev/mapper/sdb1 /dev/mapper/sdc1
> ubuntu@ubuntu:~$ sudo mdadm --assemble --force /dev/md1 $OVERLAYS
> mdadm: no recogniseable superblock on /dev/mapper/sda1
> mdadm: /dev/mapper/sda1 has no superblock - assembly aborted
Sounds like you haven't understood what you're supposed to do.
The whole point of overlays is it is meant to protect the underlying
device while you do stuff that could be destructive.
What you should be doing is setting up the overlays, then running "mdadm
--create". It sounds like if you run exactly the same command as when
you created the array, you'll get the original back.
Read up carefully on overlays to make sure you really understand what
you're doing. And then when you create the array with the overlays, if
you're doing as I suggested with three drives, make sure you tell it
it's a five drive array, and tell it two of the drives are missing.
I'm just going to work, but whatever you do, DO NOT DO ANYTHING THAT
WILL ACTUALLY WRITE TO THE DRIVES.
Cheers,
Wol
prev parent reply other threads:[~2022-10-18 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 21:38 Rebuilding mdadm RAID array after OS drive failure Steve Kolk
2022-10-16 22:22 ` anthony
2022-10-17 22:46 ` Steve Kolk
2022-10-18 7:04 ` Wols Lists [this message]
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=6e6fa554-adb4-18f3-894e-e65ebcf9ccef@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=antmbox@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=philip@turmel.org \
--cc=stevekolk@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;
as well as URLs for NNTP newsgroup(s).