From: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
To: Mateusz Korniak <mateusz-lists@ant.gliwice.pl>
Cc: Wolfgang Denk <wd@denx.de>, linux-raid@vger.kernel.org
Subject: Re: Disk Monitoring
Date: Thu, 29 Jun 2017 12:25:03 +0200 [thread overview]
Message-ID: <CAJH6TXgp4CdrJ9a3Ku-R8Tj5Am+zeyRO_Bc_hFidWVLZW1f9vQ@mail.gmail.com> (raw)
In-Reply-To: <7688279.9aYLlOU3Xu@matkor-lenovo>
2017-06-29 12:20 GMT+02:00 Mateusz Korniak <mateusz-lists@ant.gliwice.pl>:
> Also SMART long test should perform "read/verify scan of all of the user data
> area", so it is good idea to do it periodically and monitor results.
I'm already using this, but is not very reliable.
I had some disks failed by hw raid controller due to unreadable sector
(3/11) still passing the smart long test
and some failed smart long test still passing the hw raid check
next prev parent reply other threads:[~2017-06-29 10:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 13:19 Disk Monitoring Wolfgang Denk
2017-06-29 9:52 ` Gandalf Corvotempesta
2017-06-29 10:10 ` Reindl Harald
2017-06-29 10:14 ` Gandalf Corvotempesta
2017-06-29 10:37 ` Reindl Harald
2017-06-29 14:28 ` Wols Lists
2017-06-29 10:14 ` Andreas Klauer
2017-06-29 10:14 ` Mateusz Korniak
2017-06-29 10:16 ` Gandalf Corvotempesta
2017-06-29 14:33 ` Wols Lists
2017-06-30 12:35 ` Gandalf Corvotempesta
2017-06-30 14:35 ` Phil Turmel
2017-06-30 19:56 ` Anthony Youngman
2017-07-01 13:42 ` Drew
2017-07-01 14:12 ` Gandalf Corvotempesta
2017-07-01 15:36 ` Drew
2017-06-29 10:20 ` Mateusz Korniak
2017-06-29 10:25 ` Gandalf Corvotempesta [this message]
2017-06-29 10:34 ` Reindl Harald
-- strict thread matches above, loose matches on Subject: below --
2017-06-28 10:25 Gandalf Corvotempesta
2017-06-28 10:45 ` Johannes Truschnigg
2017-07-06 3:31 ` NeilBrown
2017-06-28 12:43 ` Wols Lists
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=CAJH6TXgp4CdrJ9a3Ku-R8Tj5Am+zeyRO_Bc_hFidWVLZW1f9vQ@mail.gmail.com \
--to=gandalf.corvotempesta@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz-lists@ant.gliwice.pl \
--cc=wd@denx.de \
/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).