Date: Mon, 10 Oct 2005 20:19:48 -0700 (PDT) From: rtsit <rtsit@yahoo.com> To: freebsd-isp@freebsd.org Subject: Problem with FreeBSD 4.9-Release resetting itself! Message-ID: <20051011031948.76568.qmail@web53008.mail.yahoo.com> In-Reply-To: <20051009120046.5CBEA16A420@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051011031948.76568.qmail>