Date: Thu, 13 Oct 2005 00:33:50 +0300 From: "Vahric MUHTARYAN" <vahric@doruk.net.tr> To: "'rtsit'" <rtsit@yahoo.com>, <freebsd-isp@freebsd.org> Subject: RE: Problem with FreeBSD 4.9-Release resetting itself! Message-ID: <auto-000418738387@doruk.net.tr> In-Reply-To: <20051011031948.76568.qmail@web53008.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi , I think you have to change your hdd cable like How Stand said before, if you are suspect from OS or from hardware it will be better to diag the disk like seatools which checking seagates disk for problems or if your disk have SMART capability then open support from board if disabled and watch SMART messages or errors . Bye Vahric -----Original Message----- From: owner-freebsd-isp@freebsd.org [mailto:owner-freebsd-isp@freebsd.org] On Behalf Of rtsit Sent: Tuesday, October 11, 2005 6:20 AM To: freebsd-isp@freebsd.org Subject: Problem with FreeBSD 4.9-Release resetting itself! 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 _______________________________________________ freebsd-isp@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-isp To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?auto-000418738387>