| 1 |
Am Samstag, 12. Mai 2012, 10:34:12 schrieb Mick: |
| 2 |
> On Thursday 10 May 2012 19:51:14 Mark Knecht wrote: |
| 3 |
> > On Thu, May 10, 2012 at 11:13 AM, Norman Invasion |
| 4 |
> > |
| 5 |
> > <invasivenorman@×××××.com> wrote: |
| 6 |
> > > On 10 May 2012 14:01, Mark Knecht <markknecht@×××××.com> wrote: |
| 7 |
> > >> On Thu, May 10, 2012 at 9:20 AM, Norman Invasion |
| 8 |
> > >> |
| 9 |
> > >> <invasivenorman@×××××.com> wrote: |
| 10 |
> > >>> On 9 May 2012 04:47, Dale <rdalek1967@×××××.com> wrote: |
| 11 |
> > >>>> Hi, |
| 12 |
> > >>>> |
| 13 |
> > >>>> As some know, I'm planning to buy me a LARGE hard drive to put all my |
| 14 |
> > >>>> videos on, eventually. The prices are coming down now. I keep |
| 15 |
> > >>>> seeing |
| 16 |
> > >>>> these "green" drives that are made by just about every company |
| 17 |
> > >>>> nowadays. When comparing them to a non "green" drive, do they hold up |
| 18 |
> > >>>> as good? Are they as dependable as a plain drive? I guess they are |
| 19 |
> > >>>> more efficient and I get that but do they break quicker, more often |
| 20 |
> > >>>> or no difference? |
| 21 |
> > >>>> |
| 22 |
> > >>>> I have noticed that they tend to spin slower and are cheaper. That |
| 23 |
> > >>>> much I have figured out. Other than that, I can't see any other |
| 24 |
> > >>>> difference. Data speeds seem to be about the same. |
| 25 |
> > >>> |
| 26 |
> > >>> They have an ugly tendency to nod off at 6 second intervals. |
| 27 |
> > >>> This runs up "193 Load_Cycle_Count" unacceptably: as many |
| 28 |
> > >>> as a few hundred thousand in a year & a million cycles is |
| 29 |
> > >>> getting close to the lifetime limit on most hard drives. I end |
| 30 |
> > >>> up running some iteration of |
| 31 |
> > >>> # hdparm -B 255 /dev/sda |
| 32 |
> > >>> every boot. |
| 33 |
> > >> |
| 34 |
> > >> Very true about the 193 count. Here's a drive in a system that was |
| 35 |
> > >> built in Jan., 2010 so it's a bit over 2 years old at this point. It's |
| 36 |
> > >> on 24/7 and not rebooted except for more major updates, etc. My tests |
| 37 |
> > >> say the drive spins down and starts back up every 2 minutes and has |
| 38 |
> > >> been doing so for about 28 months. IIRC the 193 spec on this drive was |
| 39 |
> > >> something like 300000 max with the drive currently clocking in at |
| 40 |
> > >> 700488. I don't see any evidence that it's going to fail but I am |
| 41 |
> > >> trying to make sure it's backed up often. Being that it's gone >2x at |
| 42 |
> > >> this point I will swap the drive out in the early summer no matter |
| 43 |
> > >> what. This week I'll be visiting where the machine is so I'm going to |
| 44 |
> > >> put a backup drive in the box to get ready. |
| 45 |
> > > |
| 46 |
> > > Yes, I just learned about this problem in 2009 or so, & |
| 47 |
> > > checked on my FreeBSD laptop, which turned out to be |
| 48 |
> > > at >400000. It only made it another month or so before |
| 49 |
> > > having unrecoverable errors. |
| 50 |
> > > |
| 51 |
> > > Now, I can't conclusively demonstrate that the 193 |
| 52 |
> > > Load_Cycle_Count was somehow causitive, but I |
| 53 |
> > > gots my suspicions. Many of 'em highly suspectable. |
| 54 |
> > |
| 55 |
> > It's part of the 'Wear Out Failure' part of the Bathtub Curve posted |
| 56 |
> > in the last few days. That said, some Toyotas go 100K miles, and |
| 57 |
> > others go 500K miles. Same car, same spec, same production line, |
| 58 |
> > different owners, different roads, different climates, etc. |
| 59 |
> > |
| 60 |
> > It's not possible to absolutely know when any drive will fail. I |
| 61 |
> > suspect that the 300K spec is just that, a spec. They'd replace the |
| 62 |
> > drive if it failed at 299,999 and wouldn't replace it at 300,001. That |
| 63 |
> > said, they don't want to spec thing too tightly, and I doubt many |
| 64 |
> > people make a purchasing decision on a spec like this, so for the vast |
| 65 |
> > majority of drives most likely they'd do far more than 300K. |
| 66 |
> > |
| 67 |
> > At 2 minutes per count on that specific WD Green Drive, if a home |
| 68 |
> > machine is turned on for instance 5 hours a day (6PM to 11PM) then |
| 69 |
> > 300K count equates to around 6 years. To me that seems pretty generous |
| 70 |
> > for a low cost home machine. However for a 24/7 production server it's |
| 71 |
> > a pretty fast replacement schedule. |
| 72 |
> > |
| 73 |
> > Here's data for my 500GB WD RAID Edition drives in my compute server |
| 74 |
> > here. It's powered down almost every night but doesn't suffer from the |
| 75 |
> > same firmware issues. The machine was built in April, 2010, so it's a |
| 76 |
> > bit of 2 years old. Note that it's been powered on less than 1/2 the |
| 77 |
> > number of hours but only has a 193 count of 907 vs > 700000! |
| 78 |
> > |
| 79 |
> > Cheers, |
| 80 |
> > Mark |
| 81 |
> > |
| 82 |
> > |
| 83 |
> > c2stable ~ # smartctl -a /dev/sda |
| 84 |
> > smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.12-gentoo] (local build) |
| 85 |
> > Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net |
| 86 |
> > |
| 87 |
> > === START OF INFORMATION SECTION === |
| 88 |
> > Model Family: Western Digital RE3 Serial ATA |
| 89 |
> > Device Model: WDC WD5002ABYS-02B1B0 |
| 90 |
> > Serial Number: WD-WCASYA846988 |
| 91 |
> > LU WWN Device Id: 5 0014ee 2042c3477 |
| 92 |
> > Firmware Version: 02.03B03 |
| 93 |
> > User Capacity: 500,107,862,016 bytes [500 GB] |
| 94 |
> > Sector Size: 512 bytes logical/physical |
| 95 |
> > Device is: In smartctl database [for details use: -P show] |
| 96 |
> > ATA Version is: 8 |
| 97 |
> > ATA Standard is: Exact ATA specification draft version not indicated |
| 98 |
> > Local Time is: Thu May 10 11:45:45 2012 PDT |
| 99 |
> > SMART support is: Available - device has SMART capability. |
| 100 |
> > SMART support is: Enabled |
| 101 |
> > |
| 102 |
> > === START OF READ SMART DATA SECTION === |
| 103 |
> > SMART overall-health self-assessment test result: PASSED |
| 104 |
> > |
| 105 |
> > General SMART Values: |
| 106 |
> > Offline data collection status: (0x84) Offline data collection activity |
| 107 |
> > |
| 108 |
> > was suspended by an |
| 109 |
> > |
| 110 |
> > interrupting command from host. |
| 111 |
> > |
| 112 |
> > Auto Offline Data Collection: |
| 113 |
> > Enabled. Self-test execution status: ( 0) The previous self-test |
| 114 |
> > routine completed without error or no self-test has ever been run. |
| 115 |
> > Total time to complete Offline |
| 116 |
> > data collection: ( 9480) seconds. |
| 117 |
> > Offline data collection |
| 118 |
> > capabilities: (0x7b) SMART execute Offline immediate. |
| 119 |
> > |
| 120 |
> > Auto Offline data collection |
| 121 |
> > |
| 122 |
> > on/off support. |
| 123 |
> > |
| 124 |
> > Suspend Offline collection upon |
| 125 |
> > new |
| 126 |
> > command. |
| 127 |
> > Offline surface scan supported. |
| 128 |
> > Self-test supported. |
| 129 |
> > Conveyance Self-test |
| 130 |
> > |
| 131 |
> > supported. |
| 132 |
> > |
| 133 |
> > Selective Self-test supported. |
| 134 |
> > |
| 135 |
> > SMART capabilities: (0x0003) Saves SMART data before |
| 136 |
> > entering |
| 137 |
> > |
| 138 |
> > power-saving mode. |
| 139 |
> > Supports SMART auto save |
| 140 |
> > |
| 141 |
> > timer. |
| 142 |
> > Error logging capability: (0x01) Error logging supported. |
| 143 |
> > |
| 144 |
> > General Purpose Logging |
| 145 |
> > |
| 146 |
> > supported. |
| 147 |
> > Short self-test routine |
| 148 |
> > recommended polling time: ( 2) minutes. |
| 149 |
> > Extended self-test routine |
| 150 |
> > recommended polling time: ( 112) minutes. |
| 151 |
> > Conveyance self-test routine |
| 152 |
> > recommended polling time: ( 5) minutes. |
| 153 |
> > SCT capabilities: (0x303f) SCT Status supported. |
| 154 |
> > |
| 155 |
> > SCT Error Recovery Control |
| 156 |
> > |
| 157 |
> > supported. |
| 158 |
> > |
| 159 |
> > SCT Feature Control supported. |
| 160 |
> > SCT Data Table supported. |
| 161 |
> > |
| 162 |
> > SMART Attributes Data Structure revision number: 16 |
| 163 |
> > Vendor Specific SMART Attributes with Thresholds: |
| 164 |
> > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE |
| 165 |
> > UPDATED WHEN_FAILED RAW_VALUE |
| 166 |
> > |
| 167 |
> > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail |
| 168 |
> > |
| 169 |
> > Always - 0 |
| 170 |
> > |
| 171 |
> > 3 Spin_Up_Time 0x0027 239 235 021 Pre-fail |
| 172 |
> > |
| 173 |
> > Always - 1050 |
| 174 |
> > |
| 175 |
> > 4 Start_Stop_Count 0x0032 100 100 000 Old_age |
| 176 |
> > |
| 177 |
> > Always - 935 |
| 178 |
> > |
| 179 |
> > 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail |
| 180 |
> > |
| 181 |
> > Always - 0 |
| 182 |
> > |
| 183 |
> > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age |
| 184 |
> > |
| 185 |
> > Always - 0 |
| 186 |
> > |
| 187 |
> > 9 Power_On_Hours 0x0032 091 091 000 Old_age |
| 188 |
> > |
| 189 |
> > Always - 7281 |
| 190 |
> > |
| 191 |
> > 10 Spin_Retry_Count 0x0032 100 100 000 Old_age |
| 192 |
> > |
| 193 |
> > Always - 0 |
| 194 |
> > |
| 195 |
> > 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age |
| 196 |
> > |
| 197 |
> > Always - 0 |
| 198 |
> > |
| 199 |
> > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age |
| 200 |
> > |
| 201 |
> > Always - 933 |
| 202 |
> > 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age |
| 203 |
> > Always - 27 |
| 204 |
> > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age |
| 205 |
> > Always - 907 |
| 206 |
> > 194 Temperature_Celsius 0x0022 106 086 000 Old_age |
| 207 |
> > Always - 41 |
| 208 |
> > 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age |
| 209 |
> > Always - 0 |
| 210 |
> > 197 Current_Pending_Sector 0x0032 200 200 000 Old_age |
| 211 |
> > Always - 0 |
| 212 |
> > 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age |
| 213 |
> > Offline - 0 |
| 214 |
> > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age |
| 215 |
> > Always - 0 |
| 216 |
> > 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age |
| 217 |
> > Offline - 0 |
| 218 |
> |
| 219 |
> Is this 193 Load_Cycle_Count an issue only on the green drives? |
| 220 |
> |
| 221 |
> I have a very old Compaq laptop here that shows: |
| 222 |
> |
| 223 |
> # smartctl -A /dev/sda | egrep "Power_On|Load_Cycle" |
| 224 |
> 9 Power_On_Hours 0x0012 055 055 000 Old_age Always |
| 225 |
> - 19830 |
| 226 |
> 193 Load_Cycle_Count 0x0012 001 001 000 Old_age Always |
| 227 |
> - 1739734 |
| 228 |
> |
| 229 |
> Admittedly, there are some 60 errors on it (having been used extensively on |
| 230 |
> bouncy trains, buses, aeroplanes, etc) but it is still refusing to die ... |
| 231 |
> O_O |
| 232 |
> |
| 233 |
> It is a Hitachi 20G |
| 234 |
> |
| 235 |
> === START OF INFORMATION SECTION === |
| 236 |
> Model Family: Hitachi Travelstar 80GN |
| 237 |
> Device Model: IC25N020ATMR04-0 |
| 238 |
> Serial Number: MRX107K1DS623H |
| 239 |
> Firmware Version: MO1OAD5A |
| 240 |
> User Capacity: 20,003,880,960 bytes [20.0 GB] |
| 241 |
> Sector Size: 512 bytes logical/physical |
| 242 |
> Device is: In smartctl database [for details use: -P show] |
| 243 |
> ATA Version is: 6 |
| 244 |
> ATA Standard is: ATA/ATAPI-6 T13 1410D revision 3a |
| 245 |
> Local Time is: Sat May 12 10:30:13 2012 BST |
| 246 |
> SMART support is: Available - device has SMART capability. |
| 247 |
> SMART support is: Enabled |
| 248 |
> |
| 249 |
> === START OF READ SMART DATA SECTION === |
| 250 |
|
| 251 |
SAMSUNG HD502IJ |
| 252 |
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED |
| 253 |
WHEN_FAILED RAW_VALUE |
| 254 |
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always |
| 255 |
- 0 |
| 256 |
3 Spin_Up_Time 0x0007 085 085 011 Pre-fail Always |
| 257 |
- 5480 |
| 258 |
4 Start_Stop_Count 0x0032 098 098 000 Old_age Always |
| 259 |
- 1864 |
| 260 |
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always |
| 261 |
- 0 |
| 262 |
7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always |
| 263 |
- 0 |
| 264 |
8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - |
| 265 |
10814 |
| 266 |
9 Power_On_Hours 0x0032 096 096 000 Old_age Always |
| 267 |
- 20178 |
| 268 |
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always |
| 269 |
- 0 |
| 270 |
11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always |
| 271 |
- 0 |
| 272 |
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always |
| 273 |
- 1854 |
| 274 |
13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always |
| 275 |
- 0 |
| 276 |
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always |
| 277 |
- 8 |
| 278 |
184 End-to-End_Error 0x0033 100 100 099 Pre-fail Always |
| 279 |
- 0 |
| 280 |
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always |
| 281 |
- 0 |
| 282 |
188 Command_Timeout 0x0032 100 100 000 Old_age Always |
| 283 |
- 0 |
| 284 |
190 Airflow_Temperature_Cel 0x0022 082 065 000 Old_age Always |
| 285 |
- 18 (Min/Max 13/18) |
| 286 |
194 Temperature_Celsius 0x0022 079 061 000 Old_age Always |
| 287 |
- 21 (Min/Max 13/21) |
| 288 |
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always |
| 289 |
- 2587 |
| 290 |
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always |
| 291 |
- 0 |
| 292 |
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always |
| 293 |
- 0 |
| 294 |
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - |
| 295 |
0 |
| 296 |
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always |
| 297 |
- 0 |
| 298 |
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always |
| 299 |
- 0 |
| 300 |
201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always |
| 301 |
- 0 |
| 302 |
|
| 303 |
|
| 304 |
SAMSUNG HD753LJ: |
| 305 |
|
| 306 |
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED |
| 307 |
WHEN_FAILED RAW_VALUE |
| 308 |
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always |
| 309 |
- 0 |
| 310 |
3 Spin_Up_Time 0x0007 075 075 011 Pre-fail Always |
| 311 |
- 8330 |
| 312 |
4 Start_Stop_Count 0x0032 099 099 000 Old_age Always |
| 313 |
- 1399 |
| 314 |
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always |
| 315 |
- 0 |
| 316 |
7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always |
| 317 |
- 0 |
| 318 |
8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - |
| 319 |
10041 |
| 320 |
9 Power_On_Hours 0x0032 097 097 000 Old_age Always |
| 321 |
- 16941 |
| 322 |
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always |
| 323 |
- 0 |
| 324 |
11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always |
| 325 |
- 0 |
| 326 |
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always |
| 327 |
- 1397 |
| 328 |
13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always |
| 329 |
- 0 |
| 330 |
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always |
| 331 |
- 0 |
| 332 |
184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always |
| 333 |
- 0 |
| 334 |
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always |
| 335 |
- 0 |
| 336 |
188 Command_Timeout 0x0032 100 100 000 Old_age Always |
| 337 |
- 0 |
| 338 |
190 Airflow_Temperature_Cel 0x0022 081 065 000 Old_age Always |
| 339 |
- 19 (Min/Max 12/19) |
| 340 |
194 Temperature_Celsius 0x0022 077 064 000 Old_age Always |
| 341 |
- 23 (Min/Max 12/23) |
| 342 |
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always |
| 343 |
- 1412 |
| 344 |
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always |
| 345 |
- 0 |
| 346 |
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always |
| 347 |
- 0 |
| 348 |
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - |
| 349 |
0 |
| 350 |
199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always |
| 351 |
- 0 |
| 352 |
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always |
| 353 |
- 0 |
| 354 |
201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always |
| 355 |
- 0 |
| 356 |
|
| 357 |
i have some more disks, but those clocked the most hours. |
| 358 |
|
| 359 |
|
| 360 |
-- |
| 361 |
#163933 |
Archives