From: Roman Mamedov <rm@romanrm.net>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: scrub implies failing drive - smartctl blissfully unaware
Date: Tue, 18 Nov 2014 12:36:46 +0500 [thread overview]
Message-ID: <20141118123646.01239614@natsu> (raw)
In-Reply-To: <546AF572.2020101@swiftspirit.co.za>
On Tue, 18 Nov 2014 09:29:54 +0200
Brendan Hide <brendan@swiftspirit.co.za> wrote:
> Hey, guys
>
> See further below extracted output from a daily scrub showing csum
> errors on sdb, part of a raid1 btrfs. Looking back, it has been getting
> errors like this for a few days now.
>
> The disk is patently unreliable but smartctl's output implies there are
> no issues. Is this somehow standard faire for S.M.A.R.T. output?
Not necessarily the disk's fault, could be a SATA controller issue. How are
your disks connected, which controller brand and chip? Add lspci output, at
least if something other than the ordinary "to the motherboard chipset's
built-in ports".
--
With respect,
Roman
next prev parent reply other threads:[~2014-11-18 7:46 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XqYMg-0000YI-8y@watricky.valid.co.za>
2014-11-18 7:29 ` scrub implies failing drive - smartctl blissfully unaware Brendan Hide
2014-11-18 7:36 ` Roman Mamedov [this message]
2014-11-18 13:24 ` Brendan Hide
2014-11-18 15:16 ` Duncan
2014-11-18 12:08 ` Austin S Hemmelgarn
2014-11-18 13:25 ` Brendan Hide
2014-11-18 16:02 ` Phillip Susi
2014-11-18 15:35 ` Marc MERLIN
2014-11-18 16:04 ` Phillip Susi
2014-11-18 16:11 ` Marc MERLIN
2014-11-18 16:26 ` Phillip Susi
2014-11-18 18:57 ` Chris Murphy
2014-11-18 20:58 ` Phillip Susi
2014-11-19 2:40 ` Chris Murphy
2014-11-19 15:11 ` Phillip Susi
2014-11-20 0:05 ` Chris Murphy
2014-11-25 21:34 ` Phillip Susi
2014-11-25 23:13 ` Chris Murphy
2014-11-26 1:53 ` Rich Freeman
2014-12-01 19:10 ` Phillip Susi
2014-11-28 15:02 ` Patrik Lundquist
2014-11-19 2:46 ` Duncan
2014-11-19 16:07 ` Phillip Susi
2014-11-19 21:05 ` Robert White
2014-11-19 21:47 ` Phillip Susi
2014-11-19 22:25 ` Robert White
2014-11-20 20:26 ` Phillip Susi
2014-11-20 22:45 ` Robert White
2014-11-21 15:11 ` Phillip Susi
2014-11-21 21:12 ` Robert White
2014-11-21 21:41 ` Robert White
2014-11-22 22:06 ` Phillip Susi
2014-11-19 22:33 ` Robert White
2014-11-20 20:34 ` Phillip Susi
2014-11-20 23:08 ` Robert White
2014-11-21 15:27 ` Phillip Susi
2014-11-20 0:25 ` Duncan
2014-11-20 2:08 ` Robert White
2014-11-19 23:59 ` Duncan
2014-11-25 22:14 ` Phillip Susi
2014-11-28 15:55 ` Patrik Lundquist
2014-11-21 4:58 ` Zygo Blaxell
2014-11-21 7:05 ` Brendan Hide
2014-11-21 12:55 ` Ian Armstrong
2014-11-21 17:45 ` Chris Murphy
2014-11-22 7:18 ` Ian Armstrong
2014-11-21 17:42 ` Zygo Blaxell
2014-11-21 18:06 ` Chris Murphy
2014-11-22 2:25 ` Zygo Blaxell
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=20141118123646.01239614@natsu \
--to=rm@romanrm.net \
--cc=brendan@swiftspirit.co.za \
--cc=linux-btrfs@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.