From: Phil Turmel <philip@turmel.org>
To: Julie Ashworth <ashworth@berkeley.edu>, linux-raid@vger.kernel.org
Subject: Re: request help with RAID1 array that endlessly attempts to sync
Date: Tue, 17 Dec 2013 12:55:51 -0500 [thread overview]
Message-ID: <52B09027.5090605@turmel.org> (raw)
In-Reply-To: <20131217165348.GA5070@localhost.localdomain>
Hi Julie,
On 12/17/2013 11:53 AM, Julie Ashworth wrote:
> hi all, The sync ran overnight, and smartctl reports 60 errors on
> /dev/sdb this morning. So, it seems like the drive is doomed.
You haven't actually posted enough data from smartctl to say that,
though failures in the vicinity of three years is not surprising.
Please post the output of "smartctl -x" for both of these drives.
> It's frustrating, because this has happened twice in the last month,
> where a disk failed in a RAID1, I replaced the drive, and the 'good'
> drive failed during the sync. Last time I rebuilt from scratch. I
> presume that is my fate this time.
"Good drives failing during rebuild" is a big red flag suggesting
timeout mismatches combined with lack of scrubbing.
> I plan to use RAID6 in the future, but I still have important servers
> with RAID1 arrays. Do you folks recommend replacing HDDs before they
> report errors? The drives are all ~3 years old - Seagate.
I replace drives when they reach 10 relocations, given weekly scrubs.
> I should probably stop the sync. I presume the best way to do this is
> to fail/remove /dev/sda (the new disk).
Maybe not. Please tell us you know all about error recovery timeouts
and the timeout mismatch problem commonly encountered with
consumer-grade hard drives. Otherwise, you might want search the list
archives for various combinations of the keywords "scterc", "error
recovery", "timeout mismatch", "URE", and/or "bit error rate".
Phil
next prev parent reply other threads:[~2013-12-17 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 6:50 request help with RAID1 array that endlessly attempts to sync Julie Ashworth
2013-12-17 16:53 ` Julie Ashworth
2013-12-17 17:55 ` Phil Turmel [this message]
2013-12-17 19:26 ` Julie Ashworth
2013-12-17 19:43 ` Phil Turmel
2013-12-17 23:12 ` David C. Rankin
2013-12-18 3:45 ` Julie Ashworth
2013-12-18 12:08 ` Phil Turmel
2014-01-21 6:38 ` Julie Ashworth
2014-01-21 13:23 ` Phil Turmel
2014-02-25 0:16 ` Julie Ashworth
2013-12-17 18:12 ` Wilson Jonathan
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=52B09027.5090605@turmel.org \
--to=philip@turmel.org \
--cc=ashworth@berkeley.edu \
--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).