9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] SMART: Silly Marketing Acronym, Rebuts Truth
Date: Sat,  3 Feb 2018 19:58:46 -0800	[thread overview]
Message-ID: <CA01B110-FE08-49A6-969F-15FBEE410470@bitblocks.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1802031549340.19541@orthanc.ca>

On Feb 3, 2018, at 3:59 PM, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:

>> The interesting thing (for me) was that
>> the SMART data from the drive gave it an all clear right to the end. But
>> unlike the SSDs, there was plenty of behavioural warning to remind me to
>> have the backups up to date and a spare at the ready...
> 
> FWIW, of the three-four dozen or so drives I have actively SMART monitored over the years, of the ones that failed, *not* *one* gave a SMART warning before dying.
> 
> That includes a spinny disk in one of my Mac Minis.  Of anyone, I would expect Apple to be in bed with their HD suppliers enough to have HD firmware that reliably reports SMART errors (since the disk utilities do pay attemtion to it).  I spent a month listening to that drive's heads slam back to the home position as it tried to recalibrate itself, before eventually dying. To the bitter end, SMART reported "a-ok boss!"

I have only monitored disks @ home and for them SMART does report
all sorts of things. For recalibration to have kicked in, you should seeing
lots of errors. It’s possible Apple s/w dumbs it down & presents just one
binary choice to the user but the underlying data should be there. It’s
usually host s/w that falls short. Given disks’ bathtub error curve, s/w
should show error rate as a graph (as a function of time) from the
beginning and recommend replacement as the rate starts climbing
again. Ideally it should even compare it with averaged error data
collected by the vendor. History and good visualization can be very
helpful.



  reply	other threads:[~2018-02-04  3:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-03 23:59 Lyndon Nerenberg
2018-02-04  3:58 ` Bakul Shah [this message]
2018-02-04  8:40 ` tlaronde
2018-02-04 18:10   ` Erik Quanstrom
2018-02-04 19:16     ` tlaronde

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=CA01B110-FE08-49A6-969F-15FBEE410470@bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /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).