public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Does this drive need a funeral?
Date: Wed, 2 Nov 2011 21:01:43 +0000	[thread overview]
Message-ID: <201111022101.45018.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4EB04146.8030207@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 2260 bytes --]

On Tuesday 01 Nov 2011 18:58:14 Dale wrote:
> Hi,
> 
> For the first time in my life, I think I have a drive failing on me.
> Here is the info:
[snip ...]

> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: FAILED!
> Drive failure expected in less than 24 hours. SAVE ALL DATA.

That's not encouraging ...  :-/

Then this:

> SMART Attributes Data Structure revision number: 16
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
> UPDATED  WHEN_FAILED RAW_VALUE
>    1 Raw_Read_Error_Rate     0x000b   018   001   051    Pre-fail
> Always   FAILING_NOW 1904

The Value (018) being lower than the Threshold (051) indicates failure is 
imminent.  Of course it also screams at you that it's "FAILING NOW" in case 
you missed it!  :-))


>    3 Spin_Up_Time            0x0007   087   084   021    Pre-fail
> Always       -       2166
>    4 Start_Stop_Count        0x0032   099   099   040    Old_age
> Always       -       1288
>    5 Reallocated_Sector_Ct   0x0033   199   199   140    Pre-fail
> Always       -       1
>    7 Seek_Error_Rate         0x000b   200   200   051    Pre-fail
> Always       -       0
>    9 Power_On_Hours          0x0032   023   023   000    Old_age
> Always       -       56466
>   10 Spin_Retry_Count        0x0013   100   100   051    Pre-fail
> Always       -       0
>   11 Calibration_Retry_Count 0x0013   100   100   051    Pre-fail
> Always       -       0
>   12 Power_Cycle_Count       0x0032   099   099   000    Old_age
> Always       -       1039
> 194 Temperature_Celsius     0x0022   110   253   000    Old_age
> Always       -       33
> 196 Reallocated_Event_Count 0x0032   199   199   000    Old_age
> Always       -       1
> 197 Current_Pending_Sector  0x0012   199   199   000    Old_age
> Always       -       17
> 198 Offline_Uncorrectable   0x0012   200   200   000    Old_age
> Always       -       10
> 199 UDMA_CRC_Error_Count    0x000a   200   253   000    Old_age
> Always       -       1155
> 200 Multi_Zone_Error_Rate   0x0009   195   085   051    Pre-fail
> Offline      -       191

The remaining values look OK.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2011-11-02 21:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 18:58 [gentoo-user] Does this drive need a funeral? Dale
2011-11-01 19:07 ` Mark Knecht
2011-11-01 19:47   ` Dale
2011-11-01 19:58     ` Michael Mol
2011-11-01 20:04     ` Joost Roeleveld
2011-11-02  1:17 ` Dale
2011-11-02  1:35   ` Dale
2011-11-02 14:02     ` Michael Mol
2011-11-02 14:07       ` Neil Bothwick
2011-11-02 15:29         ` Dale
2011-11-02 14:15   ` Lorenzo Bandieri
2011-11-02 14:18     ` Lorenzo Bandieri
2011-11-02 14:52       ` Pandu Poluan
2011-11-02 15:33     ` Dale
2011-11-02 16:51   ` James Broadhead
2011-11-02 17:16     ` Dale
2011-11-02 21:01 ` Mick [this message]

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=201111022101.45018.michaelkintzios@gmail.com \
    --to=michaelkintzios@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