From: Wols Lists <antlists@youngman.org.uk>
To: Jun-Kai Teoh <kai.teoh@gmail.com>,
Linux-RAID <linux-raid@vger.kernel.org>,
Phil Turmel <philip@turmel.org>
Subject: Re: RAID5 up, but one drive removed, one says spare building, what now?
Date: Fri, 10 Nov 2017 11:31:49 +0000 [thread overview]
Message-ID: <5A058E25.1020608@youngman.org.uk> (raw)
In-Reply-To: <CAA4aoFaEwv=EPcotAbjzkgXWoOFwxo2XAoMzN1Zfb62k4Fngxw@mail.gmail.com>
On 10/11/17 03:09, Jun-Kai Teoh wrote:
> Hi all,
>
> I managed to get my RAID drive back up, content looks like it's still
> there, but it's not resyncing or reshaping and my parity drive was
> removed (I did it when I tried to get it back up).
>
> So what should I do now? I'm afraid of doing anything else at this point.
>
> /dev/md126:
> Version : 1.2
> Creation Time : Thu Jun 30 07:57:36 2016
> Raid Level : raid5
> Array Size : 23441323008 (22355.39 GiB 24003.91 GB)
> Used Dev Size : 3906887168 (3725.90 GiB 4000.65 GB)
> Raid Devices : 8
> Total Devices : 7
> Persistence : Superblock is persistent
>
> Intent Bitmap : Internal
>
> Update Time : Thu Nov 9 18:57:18 2017
> State : clean, FAILED
> Active Devices : 6
> Working Devices : 7
> Failed Devices : 0
> Spare Devices : 1
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Delta Devices : 1, (7->8)
>
> Name : livingrm-server:2 (local to host livingrm-server)
> UUID : f7333d4f:8300969d:55148d64:93c8afc8
> Events : 650582
>
> Number Major Minor RaidDevice State
> 0 8 112 0 active sync /dev/sdh
> 1 8 48 1 active sync /dev/sdd
> 7 8 64 2 spare rebuilding /dev/sde
> 3 8 96 3 active sync /dev/sdg
> 4 8 32 4 active sync /dev/sdc
> 5 8 80 5 active sync /dev/sdf
> 6 8 16 6 active sync /dev/sdb
> 14 0 0 14 removed
Okay. I was hoping someone else would chime in, but I'd say this looks
well promising. You have seven drives of eight so you have no redundancy :-(
You say your data is still there - does that mean you've mounted it, and
it looks okay?
sde is rebuilding, which means the array is sorting itself out.
You need that eighth drive. If a fsck says you have no (or almost no)
filesystem corruption, and you have a known-good drive, add it in. The
array will then sort itself out.
I would NOT recommend mounting it read-write until it comes back and
says "eight drives of eight working".
Cheers,
Wol
next prev parent reply other threads:[~2017-11-10 11:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 3:09 RAID5 up, but one drive removed, one says spare building, what now? Jun-Kai Teoh
2017-11-10 11:31 ` Wols Lists [this message]
2017-11-10 13:01 ` Phil Turmel
2017-11-10 13:13 ` Mark Knecht
2017-11-10 17:25 ` Jun-Kai Teoh
2017-11-10 18:01 ` Phil Turmel
2017-11-10 18:15 ` Jun-Kai Teoh
2017-11-10 19:04 ` Phil Turmel
2017-11-10 19:22 ` Jun-Kai Teoh
2017-11-10 21:58 ` Phil Turmel
2017-11-10 23:17 ` Wols Lists
2017-11-10 23:22 ` Wols Lists
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=5A058E25.1020608@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=kai.teoh@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.