From: antlists <antlists@youngman.org.uk>
To: Daniel Jones <dj@iowni.com>, linux-raid@vger.kernel.org
Subject: Re: Requesting assistance recovering RAID-5 array
Date: Tue, 31 Mar 2020 01:24:43 +0100 [thread overview]
Message-ID: <058b3f48-e69d-2783-8e08-693ad27693f6@youngman.org.uk> (raw)
In-Reply-To: <CAB00BMjPSg2wdq7pjt=AwmcDmr0ep2+Xr0EAy6CNnVhOsWk8pg@mail.gmail.com>
On 31/03/2020 01:04, Daniel Jones wrote:
> I am genuinely over my head at this point and unsure how to proceed.
> My logic tells me the best choice is to attempt a --create to try to
> rebuild the missing superblocks, but I'm not clear if I should try
> devices=4 (the true size of the array) or devices=3 (the size it was
> last operating in). I'm also not sure of what device order to use
> since I have likely scrambled /dev/sd[bcde] and am concerned about
> what happens when I bring the previously disable drive back into the
> array.
Don't even THINK of --create until the experts have chimed in !!!
https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
The lsdrv information is crucial - that recovers pretty much all the
config information that is available, and massively increases the
chances of a successful --create, if you do have to go down that route...
If your drives are 1TB, I would *seriously* consider getting hold of a
4TB drive - they're not expensive - to make a backup. And read up on
overlays.
Hopefully we can recover your data without too much grief, but this will
all help.
Cheers,
Wol
next prev parent reply other threads:[~2020-03-31 0:24 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 [this message]
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
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=058b3f48-e69d-2783-8e08-693ad27693f6@youngman.org.uk \
--to=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