- Feb 15, 2014
Probably nonsense, could be a firmware bug in a specific model.
That is fake news!Somebody has posted on a YouTube video saying that the wdidle3 /d command doesn't disable head parking, just the timer, so it actually parks the heads immediately after read/writing.
I'm going to assume that person is completely misinformed? I've had the timers disabled on 4 2TB Blue drives and the load/unload cycle count has barely changed in months. Wouldn't my load/unload cycle count be massive if it were parking immediately?
Pretty sure it's complete nonsense, but just wanted to be sure.
True statement, the head loading count would increment at the same rate as the power cycles counter assuming the drive is not being commanded to spin down.load/unload cycle would increase much faster.
That might not be totaly wrong. I've had WD drives that increased head parks by the thousands in a few minutes after using /d parameter. They started to behave as soon as I rebooted tho.
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 182 175 021 Pre-fail Always - 5866 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 95 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 057 057 000 Old_age Always - 31642 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 - 95 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 37 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 966909 194 Temperature_Celsius 0x0022 111 110 000 Old_age Always - 39 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 200 200 000 Old_age Offline - 0
TL;DR - does it still apply? I have 2 WD Red 6TB Nasware 3.0 (non-pro) HDDs.*NOTE*: Some of this info applies to WD Reds. So if you have WD Reds you may want to read this and see if this applies to you.
The 2 TBs are thinner (7 or 9mm IIRC).
Just joined the community to thank the OP for his help.
I did this to two brand new greens. The thing is that after I did it I tried the /R switch to double check, but the command halts at Configure Idle3.
It does the same for both drives. Any ideas why?
OUCH! The green drive is having power cycled on it an average of 5.2 times a day, the black drive is just over 4 times a day. But to address the reason of your posting, the black drive is likely being woke up every 5 minutes due to some maintenance activity (you probably have your Dataset on that drive or are using SWAP on that drive or both. Then after a minute or so the drive sleeps again. The cycle repeats forever. Your green drive looks like it sleeps a lot, just over 5 times a day and thus causing your counts to go up, but the headload count is not the issue, the drive power cycling is of concern. I know you didn't ask for any advice but that is what happens when you post to an active thread.
Isn't it the opposite here?black drive is likely being woke up every 5 minutes due to some maintenance activity (you probably have your Dataset on that drive or are using SWAP on that drive or both. Then after a minute or so the drive sleeps again. The cycle repeats forever. Your green drive looks like it sleeps a lot, just over 5 times