From: Wols Lists <antlists@youngman.org.uk>
To: Jun-Kai Teoh <kai.teoh@gmail.com>
Cc: mdraid <linux-raid@vger.kernel.org>
Subject: Re: Raid 5 array down/missing - went through wiki steps
Date: Sun, 29 Oct 2017 01:18:04 +0100 [thread overview]
Message-ID: <59F51E3C.1050509@youngman.org.uk> (raw)
In-Reply-To: <CAA4aoFatrJQFPHOUm9C6LjUAeNkSE9eH08T8xphuYNPErVg=QQ@mail.gmail.com>
On 28/10/17 23:15, Jun-Kai Teoh wrote:
> Thanks for the response Anthony & Mark, really appreciate how helpful
> both of you are.
>
> I did try to reassemble last night (before I found the wiki and all)
> and it would assemble, but then it'll say it can't bring the array up
> 6 drives with 1 rebuilding, and the array thinks that there should be
> 8 drives. Does that mean I'm... screwed?
Nope! Definitely not.
Six drives, one rebuilding, array of 8.
That means you have seven *working* drives out of eight. That's enough.
Get the array working, it will continue rebuilding, and will leave you
with seven drives out of eight. In other words, everything is CURRENTLY
okay. But YOU HAVE NO REDUNDANCY. One more problem, and yes you are
screwed. Which is why I say "wait for the experts". But, hardware
permitting, I think this is an easy situation to recover.
Cheers,
Wol
next prev parent reply other threads:[~2017-10-29 0:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 18:36 Raid 5 array down/missing - went through wiki steps Jun-Kai Teoh
2017-10-28 18:48 ` Mark Knecht
2017-10-28 19:03 ` Jun-Kai Teoh
2017-10-28 19:10 ` Jun-Kai Teoh
2017-10-28 19:31 ` Mark Knecht
2017-10-28 19:42 ` Jun-Kai Teoh
2017-10-28 21:15 ` Mark Knecht
2017-10-28 22:04 ` Anthony Youngman
2017-10-28 22:15 ` Jun-Kai Teoh
2017-10-28 23:41 ` Mark Knecht
2017-10-29 0:18 ` Wols Lists [this message]
2017-10-30 18:08 ` Jun-Kai Teoh
2017-10-30 18:15 ` Reindl Harald
2017-10-30 18:18 ` Mark Knecht
2017-11-06 17:10 ` Jun-Kai Teoh
2017-11-09 16:51 ` `Raid " Jun-Kai Teoh
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=59F51E3C.1050509@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=kai.teoh@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