From: Wols Lists <antlists@youngman.org.uk>
To: David Madore <david+ml@madore.org>
Cc: Linux RAID mailing-list <linux-raid@vger.kernel.org>
Subject: Re: RAID5->RAID6 reshape remains stuck at 0% (does nothing, not even start)
Date: Wed, 30 Sep 2020 20:03:32 +0100 [thread overview]
Message-ID: <5F74D684.8020005@youngman.org.uk> (raw)
In-Reply-To: <20200930185824.q6dphu2axpfcjjly@achernar.gro-tsen.net>
On 30/09/20 19:58, David Madore wrote:
> On Wed, Sep 30, 2020 at 03:09:05PM +0100, antlists wrote:
>> > So my guess was spot on :-)
>> >
>> > You'll guess that this is a common problem, with a well-known solution...
>> >
>> > https://raid.wiki.kernel.org/index.php/Easy_Fixes#Debian_9_and_Ubuntu
> OK, I've just retried with a new version of mdadm,
>
> mdadm - v4.1 - 2018-10-01
>
> - which I think is roughly contemporaneous to the kernel version I'm
> using. But the problem still persists (with the exact same symptoms
> and details).
Except that mdadm is NOT the problem. The problem is that the kernel and
mdadm are not matched date-wise, and because the kernel is a
franken-kernel you need to use a different kernel.
Use a rescue disk!!! That way, you get a kernel and an mdadm that are
the same approximate date. As it stands, your frankenkernel is too new
for mdadm 3.4, but too ancient for a modern kernel.
Cheers,
Wol
next prev parent reply other threads:[~2020-09-30 19:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 1:40 RAID5->RAID6 reshape remains stuck at 0% (does nothing, not even start) David Madore
2020-09-30 4:03 ` Wols Lists
2020-09-30 9:00 ` David Madore
2020-09-30 14:09 ` antlists
2020-09-30 18:58 ` David Madore
2020-09-30 19:03 ` Wols Lists [this message]
2020-09-30 19:45 ` David Madore
2020-09-30 20:16 ` antlists
2020-09-30 22:26 ` David Madore
2020-10-01 14:10 ` Wols Lists
2020-10-01 15:04 ` David Madore
2020-10-01 18:21 ` Phil Turmel
2020-10-02 10:52 ` Nix
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=5F74D684.8020005@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=david+ml@madore.org \
--cc=linux-raid@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).