From: Leslie Rhorer <lesrhorer@att.net>
To: antlists <antlists@youngman.org.uk>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: My superblocks have gone missing, can't reassemble raid5
Date: Wed, 19 May 2021 12:03:50 -0500 [thread overview]
Message-ID: <e7317eee-9a6d-7fbd-bdee-8aca788b47fe@att.net> (raw)
In-Reply-To: <cceec847-e2e2-3d7f-008e-e3f1fac9ca20@youngman.org.uk>
On 5/19/2021 11:41 AM, antlists wrote:
> On 19/05/2021 15:48, Leslie Rhorer wrote:
>> Then I would try recreating the RAID based upon the earlier
>> Examine report:
>>
>> mdadm -C -f -n 3 -l 5 -e 1.2 -c 512 -p ls /dev/md99 /dev/loop2
>> /dev/loop0 /dev/loop1
>>
>> You may notice some of the command switches are defaults.
>> Remember what I said about a belt and suspenders? Personally, in such
>> a case I would not rely on defaults.
>
> Because defaults change?
That is one reason, yes. It also means no mater what else, I know what
the system is being told to do.
>> 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.
No, I am not.
> If those three
> drives aren't the originals, then the chances are HIGH that a simple
> re-assembly/creation is going to fail your simplistic scenario.
Absolutely. So what? If it does, very little time and no data
whatsoever is lost. If it doesn't fail, then his problem is solved with
very little trouble. I have been troubleshooting technical issues for
well over 50 years, and one of the very first lessons I learned is one
should try the simplest solutions first. Whenever they work, they can
save a tremendous amount of time and effort. After that, it's time to
dig out the heavy tools.
next prev parent reply other threads:[~2021-05-19 17:04 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 [this message]
2021-05-19 17:08 ` Leslie Rhorer
2021-05-19 18:00 ` Wols Lists
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=e7317eee-9a6d-7fbd-bdee-8aca788b47fe@att.net \
--to=lesrhorer@att.net \
--cc=antlists@youngman.org.uk \
--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