From owner-freebsd-isp@FreeBSD.ORG Tue Oct 11 03:19:50 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5864916A41F for ; Tue, 11 Oct 2005 03:19:50 +0000 (GMT) (envelope-from rtsit@yahoo.com) Received: from web53008.mail.yahoo.com (web53008.mail.yahoo.com [206.190.49.38]) by mx1.FreeBSD.org (Postfix) with SMTP id 95E4343D45 for ; Tue, 11 Oct 2005 03:19:49 +0000 (GMT) (envelope-from rtsit@yahoo.com) Received: (qmail 76570 invoked by uid 60001); 11 Oct 2005 03:19:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=QXjXeSreyRSgFZO7nr6nLtgidF082Lzc4VtlS7qGFZ/EpJoku8e1Xs+HdTGd6GFjFuhPqNc+a7n7Fab0Y+ZqDH2hc9rL3XIwzyRnuh75kOuvFOBCQr8A2MzYdStffI9ADGLU38KLwE79qpFTbm8Oy0ToVJiGXS5JQ01MMUhBg94= ; Message-ID: <20051011031948.76568.qmail@web53008.mail.yahoo.com> Received: from [216.232.87.238] by web53008.mail.yahoo.com via HTTP; Mon, 10 Oct 2005 20:19:48 PDT Date: Mon, 10 Oct 2005 20:19:48 -0700 (PDT) From: rtsit To: freebsd-isp@freebsd.org In-Reply-To: <20051009120046.5CBEA16A420@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Problem with FreeBSD 4.9-Release resetting itself! X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2005 03:19:50 -0000 I've got a problem with FreeBSD 4.9-RELEASE resetting itself. This is a production system that has been running fine for over a year. It seems to be linked to a disk error of some sort. I often see log file entries like this: Sep 23 00:00:46 nfs2 /kernel: ad0: timeout sending command=c8 s=80 e=00 Sep 23 00:00:46 nfs2 /kernel: ad0: error executing command - resetting Sep 23 00:00:46 nfs2 /kernel: ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device Sep 23 00:00:46 nfs2 /kernel: don Sep 29 11:49:01 nfs2 /kernel: ad0: READ command timeout tag=0 serv=0 - resetting Sep 29 11:49:01 nfs2 /kernel: ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device Sep 29 11:49:01 nfs2 /kernel: done Oct 9 21:40:55 nfs2 /kernel: ad0: READ command timeout tag=0 serv=0 - resetting Oct 9 21:40:55 nfs2 /kernel: ata0: resetting devices .. ad0: DMA limited to UDMA33, non-ATA66 cable or device All I can figure is that the FreeBSD system is trying to read/write to ad0 (my primary HD) and there's an error of some sort, so it waits a bit and then resets the entire system. When I do an fsck, it comes out fine. So it's definately some sort of weird intermittent problem. Is my HD toast, or is FreeBSD acting stupid unnecessarily? __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com