From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: linux-raid@vger.kernel.org
Subject: Re: Re-assembling array after double device failure
Date: Mon, 27 Mar 2017 16:31:13 +0200 [thread overview]
Message-ID: <20170327143113.GA19680@metamorpher.de> (raw)
In-Reply-To: <20170327133813.GQ4349@bitfolk.com>
On Mon, Mar 27, 2017 at 01:38:13PM +0000, Andy Smith wrote:
> I'm fairly confident that the drives themselves are actually okay -
> nothing untoward in SMART data - so I'm not going to replace them at
> this stage.
You did not show any logs or SMART output. There is literally nothing
in your mail that points at timeouts. If your confidence is based on
the frequent "disk got kicked. must be timeouts!!1" mails on this list,
then I wish you all the best. Praying works for some people, right...?
If you get two disks kicked, chances are something is seriously wrong.
If there is any doubt at all, and no backups exist, ddrescue both drives.
Better to make a copy you don't need than need a copy you didn't make.
Be very careful with mdadm --create. Defaults change over time and
rescue systems might give you old mdadm versions, so you have to
specify everything (metadata version, data offsets, ...).
Consider using overlays for experiments:
https://raid.wiki.kernel.org/index.php/Recovering_a_failed_software_RAID#Making_the_harddisks_read-only_using_an_overlay_file
(But not on faulty drives.)
Regards
Andreas Klauer
next prev parent reply other threads:[~2017-03-27 14:31 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 [this message]
2017-03-27 15:27 ` Anthony Youngman
2017-03-27 15:23 ` Anthony Youngman
2017-03-31 4:25 ` Andy Smith
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=20170327143113.GA19680@metamorpher.de \
--to=andreas.klauer@metamorpher.de \
--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).