From owner-freebsd-questions@FreeBSD.ORG Mon Oct 30 18:11:18 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 6C4E416A40F for ; Mon, 30 Oct 2006 18:11:18 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1452643DA9 for ; Mon, 30 Oct 2006 18:10:53 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.2] (pool-71-109-167-24.lsanca.dsl-w.verizon.net [71.109.167.24]) (authenticated bits=0) by zoot.lafn.org (8.13.6/8.13.4) with ESMTP id k9UIAqDQ087760 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 30 Oct 2006 10:10:53 -0800 (PST) (envelope-from bc979@lafn.org) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <74DA442C-3653-4D5A-938C-B4A7B69977BA@lafn.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-questions From: Doug Hardie Date: Mon, 30 Oct 2006 10:10:51 -0800 X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: ClamAV 0.88/2131/Sun Oct 29 14:00:12 2006 on zoot.lafn.org X-Virus-Status: Clean Subject: Hardware Problem 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, 30 Oct 2006 18:11:18 -0000 I have a hardware problem with a disk drive. Last night I received millions of messages like: Oct 29 23:00:02 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:02 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=39908835328, lengt h=8192)]error = 5 Oct 29 23:00:02 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:02 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=39908835328, lengt h=8192)]error = 5 Oct 29 23:00:16 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:16 zook last message repeated 3 times Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=1433600, length=81 92)]error = 5 Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=1441792, length=81 92)]error = 5 Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE (offset=1449984, length=51 20)]error = 5 Oct 29 23:00:16 zook kernel: g_vfs_done():ad0s1e[WRITE(offset=8192, length=2048) ]error = 5 Oct 29 23:00:28 zook kernel: ad0: timeout waiting for write DRQ Oct 29 23:00:28 zook last message repeated 8 times They were going to messages and the console as fast as the system could log them. ad0 is not the boot disk but is used to hold large files. I have seen somewhat similar problems once before and replaced the drive. That was about a year ago. This time I am suspecting the IDE controller. Is this reasonable, or is it still likely a drive failure? Rebooting the system appears to have temporarily terminated the problem as I am no longer receiving the messages and nothing appears to have been lost on ad0. However, the bulk of data on it are the news archive and other archive files that were replaced shortly after the reboot. smartctl shows passed on the drive, but I believe I am reading that 6 sectors have been remapped.