Preclearing WD30EFRX


Recommended Posts

NO don't run it.  There is NO problem with LCCs on the RED drives.  They are designed for NAS boxes rather than low power so they don't need to park the heads as often.  I have some REDs myself and I'll have to verify tonight but I believe one has about 50 LCC with a 1000 power on hours.

 

 

Edit: I was a little off it is 80 LCC count and 2444 power on hours:

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD20EFRX-68AX9N0
Serial Number:    WD-WMC300511324
Firmware Version: 80.00A80
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   9
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu Feb 14 17:04:44 2013 CST
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:  (0x00)	Offline data collection activity
				was never started.
				Auto Offline Data Collection: Disabled.
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: 		 (27720) 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: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x70bd)	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   174   172   021    Pre-fail  Always       -       4275
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       129
  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   097   097   000    Old_age   Always       -       2444
10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       52
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       49
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       80
194 Temperature_Celsius     0x0022   128   115   000    Old_age   Always       -       19
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   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   100   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


Link to comment

Can I just ask what your bad experience was? I myself have never had anything go bad with Western Digital and I'm about to buy three more of their 3TB red drives.

 

I had 4 in my NAS, 3 of them got an increasing amount of reallocated and pending secors in SMART after 12-15months, all have been RMAd and on the positive side were advanced replaced. Currently here in Europe WD is the only one that seems to offer advanced replacement. Maybe it was a bad batch of drives. At that time I also learned about WDIDLE. I hadn't used it on the drives that went bad. My NAS did signal the bad disks and were replaced in time. But replacing the disk and rebuilding a RAID5 array is annoying and doing this 3 time in 2 months pissed me off. Excuse me for the bad language. There are still a couple of WD20EARS the seem to hold fine (knock on wood). I just hope the WD30EFRX will be a better experience.

Link to comment

Can I just ask what your bad experience was? I myself have never had anything go bad with Western Digital and I'm about to buy three more of their 3TB red drives.

 

I had 4 in my NAS, 3 of them got an increasing amount of reallocated and pending secors in SMART after 12-15months, all have been RMAd and on the positive side were advanced replaced. Currently here in Europe WD is the only one that seems to offer advanced replacement. Maybe it was a bad batch of drives. At that time I also learned about WDIDLE. I hadn't used it on the drives that went bad. My NAS did signal the bad disks and were replaced in time. But replacing the disk and rebuilding a RAID5 array is annoying and doing this 3 time in 2 months pissed me off. Excuse me for the bad language. There are still a couple of WD20EARS the seem to hold fine (knock on wood). I just hope the WD30EFRX will be a better experience.

 

Lots of the negative reviews of drives on places like Newegg are for exactly the same complaints listed here and I think it's unfair to the manufacturers. Green drives are not intended to be used in always spun up RAID5 arrays. wdidle3 can help but the firmware on the drives is simply not designed to cope with that type of usage. This is the whole reason the Red series of drives was created. Before this you really needed to use pro-sumer (like the WD Black series) or enterprise class drives in RAID5 arrays to avoid those problems. Those drives were a lot more expensive so people just bought green drives and then they'd fail. Unfortunately Red drives still have enough of a premium that people will probably still continue to buy greens for RAID5 and they'll continue to fail. That's one of the great features of unraid, that these green drives can be used without those issues.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.