From: Andy Smith <andy@strugglers.net>
To: linux-raid@vger.kernel.org
Subject: Re: Re-assembling array after double device failure
Date: Fri, 31 Mar 2017 04:25:10 +0000 [thread overview]
Message-ID: <20170331042510.GD4349@bitfolk.com> (raw)
In-Reply-To: <eb7bebad-f173-b6e9-75f8-182148eccc46@youngman.org.uk>
Hi Anthony,
On Mon, Mar 27, 2017 at 04:23:19PM +0100, Anthony Youngman wrote:
> Hopefully fixing the timeout, followed by a --assemble --force, then
> a scrub, will be all that's required.
Yep, thanks. Luckily it assembled without --force, and I was then
able to replace the older drive with a new one and rebuild onto it.
It completed that without error and seems happy now.
I'm going to subject the removed drive that got kicked out first to
some more in-depth scrutiny in another machine as soon as I get
chance.
Cheers,
Andy
prev parent reply other threads:[~2017-03-31 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 13:38 Re-assembling array after double device failure Andy Smith
2017-03-27 14:31 ` Andreas Klauer
2017-03-27 15:27 ` Anthony Youngman
2017-03-27 15:23 ` Anthony Youngman
2017-03-31 4:25 ` Andy Smith [this message]
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=20170331042510.GD4349@bitfolk.com \
--to=andy@strugglers.net \
--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).