From owner-freebsd-stable@FreeBSD.ORG Fri Oct 17 06:49:31 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 607D616A4B3 for ; Fri, 17 Oct 2003 06:49:31 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D78043FB1 for ; Fri, 17 Oct 2003 06:49:30 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id ACB493D28; Fri, 17 Oct 2003 09:48:44 -0400 (EDT) From: "Dan Langille" To: freebsd-stable@freebsd.org Date: Fri, 17 Oct 2003 09:52:07 -0400 MIME-Version: 1.0 Message-ID: <3F8FBBC7.10222.304EFA2@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: Dan Langille Subject: erorrs from spec_getpages X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Oct 2003 13:49:31 -0000 Hi, Last night I did a buildworld. This morning I found this: $ cd -bash: cd: /home/dan: Device not configured looking at /, it was empty. $ ls /home/ ls: /home/: Device not configured Looking at the console, I found this: http://beta.freebsddiary.org/tmp/mtwenty-console.jpg I rebooted. The system couldn't find the disk. I replaced the IDE drive. Still no disk. Checked the BIOS. The disk wasn't listed so I added it. I also deactivated the floppy because it had been removed yesterday. A reboot was fine. fsck went OK. All seems well now. I'm doing another buildworld, building some ports, and running cvsup on my ports tree to create disk activity. When that finishes, I'm going to run the manufacturer's test program on the drive to see if any problems are found. Was this a hardware failure? System failure? Any recommended courses of action? -- Dan Langille : http://www.langille.org/