From owner-freebsd-stable@FreeBSD.ORG Fri Dec 26 17:34:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E49CA1065675 for ; Fri, 26 Dec 2008 17:34:39 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-28-76-39.eur.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3C14D8FC1B; Fri, 26 Dec 2008 17:34:39 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <495515AE.4050606@FreeBSD.org> Date: Fri, 26 Dec 2008 17:34:38 +0000 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: Glen Barber References: <4ad871310812260918h538d82c7s2f72f254bf08c26c@mail.gmail.com> In-Reply-To: <4ad871310812260918h538d82c7s2f72f254bf08c26c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable Subject: Re: Kernel Trap during installworld caused unrecoverable system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Dec 2008 17:34:40 -0000 Glen Barber wrote: > Hi folks. > > I was unfortunate enough to encounter a kernel trap in single user > mode yesterday when upgrading from 7.1-RC1 to -RC2 using the typical > build/install world. > > I'm still not sure what caused the trap, as the system was rebooting > when I saw the screen. As one would expect, this led to an > irrecoverable system; the system would automatically drop me into > single user mode, as it could only mount the root directory; /bin/sh > and /bin/csh would not work (had to use /restore/csh for the minimal > digging I actually could do). > > So, now to the question. Given I could not mount anything other than > /, would there have been any way for me to gather debugging > information on what caused this failure? (FWIW, I am certain it is > not a hardware failure.) You can proceed recovering the system using the tools in /rescue, and once you have shared libraries working again, run savecore to save the crashdump (assuming one was made). Kris