From: Thomas Grawert <thomasgrawert0282@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Re: help requested for mdadm grow error
Date: Mon, 25 May 2020 21:05:20 +0200 [thread overview]
Message-ID: <4891e1e8-aaee-b36b-4131-ca7deb34defd@gmail.com> (raw)
In-Reply-To: <5ECC1488.3010804@youngman.org.uk>
The EFAX had me worried a moment, but these are 12TB Reds? That's fine.
> A lot of the smaller drives are now shingled, ie not fit for purpose!
>
> Debian 10 - I don't know my Debians - how up to date is that? Is it a
> new kernel with not much backports, or an old kernel full of backports?
>
> What version of mdadm?
>
>
> That said, everything looks good. There are known problems - WITH FIXES
> - growing a raid 5 so I suspect you've fallen foul of one. I'd sort out
> a rescue disk that you can boot off as you might need it. Once we know a
> bit more the fix is almost certainly a rescue disk and resume the
> reshape, or a revert-reshape and then reshaping from a rescue disk. At
> which point, you'll get your array back with everything intact.
yes, that´s the 12TB WD-Red - I´m using five pieces of it.
The Debian 10 is the most recent one. Kernel version is 4.9.0-12-amd64.
mdadm-version is v3.4 from 28th Jan 2016 - seems to be the latest,
because I can´t upgrade to any newer one using apt upgrade.
I don´t think I need a rescue disk, because the raid isn´t bootable.
It´s simply a big storage.
Thanks a lot for your support.
next prev parent reply other threads:[~2020-05-25 19:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 17:25 help requested for mdadm grow error Thomas Grawert
2020-05-25 18:09 ` Wols Lists
2020-05-25 18:18 ` Thomas Grawert
2020-05-25 18:55 ` Wols Lists
2020-05-25 19:05 ` Thomas Grawert [this message]
2020-05-25 19:20 ` Wols Lists
2020-05-25 21:45 ` John Stoffel
2020-05-25 21:55 ` antlists
2020-05-25 19:33 ` Mikael Abrahamsson
2020-05-25 19:35 ` Thomas Grawert
2020-05-25 19:42 ` Andy Smith
2020-05-25 20:30 ` Thomas Grawert
2020-05-25 21:19 ` antlists
2020-05-25 21:22 ` Thomas Grawert
2020-05-25 22:02 ` antlists
2020-05-25 22:18 ` Thomas Grawert
2020-05-25 22:32 ` antlists
2020-05-25 23:01 ` Thomas Grawert
2020-05-25 23:15 ` Thomas Grawert
2020-05-25 23:31 ` Thomas Grawert
2020-05-26 1:16 ` antlists
2020-05-26 1:16 ` Thomas Grawert
2020-05-25 18:24 ` Thomas Grawert
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=4891e1e8-aaee-b36b-4131-ca7deb34defd@gmail.com \
--to=thomasgrawert0282@gmail.com \
--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