From owner-freebsd-questions@FreeBSD.ORG Wed Mar 24 07:18:05 2004 Return-Path: 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 18A6E16A4CE for ; Wed, 24 Mar 2004 07:18:05 -0800 (PST) Received: from p1028-ipbffx02marunouchi.tokyo.ocn.ne.jp (p1028-ipbffx02marunouchi.tokyo.ocn.ne.jp [220.111.132.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id C694F43D2D for ; Wed, 24 Mar 2004 07:18:03 -0800 (PST) (envelope-from lukek@meibin.net) Received: (qmail 7390 invoked by uid 89); 24 Mar 2004 15:18:02 -0000 Received: from unknown (HELO ?192.168.10.8?) (192.168.10.8) by 192.168.20.5 with SMTP; 24 Mar 2004 15:18:02 -0000 Date: Thu, 25 Mar 2004 00:18:41 +0900 From: Luke Kearney To: FreeBSD Questions Message-Id: <20040325001226.9E37.LUKEK@meibin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.07.01 Subject: Hardware problems or Software problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Mar 2004 15:18:05 -0000 Hello, I have a server which recently died on me. I believed that the problem was likely the memory as the machine would reboot of its own accord initially when accessing via samba or NFS. Then I noticed that it would reboot when under no load. Given that the motherboard and CPU etc was pushing three years old it seemed like a good opportunity to upgrade to some newer kit I had. I installed a new ASUS P4800 motherboard with a celeron 2.20ghz chip and brandnew 512mb memory. Now again whilst under no load at all it will freeze. The only original parts are the HDD's. My difficulty is that nothing is left in the logs or on std out. If it is the disks I will reluctantly replace but I cannot see why disks would cause a reboot and leave nothing logged such as a time out or anything. Are there any specific commands I can issue during start up to increase the verbosity of logging to try to capture the root cause for this ? Any assistance is appreciated. LukeK -- Luke Kearney