WD2002FYPS - 2TB

Quicker wrote:

Bottom line: exactly the same drive firmware, exactly the same symptoms. LCC is increasing very rapidly. Sigh. Sorry I don't have your endurance in reporting everything here :) but my S.M.A.R.T. reports look basicly the same as yours before your idle 3 timer tweak. I even noted that Power on Hours was 240 hrs (or little more) on each drive! Maybe they "pre-burn" electronics at the factory for ten days to find faulty units.

All looks good on my side so far with the LCC only increasing by 100 after about 250 hours. :D The increase in 100 is probably accounted for by the NAS automatically powering off for 8 hours per day and the drives being put to sleep by the NAS after 20 minutes of inactivity.

SMART Information for Disk 1

Model: WDC WD2002FYPS-01U1B0
Serial: WD-WCAVY-----44
Firmware: 04.05G04

SMART Attribute
Raw Read Error Rate 0 ; Spin Up Time 9283 ; Start Stop Count 108 ; Reallocated Sector Count 0 ; Seek Error Rate 0 ; Power On Hours 559 ; Spin Retry Count 0 ; Calibration Retry Count 0 ; Power Cycle Count 26 ; Power-Off Retract Count 6 ; Load Cycle Count 2017 ; Temperature Celsius 41 ; Reallocated Event Count 0 ; Current Pending Sector 0 ; Offline Uncorrectable 0 ; UDMA CRC Error Count 0 ; Multi Zone Error Rate 0 ; ATA Error Count 0

Further information that might help ... I have the following Performance options set ...

[x] Enable disk write cache. Disk write cache allows ...
[x] Disable full data journaling. Full data journaling makes a backup ...
[x] Disable journaling. Journaling allows very quick file system ...
[ ] Optimize for OS X. Enable this option for best performance in Mac OS X ...
[x] Enable fast CIFS writes. This option allows for optimal write performance ...
[ ] Enable fast USB disk writes. This option speeds up USB write access by ...

... And the following Power options set.

[x] Enable disk spin-down after 20 minutes of inactivity.
[x] Enable power timer ...
[ ] Enable monitoring of UPS physically attached to a remote ReadyNAS.
[ ] Enable Wake-on-LAN service.

@Quicker ... Did you try the 255 or 254 (like I did) millisecond delay? Also, where did you download your WDIdle3 application from and what version was it?


Thanks,