From: Phil Turmel <philip@turmel.org>
To: Jun-Kai Teoh <kai.teoh@gmail.com>, Mark Knecht <markknecht@gmail.com>
Cc: Wols Lists <antlists@youngman.org.uk>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RAID5 up, but one drive removed, one says spare building, what now?
Date: Fri, 10 Nov 2017 13:01:50 -0500 [thread overview]
Message-ID: <3fa05723-8275-8840-7fbc-397801fa17de@turmel.org> (raw)
In-Reply-To: <CAA4aoFbOnCtj_+qbfuzz7qS6xrt5HB9XJK-E+h0_eEu=vLdftg@mail.gmail.com>
Hi Jun-Kai,
{Convention on kernel.org is to trim replies and avoid top-posting.}
On 11/10/2017 12:25 PM, Jun-Kai Teoh wrote:
> I was reshaping/growing my array when it died. Computer came back up
> but array wouldn't assemble.
>
> I looked around and saw some commands on how to assemble without the
> one drive that looked like it was kicked off sometime ago that I did
> not realize (I used --assemble --force --verbose)
>
> I kept getting the error that there were 6 drives, 1 rebuilding, and
> not enough to get the array up. I unplugged the one drive that had the
> incorrect superblock and ran "mdadm -A -R".
>
> It ran and looked like it was resuming reshaping but it got really
> slow - like 7 years slow.
>
> I killed the process, rebooted the machine, and it just auto
> reassembled the array and automounted it on boot.
>
> Am in the process of backup right now.
>
> And yes, the drive/array is mounted.
Ok. I reviewed the other thread. Consider creating a new array from
scratch after you complete your backups, using consistent partitioning
across all devices. I would put LVM on top and leave part of it
unallocated (for emergencies), but that's just my preference.
Phil
next prev parent reply other threads:[~2017-11-10 18:01 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
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 [this message]
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=3fa05723-8275-8840-7fbc-397801fa17de@turmel.org \
--to=philip@turmel.org \
--cc=antlists@youngman.org.uk \
--cc=kai.teoh@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=markknecht@gmail.com \
/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