|Subject:||Problem with FreeBSD 4.9-Release resetting itself!|
|Date:||Oct 10, 2005 8:46:05 pm|
Check the system board, RAM slots etc. Get all the dust and lint that may have built up and is holding heat. Does your motherboard BIOS provided you with any temp reading? I had this same issue with 4.8,. 4.9 and 4.11 but is was the hardware and not the OS that was causing the problem. A good cleaning once a year never hurts
The RAM, motherboard and IO controller for the IDE hard drive could be at fault. If you clean everything and do not have a over heat problem. I would try replacing the power supply, with at least a 350 Watt system that can keep that unit cool..
Can you get your important data e.g /usr /home backed up if the hard drive is going south on you?
*/Jeff Norris/* /~ Web Hosting ~ VPN Solutions ~ Network Management ~ Design, deploy, kick ass. / *N*orris*Techs* dot net http://www.norristechs.net *AOL IM or Yahoo IM: _ ntshelper _*
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
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-isp To unsubscribe, send any mail to "free...@freebsd.org"