From owner-freebsd-hardware@FreeBSD.ORG Thu Aug 4 15:27:58 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86DFD16A41F for ; Thu, 4 Aug 2005 15:27:58 +0000 (GMT) (envelope-from tuliogs@pgt.mpt.gov.br) Received: from mail.pgt.mpt.gov.br (mail.pgt.mpt.gov.br [200.157.62.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09F4843D48 for ; Thu, 4 Aug 2005 15:27:57 +0000 (GMT) (envelope-from tuliogs@pgt.mpt.gov.br) Received: from [10.0.0.136] (516e.pgt.mpt.gov.br [10.0.0.136]) by mail.pgt.mpt.gov.br (8.13.1/8.13.1) with ESMTP id j74FRsAM015610 for ; Thu, 4 Aug 2005 12:27:54 -0300 (BRST) (envelope-from tuliogs@pgt.mpt.gov.br) Message-ID: <42F2346A.50300@pgt.mpt.gov.br> Date: Thu, 04 Aug 2005 12:29:46 -0300 From: =?ISO-8859-1?Q?Tulio_Guimar=E3es_da_Silva?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <20050801170723.GA90601@neptune.atopia.net> <20050804011439.GA66267@neptune.atopia.net> In-Reply-To: <20050804011439.GA66267@neptune.atopia.net> Content-Type: multipart/mixed; boundary="------------030204040703020404080901" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: hard drive noises -- western digital wd800ve X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2005 15:27:58 -0000 This is a multi-part message in MIME format. --------------030204040703020404080901 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi gentlemen, I donīt know if itīs related, but (I went to investigation) thereīs a known issue with WD HDs from 40 to 200GB prior to 2003/03/25 (March 25, 2003 - dates are always confusing :) ); even though itīs associated to RAID-controllers, it seems indeed that there is some kind of timeout generated by the acoustic reduction features of the drives. Hereīs the link to the explanation: http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=913 In short, there seems to be a bit to be disabled at run-time, *but* the utility is only available to Windows systems. ŽŽ It can be downloaded here: http://support.wdc.com/download/index.asp?cxml=n&pid=4&swid=11 Maybe itīs an issue that could be trated by the ata(4) driver or sysctl (if not already), but... *maybe*; thatīs really not for me to tell. :P Anyway, I guess people with this issue should contact WD or a reseller. Since itīs a somewhat limited issue, *and* itīs known to the manufacturer, I think they wouldnīt oppose to replace the affected drive(s). Cheers, Tulio G. da Silva Dan Ponte wrote: >On Wed, Aug 03, 2005 at 09:01:52PM -0400, Michael Roberts was witnessed plotting the following conspiracy: > > >>hi, >> >>thanks for all your responses. i've heard similar things, and am getting a >>replacement drive sent out from WD. however, a few interesting things: >> >>1) the frequency of the tic/toc noises (really they sound like "toc - tic" >>..) decreases when i disable acpi. i should have done this before, of >>course.... I haven't tried switching to apm. but w/o acpi, performance is >>pretty good, and i don't get the delays with tab-completion. >> >>2) i've run every hardware tester i could get my hands on, and none of them >>find any bad sectors/block/anything. the drive always checks out. >> >>this is all making me think that i've just got my system configured wrong. >>like maybe i need some special device in my kernel for this particular >>drive? or maybe i need to mess with acpi settings to get things >>streamlined? >> >>any suggestions along these lines? or should i just trash the thing... >> >>thx again. >> >> >> >Well, this drive is probably 4 or 5 years old by now, and I'm pretty >sure it's been clicking along since I got it. ACPI would make sense; >maybe the BIOS or something is trying to turn off the drive motor, but >the OS needs to use it, so it turns back on. This is rather farfetched, >though, as it happens usually during load. I have ACPI enabled, but >dmesg tells me that my BIOS is blacklisted, so I doubt it's really >enabled. >-Dan > > --------------030204040703020404080901--