by R.G. on Thu Dec 31, 2009 9:21 pm
Hi. First post.
This issue has been very much on my mind lately, as I'm trying to build up a home NAS, and I find I really don't like having WD first let me set the fail timeout, then remove that, forcing me to buy drives which cost twice as much. I'm sure the rationale is that the Raid Edition drives have much more than just TLER that is needed for Raids. However, I want a large, but slow and low power array, not a large, fast array using as much power as needed. Having to buy drives which use twice the power is almost as frustrating as paying twice as much.
It occurs to me that if the ERC/CCTL values do not persist past a power cycle, the obvious thing to do is to create a small driver which runs at power on and uses the correct interface to set the things to a shorter time out at each power on cycle. Things like displays and controllers need a power on driver to run. Why not disks?