public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Testing a used hard drive to make SURE it is good.
Date: Tue, 23 Jun 2020 12:26:43 -0500	[thread overview]
Message-ID: <51f37de0-c955-c114-56bd-672a9e064e24@gmail.com> (raw)
In-Reply-To: <1be400f1-9f5f-4e4a-ba8d-0fb7f8609a14@www.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]

Sid Spry wrote:
> On Tue, Jun 23, 2020, at 11:38 AM, Grant Edwards wrote:
>> Which is better than not knowing until the drive is failed and
>> offline. :)
>>
> But redundant if the drive degration is obvious. In two cases I
> can think of drives only reported SMART will-fail after the drives
> had hard failed. In the other cases performance was so degraded
> it was obvious it was the drive.
>
>


I've had two hard drive failures that SMART warned me about.  If not for
SMART I wouldn't have noticed the drives having issues until much
later.  Maybe even after losing a lot of data.  In both of those cases,
I lost no data at all.  I was able to recover everything off the drive. 

SMART can't predict the future so it can only monitor for the things it
can see.  If say a spindle bearing is about to lock up suddenly, SMART
most likely can't detect that since it is a hardware failure that can't
really be predicted.  We may be able to hear a strange sound if we lucky
but if it happens suddenly, it may not even do that.  While SMART can't
predict all points of failures, it can detect a lot of them.  Even if
the two drives I had failed with no warning from SMART, I'd still run it
and monitor it.  Using SMART can warn you in certain situations.  If a
person doesn't run SMART, they will miss those warnings. 

SMART isn't perfect but it is better than not having it all. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 1993 bytes --]

  reply	other threads:[~2020-06-23 17:26 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 16:07 [gentoo-user] Testing a used hard drive to make SURE it is good Dale
2020-06-15 19:20 ` Spackman, Chris
2020-06-15 19:54 ` Mark Knecht
2020-06-15 20:00   ` Rich Freeman
2020-06-15 20:04     ` Mark Knecht
2020-06-16  7:34   ` Dale
2020-06-16  8:22     ` Wols Lists
2020-06-16  9:04       ` Dale
2020-06-16 11:02         ` Wols Lists
2020-06-16 11:26           ` Dale
2020-06-16 11:36             ` Michael
2020-06-16 12:25               ` Rich Freeman
2020-06-16 23:38                 ` antlists
2020-06-17  9:47                   ` Rich Freeman
2020-06-23 16:14                 ` Sid Spry
2020-06-23 17:20                   ` Rich Freeman
2020-06-23 18:44                     ` Sid Spry
2020-06-16 13:14               ` Dale
2020-06-16 23:24             ` antlists
2020-06-17  4:47               ` Dale
2020-06-17 12:32                 ` Wols Lists
2020-06-17 12:04                   ` Rich Freeman
2020-06-16  8:29     ` Neil Bothwick
2020-06-16  8:52       ` Dale
2020-06-15 19:54 ` [gentoo-user] " Grant Edwards
2020-06-15 20:04   ` Grant Edwards
2020-06-15 23:03 ` [gentoo-user] " madscientistatlarge
2020-06-15 23:18 ` David Haller
2020-06-16  7:17   ` Dale
2020-06-16  7:32     ` William Kenworthy
2020-06-16  7:37       ` Dale
2020-06-17 15:27     ` David Haller
2020-06-18  8:07       ` Dr Rainer Woitok
2020-06-23 16:08     ` Sid Spry
2020-06-23 16:38       ` [gentoo-user] " Grant Edwards
2020-06-23 16:41         ` Sid Spry
2020-06-23 17:26           ` Dale [this message]
2020-06-23 18:32             ` Sid Spry
2020-06-23 19:37               ` Dale
2020-06-23 20:03                 ` Rich Freeman
2020-06-24  4:26               ` Wols Lists
2020-06-18  9:14   ` [gentoo-user] " Dale
2020-06-22  1:52     ` Pengcheng Xu
2020-06-22  2:15       ` Dale
2020-06-22 19:10     ` David Haller
2020-06-22 20:29       ` Dale
2020-06-22 22:59         ` David Haller
2020-06-23  4:18           ` Dale
2020-06-17  6:02 ` Dale
2020-06-20  9:50 ` Dale

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=51f37de0-c955-c114-56bd-672a9e064e24@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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