From owner-freebsd-questions@FreeBSD.ORG Mon Nov 13 16:05:23 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE7F216A521 for ; Mon, 13 Nov 2006 16:05:23 +0000 (UTC) (envelope-from michael.knoll@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9172543F07 for ; Mon, 13 Nov 2006 15:57:51 +0000 (GMT) (envelope-from michael.knoll@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so966262uge for ; Mon, 13 Nov 2006 07:57:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=IpLV5XwycHQktqGh4du9M1pKe6uAahpxAZ1Wp/F/1bWjdL2CZaD5sADo6BH3GxNgKPGoHV/YkH+zR7QuzZEWFZwyCwNGEqSEV2zcYRbB7j9qVvMGvfUY6hzS9uzIPLbJBjNcuxjjVN9JqIDwoxsLdJ4ffDdO7QyaxSHXFHiXqOM= Received: by 10.78.201.10 with SMTP id y10mr6427617huf.1163433451075; Mon, 13 Nov 2006 07:57:31 -0800 (PST) Received: by 10.78.97.11 with HTTP; Mon, 13 Nov 2006 07:57:31 -0800 (PST) Message-ID: <975053160611130757m355d7c2emc366dd8c8c4cf21@mail.gmail.com> Date: Mon, 13 Nov 2006 10:57:31 -0500 From: "Michael Knoll" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: ATA drive TIMEOUT READ_DMA errors since adding power savings X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 16:05:24 -0000 I added a power down timer on one of my harddrives, and started getting READ_DMA and WRITE_DMA timeouts. Is it possible these are occuring becuase the drive is spun down and FreeBSD isn't waiting long enough for it to spin up? Everything else seems to be working. If that is the problem, is it possible to extend the timeout to eliminate these messages clouding my logs? Thanks, Mike +ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=41399007 +ad4: TIMEOUT - READ_DMA retrying (1 retry left) LBA=12095