From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Are those "green" drives any good?
Date: Thu, 10 May 2012 11:51:14 -0700 [thread overview]
Message-ID: <CAK2H+ed1DdB8q3fAU0Rw5sxHny2Rm9nTD4_W6x=6-9RwcXyXyA@mail.gmail.com> (raw)
In-Reply-To: <CAJoTvCs6RhW8T4F9EAjBaS+KCdvzDiZaYLvTwDkx5s_7Tf2vUA@mail.gmail.com>
On Thu, May 10, 2012 at 11:13 AM, Norman Invasion
<invasivenorman@gmail.com> wrote:
> On 10 May 2012 14:01, Mark Knecht <markknecht@gmail.com> wrote:
>> On Thu, May 10, 2012 at 9:20 AM, Norman Invasion
>> <invasivenorman@gmail.com> wrote:
>>> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> As some know, I'm planning to buy me a LARGE hard drive to put all my
>>>> videos on, eventually. The prices are coming down now. I keep seeing
>>>> these "green" drives that are made by just about every company nowadays.
>>>> When comparing them to a non "green" drive, do they hold up as good?
>>>> Are they as dependable as a plain drive? I guess they are more
>>>> efficient and I get that but do they break quicker, more often or no
>>>> difference?
>>>>
>>>> I have noticed that they tend to spin slower and are cheaper. That much
>>>> I have figured out. Other than that, I can't see any other difference.
>>>> Data speeds seem to be about the same.
>>>>
>>>
>>> They have an ugly tendency to nod off at 6 second intervals.
>>> This runs up "193 Load_Cycle_Count" unacceptably: as many
>>> as a few hundred thousand in a year & a million cycles is
>>> getting close to the lifetime limit on most hard drives. I end
>>> up running some iteration of
>>> # hdparm -B 255 /dev/sda
>>> every boot.
>>>
>>
>> Very true about the 193 count. Here's a drive in a system that was
>> built in Jan., 2010 so it's a bit over 2 years old at this point. It's
>> on 24/7 and not rebooted except for more major updates, etc. My tests
>> say the drive spins down and starts back up every 2 minutes and has
>> been doing so for about 28 months. IIRC the 193 spec on this drive was
>> something like 300000 max with the drive currently clocking in at
>> 700488. I don't see any evidence that it's going to fail but I am
>> trying to make sure it's backed up often. Being that it's gone >2x at
>> this point I will swap the drive out in the early summer no matter
>> what. This week I'll be visiting where the machine is so I'm going to
>> put a backup drive in the box to get ready.
>>
>
> Yes, I just learned about this problem in 2009 or so, &
> checked on my FreeBSD laptop, which turned out to be
> at >400000. It only made it another month or so before
> having unrecoverable errors.
>
> Now, I can't conclusively demonstrate that the 193
> Load_Cycle_Count was somehow causitive, but I
> gots my suspicions. Many of 'em highly suspectable.
>
It's part of the 'Wear Out Failure' part of the Bathtub Curve posted
in the last few days. That said, some Toyotas go 100K miles, and
others go 500K miles. Same car, same spec, same production line,
different owners, different roads, different climates, etc.
It's not possible to absolutely know when any drive will fail. I
suspect that the 300K spec is just that, a spec. They'd replace the
drive if it failed at 299,999 and wouldn't replace it at 300,001. That
said, they don't want to spec thing too tightly, and I doubt many
people make a purchasing decision on a spec like this, so for the vast
majority of drives most likely they'd do far more than 300K.
At 2 minutes per count on that specific WD Green Drive, if a home
machine is turned on for instance 5 hours a day (6PM to 11PM) then
300K count equates to around 6 years. To me that seems pretty generous
for a low cost home machine. However for a 24/7 production server it's
a pretty fast replacement schedule.
Here's data for my 500GB WD RAID Edition drives in my compute server
here. It's powered down almost every night but doesn't suffer from the
same firmware issues. The machine was built in April, 2010, so it's a
bit of 2 years old. Note that it's been powered on less than 1/2 the
number of hours but only has a 193 count of 907 vs > 700000!
Cheers,
Mark
c2stable ~ # smartctl -a /dev/sda
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.12-gentoo] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Western Digital RE3 Serial ATA
Device Model: WDC WD5002ABYS-02B1B0
Serial Number: WD-WCASYA846988
LU WWN Device Id: 5 0014ee 2042c3477
Firmware Version: 02.03B03
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Thu May 10 11:45:45 2012 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an
interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 9480) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test
supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before
entering
power-saving mode.
Supports SMART auto save
timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging
supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 112) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Error Recovery Control
supported.
SCT Feature Control supported.
SCT Data Table supported.
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 0x002f 200 200 051 Pre-fail
Always - 0
3 Spin_Up_Time 0x0027 239 235 021 Pre-fail
Always - 1050
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 935
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail
Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age
Always - 0
9 Power_On_Hours 0x0032 091 091 000 Old_age
Always - 7281
10 Spin_Retry_Count 0x0032 100 100 000 Old_age
Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age
Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age
Always - 933
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age
Always - 27
193 Load_Cycle_Count 0x0032 200 200 000 Old_age
Always - 907
194 Temperature_Celsius 0x0022 106 086 000 Old_age
Always - 41
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age
Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age
Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age
Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age
Offline - 0
next prev parent reply other threads:[~2012-05-10 18:53 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 8:47 [gentoo-user] Are those "green" drives any good? Dale
2012-05-09 9:25 ` Alan McKinnon
2012-05-09 9:52 ` Dale
2012-05-09 11:32 ` Daniel Troeder
2012-05-09 11:51 ` Dale
2012-05-10 19:39 ` David Haller
2012-05-09 21:28 ` Alan McKinnon
2012-05-09 22:24 ` Dale
2012-05-09 22:48 ` Paul Hartman
2012-05-09 23:49 ` Dale
2012-05-10 1:39 ` Pandu Poluan
2012-05-10 1:52 ` Adam Carter
2012-05-10 12:53 ` Todd Goodman
2012-05-09 23:37 ` Mark Knecht
2012-05-09 23:58 ` Dale
2012-05-10 7:03 ` Mick
2012-05-10 11:55 ` napalm
2012-05-10 12:38 ` Dale
2012-05-10 13:27 ` napalm
2012-05-10 21:39 ` Dale
2012-05-10 22:53 ` Paul Hartman
2012-05-11 0:07 ` Neil Bothwick
2012-05-11 1:10 ` David Haller
2012-05-10 19:38 ` David Haller
2012-05-10 21:13 ` Alan McKinnon
2012-05-09 11:47 ` Tanstaafl
2012-05-09 12:06 ` mike
2012-05-09 13:30 ` Tanstaafl
2012-05-09 12:29 ` Mark Knecht
2012-05-09 16:39 ` Pandu Poluan
2012-05-09 17:28 ` Mark Knecht
2012-05-09 18:42 ` Paul Hartman
2012-05-09 18:53 ` Mark Knecht
2012-05-10 14:20 ` [gentoo-user] make of gentoo-sources-3.2.12 fails Michael Scherer
2012-05-10 14:50 ` Pandu Poluan
2012-05-10 19:57 ` Michael Scherer
2012-05-10 21:08 ` Stroller
2012-05-11 1:01 ` Michael Scherer
2012-05-11 5:18 ` Joshua Murphy
2012-05-11 12:59 ` Michael Scherer
2012-05-11 17:56 ` Michael Scherer
2012-05-11 10:20 ` Alan McKinnon
2012-05-11 22:48 ` [gentoo-user] " walt
2012-05-12 1:31 ` Michael Scherer
2012-05-12 18:17 ` walt
2012-05-14 1:44 ` Michael Scherer
2012-05-14 2:13 ` ny6p01
2012-05-14 15:26 ` Michael Scherer
2012-05-14 15:37 ` Alan McKinnon
2012-05-14 15:52 ` ny6p01
2012-05-26 11:18 ` luis jure
2012-05-26 13:56 ` ny6p01
2012-05-14 16:13 ` Allan Gottlieb
2012-05-14 17:13 ` Dale
2012-05-14 20:54 ` Alan McKinnon
2012-05-15 0:46 ` Dale
2012-05-15 17:01 ` Mark Knecht
2012-05-15 17:15 ` Dale
2012-05-15 21:12 ` Alan McKinnon
2012-05-18 12:29 ` Willie WY Wong
2012-05-15 17:25 ` john
2012-05-15 23:26 ` Peter Humphrey
2012-05-16 0:41 ` Pandu Poluan
2012-05-17 16:14 ` Michael Scherer
2012-05-17 17:05 ` Dale
2012-05-17 19:13 ` Michael Scherer
2012-05-17 17:13 ` Neil Bothwick
2012-05-17 18:58 ` Michael Scherer
2012-05-17 17:47 ` Tanstaafl
2012-05-17 19:14 ` ny6p01
2012-05-17 19:25 ` Alan McKinnon
2012-05-17 23:56 ` Peter Humphrey
2012-05-17 19:29 ` Michael Scherer
2012-05-17 21:10 ` Michael Mol
2012-05-17 18:06 ` Pandu Poluan
2012-05-17 20:13 ` Michael Scherer
2012-05-17 20:50 ` Hinnerk van Bruinehsen
2012-05-21 3:24 ` Joshua Murphy
2012-07-03 11:11 ` [gentoo-user] Re: make of gentoo-sources-3.2.12 fails [SOLVED] Michael Scherer
2012-05-17 20:51 ` [gentoo-user] Re: make of gentoo-sources-3.2.12 fails Michael Scherer
2012-05-17 20:59 ` Alex Schuster
2012-05-23 2:10 ` Michael Scherer
2012-05-23 6:05 ` Pandu Poluan
2012-05-19 3:18 ` Volker Armin Hemmann
2012-05-19 16:59 ` Arttu V.
2012-05-26 11:33 ` luis jure
2012-05-14 18:25 ` Tanstaafl
2012-05-14 19:11 ` Alecks Gates
2012-05-14 19:23 ` Michael Mol
2012-05-15 0:03 ` Pandu Poluan
2012-05-15 0:05 ` Alecks Gates
2012-05-15 0:16 ` Pandu Poluan
2012-05-14 20:51 ` Alan McKinnon
2012-05-14 21:01 ` Michael Mol
2012-05-14 21:24 ` Alan McKinnon
2012-05-14 21:53 ` Neil Bothwick
2012-05-14 23:23 ` Alan McKinnon
2012-05-14 23:35 ` Michael Mol
2012-05-14 23:26 ` Michael Mol
2012-05-14 23:55 ` Pandu Poluan
2012-05-14 21:56 ` Neil Bothwick
2012-05-09 13:15 ` [gentoo-user] Are those "green" drives any good? Volker Armin Hemmann
2012-05-09 22:37 ` Dale
2012-05-10 16:20 ` Norman Invasion
2012-05-10 18:01 ` Mark Knecht
2012-05-10 18:13 ` Norman Invasion
2012-05-10 18:51 ` Mark Knecht [this message]
2012-05-12 9:34 ` Mick
2012-05-12 9:49 ` Volker Armin Hemmann
2012-05-13 9:35 ` David Haller
2012-05-10 19:24 ` David Haller
2012-05-11 1:15 ` Bill Kenworthy
2012-05-12 18:50 ` Frank Steinmetzger
2012-05-13 9:38 ` David Haller
2012-05-21 21:05 ` Frank Steinmetzger
2012-05-21 22:44 ` Andrew Hoffman
2012-05-10 19:36 ` David Haller
2012-05-10 21:25 ` Neil Bothwick
2012-05-10 20:17 ` Mark Knecht
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='CAK2H+ed1DdB8q3fAU0Rw5sxHny2Rm9nTD4_W6x=6-9RwcXyXyA@mail.gmail.com' \
--to=markknecht@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