From: Wols Lists <antlists@youngman.org.uk>
To: Thomas Grawert <thomasgrawert0282@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: help requested for mdadm grow error
Date: Mon, 25 May 2020 19:55:04 +0100 [thread overview]
Message-ID: <5ECC1488.3010804@youngman.org.uk> (raw)
In-Reply-To: <ff4ea9cd-ab35-0990-5946-4a72d4021658@gmail.com>
On 25/05/20 19:18, Thomas Grawert wrote:
>
>> https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
>>
>> Especially
>>
>> https://raid.wiki.kernel.org/index.php/Asking_for_help
>>
>> More will follow but we need this info.
>
> You´re totally right. Sorry for not quoting.
>
> All drives are new.
>
> root@nas:~# smartctl --xall /dev/sda
> smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-12-amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Device Model: WDC WD120EFAX-68UNTN0
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.
Cheers,
Wol
next prev parent reply other threads:[~2020-05-25 18:55 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 [this message]
2020-05-25 19:05 ` Thomas Grawert
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=5ECC1488.3010804@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=thomasgrawert0282@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.