From: Wols Lists <antlists@youngman.org.uk>
To: Leslie Rhorer <lesrhorer@att.net>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: My superblocks have gone missing, can't reassemble raid5
Date: Wed, 19 May 2021 19:00:25 +0100 [thread overview]
Message-ID: <60A55239.9070009@youngman.org.uk> (raw)
In-Reply-To: <3f77fc62-2698-a8cb-f366-75e8a63b9a8b@att.net>
On 19/05/21 18:08, Leslie Rhorer wrote:
>
>
> On 5/19/2021 11:41 AM, antlists wrote:
>> On 19/05/2021 15:48, Leslie Rhorer wrote:
>>
>> Because defaults change?
>
> Oh, I also don't necessarily know which build of mdadm he is using.
> They might be default on my build but not his.
>
>>> Now try running a check on the assembled array:
>>> fsck /dev/md99
>>>
>>> If that fails, shutdown the array with
>>>
>>> mdadm -S /dev/md99
>>>
>>> and then try creating the array with a different drive order.
>>> There are only two other possible permutations of three disks. If
>>> none of those work, you have some more serious problems.
>>
>> And here you are oversimplifying the problem immensely. If those three
>> drives aren't the originals
>
> Hang on. Which drives do you mean?
The drives he originally ran --create on to create the array in the
first place.
The ONLY time you can be reasonably confident that running --create WILL
recover a damaged array is if it is still in its original state - no
drives swapped, no admin changes to the array, AND you're using the same
version of mdadm.
Cheers,
Wol
next prev parent reply other threads:[~2021-05-19 18:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 4:16 My superblocks have gone missing, can't reassemble raid5 Christopher Thomas
2021-05-17 4:23 ` Christopher Thomas
2021-05-17 6:28 ` Roman Mamedov
2021-05-17 9:30 ` Wols Lists
[not found] ` <CAAMCDec=H=6ceP9bKjSnsQyvmZ0LqTAYzJTDmDQoBOHSJV+hDw@mail.gmail.com>
2021-05-17 13:19 ` Roman Mamedov
2021-05-18 17:47 ` Phil Turmel
2021-05-18 18:31 ` Reindl Harald
2021-05-19 13:20 ` Leslie Rhorer
2021-05-19 13:41 ` Phil Turmel
2021-05-19 16:54 ` Leslie Rhorer
2021-05-20 19:37 ` Nix
2021-06-07 9:52 ` Leslie Rhorer
2021-05-19 14:20 ` Andy Smith
2021-05-19 14:59 ` Leslie Rhorer
2021-05-19 14:48 ` Leslie Rhorer
2021-05-19 16:41 ` antlists
2021-05-19 17:03 ` Leslie Rhorer
2021-05-19 17:08 ` Leslie Rhorer
2021-05-19 18:00 ` Wols Lists [this message]
2021-05-19 19:01 ` Leslie Rhorer
2021-05-19 20:01 ` antlists
2021-05-19 23:45 ` Leslie Rhorer
2021-05-20 20:49 ` Nix
2021-05-21 4:07 ` Leslie Rhorer
2021-06-07 9:55 ` Leslie Rhorer
2021-05-20 20:48 ` Nix
2021-05-21 3:56 ` Leslie Rhorer
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=60A55239.9070009@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=lesrhorer@att.net \
--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