February 6, 201313 yr I have recently built my first unraid server. I am running WD green EZRX drives. I have just found out about the LLC parking issus with EARS and EADS drives. Does the issue still exist on the EZRX? If I run widdle3 will I lose data on these drives?
February 10, 201313 yr No,and no.. Only up until first generation EARX drives had the intellipark feature set at 8 seconds,all drive models after that is fine. I ran WDidle3 on all my EARS,EADS,and 1st gen. EARX to disable the intellipark completely all had data on them,and all are well.
February 10, 201313 yr Author Thanks for the input. Curious what did WD do to fix the EZRX drives? I do have a EARX to go in which is a refurb warranty recplacement to go in. So I will run widdle on it and leave the newer EZRX drives alone.
February 10, 201313 yr Only up until first generation EARX drives had the intellipark feature set at 8 seconds,all drive models after that is fine. Do you know whether this would have involved a firmware change? My EARS drives and my fairly recent EARX all report the same firmware: 51.0AB51
February 11, 201313 yr i just replied to the old thread too... i think the guy i quoted hasn't been on since October. I too would like to know what the consensus is. I know calling WD will get us nowhere. Can someone tell me if this looks serious? First Disk: 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 175 171 021 Pre-fail Always - 6216 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 24 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 17 10 Spin_Retry_Count 0x0032 100 253 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 - 24 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 22 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 58 194 Temperature_Celsius 0x0022 120 117 000 Old_age Always - 30 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 This is the next disk: 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 100 253 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 227 190 021 Pre-fail Always - 3641 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 17 10 Spin_Retry_Count 0x0032 100 253 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 - 15 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 14 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 41 194 Temperature_Celsius 0x0022 119 117 000 Old_age Always - 31 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 253 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 For what it's worth these drives have been in the server for less than a week, I haven't even pre-cleared or assigned array positions, yet. let me know if i am focusing on the wrong thing
February 11, 201313 yr FYI. I've never done anything for LCC's myself and I have no problem with my drives. Most of them started out with higher LCCs than power on hours but after thousands of hours of operation it has reversed. I now have a twice as many power on hours as LCC count. I would not worry about them unless you notice a problem. If your power on hours are in the thousands and the LCC count is in the tens or hundreds of thousands then try turning the head parking off. I've heard of drives with close to 1 million LCC counts still functioning fine - they didn't say how long after that but it was functioning fine at the check. If your drives spend 98% or more of their time asleep like mine then I think after 3-4 thousand power on hours you will find your LCCs still under 10,000. Now that I have close to 15,000 power on hours I still only have 7-8 thousand LCCs or less on my WD green drives.
February 14, 201313 yr I had the LCC problem on my WD10EZRX, solved by setting WDIDLE3 to /s60. Setting it to /d made the drive make strange noises, but maybe its because i didn't cycle power after using wdidle3. Before, in 2 days my LCC count went up to 800 with 20 power hours and the drive was making a lot of clicking sounds.
February 14, 201313 yr I had the LCC problem on my WD10EZRX, solved by setting WDIDLE3 to /s60. Setting it to /d made the drive make strange noises, but maybe its because i didn't cycle power after using wdidle3. Before, in 2 days my LCC count went up to 800 with 20 power hours and the drive was making a lot of clicking sounds. thanks -= how old is that drive? it' the 1TB version, right?
March 4, 201313 yr Bought WD20EZRX, Idle3 is set to 8 seconds, so you SHOULD use wdidle3 or similar program for linux idle3ctl
March 5, 201313 yr Bought WD20EZRX, Idle3 is set to 8 seconds, so you SHOULD use wdidle3 or similar program for linux idle3ctl is it the LCC count that's the most critical (indicative of the idle issue)?
Archived
This topic is now archived and is closed to further replies.