From owner-freebsd-stable@FreeBSD.ORG Tue Feb 9 00:29:36 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 838B5106566C for ; Tue, 9 Feb 2010 00:29:36 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id D53858FC12 for ; Tue, 9 Feb 2010 00:29:35 +0000 (UTC) Received: from inchoate.gsoft.com.au ([203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id o190TVlq042063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 9 Feb 2010 10:59:31 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 9 Feb 2010 10:59:21 +1030 User-Agent: KMail/1.9.10 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4814856.fuMKQumRO5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201002091059.28625.doconnor@gsoft.com.au> X-Spam-Score: -3.641 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Dan Naumov Subject: Re: one more load-cycle-count problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2010 00:29:36 -0000 --nextPart4814856.fuMKQumRO5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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=20 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=20 on one drive first (not that I did, I heard the bricking reports=20 later..) =2D-=20 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 --nextPart4814856.fuMKQumRO5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBLcKxo5ZPcIHs/zowRAu6+AJ0YtVNOAg8LWLp2dgkv3x+NvnlNrACgmTot 0eibJt0w5WCP0RtCGnX0tMY= =oSmG -----END PGP SIGNATURE----- --nextPart4814856.fuMKQumRO5--