9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] SMART: Silly Marketing Acronym, Rebuts Truth
Date: Sun,  4 Feb 2018 09:40:35 +0100	[thread overview]
Message-ID: <20180204084035.GA684@polynum.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1802031549340.19541@orthanc.ca>

On Sat, Feb 03, 2018 at 03:59:26PM -0800, Lyndon Nerenberg 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 had the same experience. SMART has been totally useless advertising
problems only _after_ the disks had failed, repeating "reliable" till
disaster. The OSes log were more helpful since the read and write errors
were reported (corrected) days or even weeks before the disks became
useless---and fortunately, I relied on this information to swap data.
--
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                       http://www.sbfa.fr/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  parent reply	other threads:[~2018-02-04  8:40 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
2018-02-04  8:40 ` tlaronde [this message]
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=20180204084035.GA684@polynum.com \
    --to=tlaronde@polynum.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).