From: Curt <lightspd@gmail.com>
To: Anthony Youngman <antlists@youngman.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: hung grow
Date: Wed, 4 Oct 2017 14:16:52 -0400 [thread overview]
Message-ID: <CADg2FGYPENaUb7oDhOUu08VMhzygE365mqw=Lw332jBGbe1dGQ@mail.gmail.com> (raw)
In-Reply-To: <a528459f-8bf5-3e47-9c9a-7c040ad7ab81@youngman.org.uk>
Hi,
I was reading this one https://raid.wiki.kernel.org/index.php/RAID_Recovery
I don't have any spare bays on that server...I'd have to make a trip
to my datacenter and bring the drives back to my house. The bad thing
is the 2 drives I replaced, failed a while ago, so they were behind.
I was hoping I could still use the 4 drives I had before I did a grow
on them. Do they need to be up-to-date or do I just need the config
from them to recover the 3 drives that were still good?
Oh, I originally started with 7, 2 failed a few moths back and the 3rd
one just recently. FML
Cheers,
Curt
On Wed, Oct 4, 2017 at 1:51 PM, Anthony Youngman
<antlists@youngman.org.uk> wrote:
> On 04/10/17 18:18, Curt wrote:
>>
>> Is my raid completely fucked or can I still recover some data with
>> doing the create assume clean?
>
>
> PLEASE PLEASE PLEASE DON'T !!!!!!
>
> I take it you haven't read the raid wiki?
>
> https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
>
> The bad news is your array is well borked. The good news is I don't think
> you have - YET - managed to bork it irretrievably. A create will almost
> certainly trash it beyond recovery!!!
>
> I think we can stop/revert the grow, and get the array back to a usable
> state, where we can force an assemble. If a bit of data gets lost, sorry.
>
> Do you have spare SATA ports? So you have the bad drives you replaced (can
> you ddrescue them on to new drives?). What was the original configuration of
> the raid - you say you lost three drives, but how many did you have to start
> with?
>
> I'll let the experts talk you through the actual recovery, but the steps
> need to be to revert the grow, ddrescue the best of your failed drives,
> force an assembly, and then replace the other two failed drives. No
> guarantees as to how much data will be left at the end, although hopefully
> we'll save most of it.
>
> Cheers,
> Wol
next prev parent reply other threads:[~2017-10-04 18:16 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 17:18 hung grow Curt
2017-10-04 17:51 ` Anthony Youngman
2017-10-04 18:16 ` Curt [this message]
2017-10-04 18:29 ` Joe Landman
2017-10-04 18:37 ` Curt
2017-10-04 18:44 ` Joe Landman
2017-10-04 19:01 ` Anthony Youngman
2017-10-04 19:09 ` Curt
2017-10-04 19:46 ` Anthony Youngman
2017-10-04 20:01 ` Curt
2017-10-04 21:08 ` Anthony Youngman
2017-10-04 21:53 ` Phil Turmel
[not found] ` <CADg2FGbnMzLBqWthKY5Uo__ANC2kAqH_8B1G23nhW+7hWJ=KeA@mail.gmail.com>
2017-10-06 1:25 ` Curt
2017-10-06 11:16 ` Wols Lists
[not found] ` <CADg2FGYc-sPjwukuhonoUUCr3ze3PQWv8gtZPnUT=E4CvsQftg@mail.gmail.com>
2017-10-06 13:13 ` Phil Turmel
2017-10-06 14:07 ` Curt
2017-10-06 14:27 ` Joe Landman
2017-10-06 14:27 ` Phil Turmel
2017-10-07 3:09 ` Curt
2017-10-07 3:15 ` Curt
2017-10-07 20:45 ` Curt
2017-10-07 21:29 ` Phil Turmel
2017-10-08 22:40 ` Curt
2017-10-09 1:23 ` NeilBrown
2017-10-09 1:40 ` Curt
2017-10-09 4:28 ` NeilBrown
2017-10-09 4:59 ` Curt
2017-10-09 5:47 ` NeilBrown
2017-10-09 12:41 ` Curt
2017-10-10 12:08 ` Curt
2017-10-10 13:06 ` Phil Turmel
2017-10-10 13:37 ` Anthony Youngman
2017-10-10 14:00 ` Phil Turmel
2017-10-10 14:11 ` Curt
2017-10-10 14:14 ` Reindl Harald
2017-10-10 14:15 ` Phil Turmel
2017-10-10 14:23 ` Curt
2017-10-10 18:06 ` Phil Turmel
2017-10-10 19:25 ` Curt
2017-10-10 19:42 ` Phil Turmel
2017-10-10 19:49 ` Curt
2017-10-10 19:51 ` Curt
2017-10-10 20:18 ` Phil Turmel
2017-10-10 20:29 ` Curt
2017-10-10 20:31 ` Phil Turmel
2017-10-10 20:48 ` Curt
2017-10-10 20:47 ` NeilBrown
2017-10-10 20:58 ` Curt
2017-10-10 21:23 ` Curt
2017-10-10 21:56 ` NeilBrown
2017-10-11 0:26 ` Curt
2017-10-11 4:46 ` NeilBrown
2017-10-11 2:20 ` Curt
2017-10-11 4:49 ` NeilBrown
2017-10-11 15:38 ` Curt
2017-10-12 6:15 ` NeilBrown
2017-10-10 14:12 ` Anthony Youngman
2017-10-04 19:06 ` Anthony Youngman
2017-10-04 18:57 ` Anthony Youngman
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='CADg2FGYPENaUb7oDhOUu08VMhzygE365mqw=Lw332jBGbe1dGQ@mail.gmail.com' \
--to=lightspd@gmail.com \
--cc=antlists@youngman.org.uk \
--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 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.