From: Bob Brand <brand@wmawater.com.au>
To: "Wols Lists" <antlists@youngman.org.uk>, <linux-raid@vger.kernel.org>
Cc: "Phil Turmel" <philip@turmel.org>
Subject: RE: Failed adadm RAID array after aborted Grown operation
Date: Mon, 9 May 2022 08:04:38 +1000 (AEST) [thread overview]
Message-ID: <00cf01d86327$9c5dd8a0$d51989e0$@wmawater.com.au> (raw)
In-Reply-To: <f4e9c9f8-590d-49a4-39da-e31d81258ff3@youngman.org.uk>
Thank Wol.
Should I use a CentOS 7 disk or a CentOS disk?
Thanks
-----Original Message-----
From: Wols Lists <antlists@youngman.org.uk>
Sent: Monday, 9 May 2022 1:32 AM
To: Bob Brand <brand@wmawater.com.au>; linux-raid@vger.kernel.org
Cc: Phil Turmel <philip@turmel.org>
Subject: Re: Failed adadm RAID array after aborted Grown operation
On 08/05/2022 14:18, Bob Brand wrote:
> If you’ve stuck with me and read all this way, thank you and I hope
> you can help me.
https://raid.wiki.kernel.org/index.php/Linux_Raid
Especially
https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
What you need to do is revert the reshape. I know what may have happened,
and what bothers me is your kernel version, 3.10.
The first thing to try is to boot from up-to-date rescue media and see if an
mdadm --revert works from there. If it does, your Centos should then bring
everything back no problem.
(You've currently got what I call a Frankensetup, a very old kernel, a
pretty new mdadm, and a whole bunch of patches that does who knows what.
You really need a matching kernel and mdadm, and your frankenkernel won't
match anything ...)
Let us know how that goes ...
Cheers,
Wol
CAUTION!!! This E-mail originated from outside of WMA Water. Do not click
links or open attachments unless you recognize the sender and know the
content is safe.
next prev parent reply other threads:[~2022-05-08 22:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 13:18 Failed adadm RAID array after aborted Grown operation Bob Brand
2022-05-08 15:32 ` Wols Lists
2022-05-08 22:04 ` Bob Brand [this message]
2022-05-08 22:15 ` Wol
2022-05-08 22:19 ` Bob Brand
2022-05-08 23:02 ` Bob Brand
2022-05-08 23:32 ` Bob Brand
2022-05-09 0:09 ` Bob Brand
2022-05-09 6:52 ` Wols Lists
2022-05-09 13:07 ` Bob Brand
[not found] ` <CAAMCDecTb69YY+jGzq9HVqx4xZmdVGiRa54BD55Amcz5yaZo1Q@mail.gmail.com>
2022-05-11 5:39 ` Bob Brand
2022-05-11 12:35 ` Reindl Harald
2022-05-11 13:22 ` Bob Brand
2022-05-11 14:56 ` Reindl Harald
2022-05-11 14:59 ` Reindl Harald
2022-05-13 5:32 ` Bob Brand
2022-05-13 8:18 ` Reindl Harald
2022-05-20 15:13 ` Bob Brand
2022-05-20 15:41 ` Reindl Harald
2022-05-22 4:13 ` Bob Brand
2022-05-22 11:25 ` Reindl Harald
2022-05-22 13:31 ` Wols Lists
2022-05-22 22:54 ` Bob Brand
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='00cf01d86327$9c5dd8a0$d51989e0$@wmawater.com.au' \
--to=brand@wmawater.com.au \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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