From owner-freebsd-stable@FreeBSD.ORG Fri May 14 03:32:33 2010 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 A52C11065673 for ; Fri, 14 May 2010 03:32:33 +0000 (UTC) (envelope-from fred@storming.org) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3F4FF8FC0A for ; Fri, 14 May 2010 03:32:33 +0000 (UTC) Received: by fxm17 with SMTP id 17so1128585fxm.13 for ; Thu, 13 May 2010 20:32:32 -0700 (PDT) Received: by 10.239.189.139 with SMTP id t11mr88106hbh.17.1273807952132; Thu, 13 May 2010 20:32:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.148.78 with HTTP; Thu, 13 May 2010 20:32:12 -0700 (PDT) In-Reply-To: <20100514032540.GA85214@icarus.home.lan> References: <20100514030630.GA84755@icarus.home.lan> <20100514032540.GA85214@icarus.home.lan> From: Fred Souza Date: Fri, 14 May 2010 00:32:12 -0300 Message-ID: To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: Mount root error / New device numbering? 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, 14 May 2010 03:32:33 -0000 On Fri, May 14, 2010 at 00:25, Jeremy Chadwick w= rote: > Absolutely. =A0I've done it myself many times over the years, including > remotely over serial console. =A0However, you said you did that then type= d > "exit" rather than "reboot", and the end result was a kernel panic. Yes, I should have given it another clean try after changing /etc/fstab. I guess my rustiness with the Good Stuff(tm) plus the unexpected behavior made me panic myself. > Honestly, I'm not surprised; the system was probably still confused > about the root device. =A0I'm guessing some kernel innards (or maybe > something picked up from boot2/loader) still referenced the "unknown > root device" and caused the panic. Could be. The system had just too many possible points of failure at that point (its original kernel refused to boot for a few hours due to the geometry mess, then all of a sudden started working normally, for instance), so I take whatever I learned from that install as experience. I'm glad I thought about the right thing to do, it may have failed for a number of things in the way. > Even on other operating systems, if I'm dropped (unintentionally or > intentionally/by choice) into single-user mode, I reboot the system > rather than exit out of single-user and hope that multi-user works from > that point forward. =A0I've seen "exit" on Solaris fail and cause all > sorts of mayhem (all sorts of system startup services (not rc/init!) > failing, machine ending up in some sort of catatonic state). Good to know, I never really paid much attention to those details (I will from now on). Thank you a lot for the help, Jeremy. I will try your suggestions in the morning and post back to tell what did I find out. Best regards, Fred