From: Phil Turmel <philip@turmel.org>
To: Daniel Jones <dj@iowni.com>
Cc: Wols Lists <antlists@youngman.org.uk>, linux-raid@vger.kernel.org
Subject: Re: Requesting assistance recovering RAID-5 array
Date: Fri, 3 Apr 2020 14:34:16 -0400 [thread overview]
Message-ID: <5985cc5b-a332-eb69-2d84-cb54f8f5b0fc@turmel.org> (raw)
In-Reply-To: <CAB00BMgwCbtGYJ_hX3_rZv3uaOd7vrHuEebqsPLHp3S96tJaRw@mail.gmail.com>
On 4/3/20 2:29 PM, Daniel Jones wrote:
> Hello again,
>
>> Don't do the --add operation until you've copied anything critical in the array to external backups (while running with 3 of 4).
>
> Everything from the array has been backed up elsewhere.
>
> Up until now the only writes intentionally done to the physical drives
> have been the new partition tables. Everything else has been through
> the overlay.
>
> Now I think I'm ready to run a --create as follows on the physical drives:
> mdadm --create /dev/md0 --assume-clean --data-offset=129536 --level=5
> --chunk=512K --raid-devices=4 missing /dev/sdc1 /dev/sdd1 /dev/sde1
>
> After that I'd try to re-add the rejected drive?
> mdadm --manage /dev/md0 --add /dev/sdb1
>
> Part of me wonders about just rebuilding the whole thing and then
> copying the data back, but I don't know that would be any better then
> this path.
Sounds like a risk-free decision. mdadm --create --assume-clean
followed by a proper fsck will be lots faster than mdadm --create, mkfs,
and copying.
I'd go fast.
Phil
next prev parent reply other threads:[~2020-04-03 18:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 0:04 Requesting assistance recovering RAID-5 array Daniel Jones
2020-03-31 0:24 ` antlists
2020-03-31 0:51 ` Daniel Jones
2020-03-31 1:27 ` crowston.name
2020-03-31 1:50 ` Phil Turmel
2020-03-31 1:48 ` Phil Turmel
2020-03-31 2:09 ` Daniel Jones
2020-03-31 12:00 ` Phil Turmel
2020-03-31 13:36 ` Daniel Jones
2020-04-01 3:39 ` Daniel Jones
2020-04-01 4:45 ` Phil Turmel
2020-04-01 6:03 ` Daniel Jones
2020-04-01 12:15 ` Wols Lists
2020-04-01 12:55 ` Phil Turmel
2020-04-01 15:21 ` Daniel Jones
2020-04-01 15:38 ` Phil Turmel
2020-04-01 15:39 ` Phil Turmel
2020-04-01 18:07 ` Daniel Jones
2020-04-01 18:32 ` Phil Turmel
2020-04-03 18:29 ` Daniel Jones
2020-04-03 18:34 ` Phil Turmel [this message]
2020-04-03 18:42 ` Daniel Jones
2020-04-03 18:43 ` Phil Turmel
2020-04-03 20:13 ` Adam Goryachev
2020-04-03 20:14 ` Phil Turmel
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=5985cc5b-a332-eb69-2d84-cb54f8f5b0fc@turmel.org \
--to=philip@turmel.org \
--cc=antlists@youngman.org.uk \
--cc=dj@iowni.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