From: Mark Wagner <carnildo@gmail.com>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Cc: Kenneth Emerson <kenneth.emerson@gmail.com>
Subject: Re: Need Help with Corrupted RAID6 Array
Date: Tue, 6 Oct 2020 12:57:10 -0700 [thread overview]
Message-ID: <CAA04aRQwR2J90fb1QUf1cpXsyvwbmrqVZnOT41JE7mLtvyYYOw@mail.gmail.com> (raw)
In-Reply-To: <CADzwnhXJBRuCNPsGhPHt-h1J3MU2HmH3_ZWkxW_auJ7FQyqJ0w@mail.gmail.com>
On Tue, Oct 6, 2020 at 4:06 AM Kenneth Emerson
<kenneth.emerson@gmail.com> wrote:
>
> It's been several years since I asked and received help on this list.
> Once again, I find myself in a bind. I have accidentally destroyed
> one of my disks in a set of 5 4-TB drives set as RAID6. When I
> rebooted 2 of the three arrays rebuilt correctly; however, the third
> (largest and most important) would not assemble. I thought, even
> though I had lost one drive, I could rebuild the array by substituting
> a new, partitioned drive but I cannot get the array to start.
> root@MythTV:/home/ken# mdadm --examine /dev/sdb4
> /dev/sdb4:
> Raid Level : raid6
> Raid Devices : 7
> Array Size : 13165485120 (12555.59 GiB 13481.46 GB)
> Used Dev Size : 5266194048 (2511.12 GiB 2696.29 GB)
> Array State : AAAAAAA ('A' == active, '.' == missing, 'R' == replacing)
You say this is a five-disk RAID-6 array, but the disk metadata says,
in three different ways, that this is a seven-disk array. Do you have
any idea what could be causing this discrepancy?
--
Mark
next prev parent reply other threads:[~2020-10-06 19:57 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
2020-10-06 19:57 ` Mark Wagner [this message]
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=CAA04aRQwR2J90fb1QUf1cpXsyvwbmrqVZnOT41JE7mLtvyYYOw@mail.gmail.com \
--to=carnildo@gmail.com \
--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).