From owner-freebsd-questions@FreeBSD.ORG Fri May 28 10:01:12 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 84E7716A4CE for ; Fri, 28 May 2004 10:01:12 -0700 (PDT) Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F28843D1F for ; Fri, 28 May 2004 10:01:12 -0700 (PDT) (envelope-from nullentropy@lineone.net) Received: from [192.168.0.2] (orbital.gotadsl.co.uk [81.6.215.230]) by smtp.nildram.co.uk (Postfix) with ESMTP id ECB6E25F5B4 for ; Fri, 28 May 2004 18:00:12 +0100 (BST) Message-ID: <40B77019.9020108@lineone.net> Date: Fri, 28 May 2004 18:00:09 +0100 From: Robert Downes User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040526 X-Accept-Language: en, fr, en-us MIME-Version: 1.0 To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: buildworld actually crashed 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: Fri, 28 May 2004 17:01:12 -0000 During buildworld, I wandered off. When I returned, my machine was, alarmingly, in single user mode, demanding that I run fsck manually. I'm running fsck right now, and it's finding all sorts of block size errors, to which I'm simply hitting 'y' and agreeing that things should be salvaged and corrected. Before running fsck, I had a look at the buildworld.out script that was being written to during the buildworld process. I can't tell you exactly what it says, but it definitely came to a stop in the middle of a 'sentence' of output. I.e. it looks like my new machine (yeah, the soon-to-be-fanless EPIA again) must have crashed during buildworld. What could cause buildworld to crash like that? I'm now worried that my PSU board *was* damaged the other day. Is a damaged PSU the most likely cause of this incident? All advice very welcome. -- Bob London, UK echo Mail fefsensmrrjyaheeoceoq\! | tr "jefroq\!" "@obe.uk"