From: | Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | SMART attributes for SSD (was: SSDD reliability) |
Date: | 2011-05-06 01:50:13 |
Message-ID: | 4DC353D5.90508@strategicdata.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/05/11 22:50, David Boreham wrote:
> On 5/4/2011 11:50 PM, Toby Corkindale wrote:
>>
>> In what way has the SMART read failed?
>> (I get the relevant values out successfully myself, and have Munin
>> graph them.)
> Mis-parse :) It was my _attempts_ to read SMART that failed.
> Specifically, I was able to read a table of numbers from the drive, but
> none of the numbers looked particularly useful or likely to be a "time
> to live" number. Similar to traditional drives, where you get this table
> of numbers that are either zero or random, that you look at saying
> "Huh?", all of which are flagged as "failing". Perhaps I'm using the
> wrong SMART groking tools ?
I run:
sudo smartctl -a /dev/sda
And amongst the usual values, I also get:
232 Available_Reservd_Space 0x0002 100 048 000 Old_age Always
- 9011683733561
233 Media_Wearout_Indicator 0x0002 100 000 000 Old_age Always
- 0
The media wearout indicator is the useful one.
Plus some unknown attributes:
229 Unknown_Attribute 0x0002 100 000 000 Old_age Always
- 21941823264152
234 Unknown_Attribute 0x0002 100 000 000 Old_age Always
- 953583437830
235 Unknown_Attribute 0x0002 100 000 000 Old_age Always
- 1476591679
I found some suggested definitions for those attributes, but they didn't
seem to match up with my values once I decoded them, so mine must be
proprietary.
-Toby
From | Date | Subject | |
---|---|---|---|
Next Message | Toby Corkindale | 2011-05-06 02:02:12 | Re: Fwd: Re: SSDD reliability |
Previous Message | David Johnston | 2011-05-05 21:47:22 | Re: multiple sequence number for one column |