From: Roman Mamedov <rm@romanrm.net>
To: Kenneth Emerson <kenneth.emerson@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Need Help with Corrupted RAID6 Array
Date: Tue, 6 Oct 2020 18:17:02 +0500 [thread overview]
Message-ID: <20201006181702.09543eb2@natsu> (raw)
In-Reply-To: <CADzwnhXJBRuCNPsGhPHt-h1J3MU2HmH3_ZWkxW_auJ7FQyqJ0w@mail.gmail.com>
On Tue, 6 Oct 2020 06:05:40 -0500
Kenneth Emerson <kenneth.emerson@gmail.com> wrote:
> If I assemble and force it to run, the drives are no longer spare but
> even with a --force, the array will not go active:
>
> root@MythTV:/home/ken# mdadm --assemble --run /dev/md3
> root@MythTV:/home/ken# cat /proc/mdstat
> Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5]
> [raid4] [raid10]
> md0 : active raid1 sdc1[2] sde1[4] sdd1[3] sdb1[1]
> 292800 blocks [5/4] [_UUUU]
>
> md1 : active raid1 sdc2[4] sde2[1] sdd2[3] sdb2[2]
> 292968384 blocks [5/4] [_UUUU]
>
> md3 : inactive sdc4[9] sde4[4] sdd4[2] sdb4[3]
> 10532388320 blocks super 1.0
Would be nice to see 'mdadm --detail /dev/md3' when it's in this state, and
what it says in 'dmesg' after you tried --force.
--
With respect,
Roman
next prev parent reply other threads:[~2020-10-06 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 11:05 Need Help with Corrupted RAID6 Array Kenneth Emerson
2020-10-06 13:17 ` Roman Mamedov [this message]
2020-10-06 19:57 ` Mark Wagner
2020-10-06 22:10 ` antlists
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=20201006181702.09543eb2@natsu \
--to=rm@romanrm.net \
--cc=kenneth.emerson@gmail.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;
as well as URLs for NNTP newsgroup(s).