one more load-cycle-count problem

[Daniel O'Connor]

On Tue, 9 Feb 2010, Dan Naumov wrote:
> which essentially solves the problem. Note that going this route will
> probably involve rebuilding your entire array from scratch, because
> applying WDIDLE3 to the disk is likely to very slightly affect disk
> geometry, but just enough for hardware raid or ZFS or whatever to
> bark at you and refuse to continue using the drive in an existing
> pool (the affected disk can become very slightly smaller in
> capacity). Backup data, apply WDIDLE3 to all disks. Recreate the
> pool, restore backups. This will also void your warranty if used on
> the new WD drives, although it will still work just fine.

Errm.. Why would it change the geometry?

I have used this tool to change the settings on all my disks and it did 
not in any way cause a problem booting later.

My disks are WDC WD10EADS-00L5B1/01.01A01

(1Tb "green" disks)

AFAIK it just tunes EEPROM settings, it doesn't reflash the firmware.

That said I have heard reports of it bricking a drive so I would test it 
on one drive first (not that I did, I heard the bricking reports 
later..)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20100209/8b163583/attachment.pgp