From owner-freebsd-questions@FreeBSD.ORG Sat Nov 1 07:27:09 2003 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 BA58616A4CE for ; Sat, 1 Nov 2003 07:27:09 -0800 (PST) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF6F543FAF for ; Sat, 1 Nov 2003 07:27:06 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 4E3653AB7; Sat, 1 Nov 2003 10:27:06 -0500 (EST) Sender: lowell@be-well.ilk.org To: Bob Collins References: <5.2.0.9.0.20031030152350.00a9e260@anything-inc.com> From: Lowell Gilbert Date: 01 Nov 2003 10:27:06 -0500 In-Reply-To: <5.2.0.9.0.20031030152350.00a9e260@anything-inc.com> Message-ID: <4465i4p0s5.fsf@be-well.ilk.org> Lines: 24 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: FreeBSD Subject: Re: cannot boot, at mountroot> prompt X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2003 15:27:09 -0000 Bob Collins writes: > I have a system running 5.0-RELEASE on an AMD 667Mhz processor with > 256MB ram, Soyo mobo. Install was no trouble, and setup of X, KDE, > MySQL, Apache went fine. I ran a setup of both xmms and mplayer as > well. Then I went for an install of Webmin. > > Once webmin was complete, I was running in KDE, I closed the term > window and the machine rebooted immediately, no shutdown, nothing. > > Question, does this sound like a bad drive, RAM, or perhaps my bad luck. > Second question, how can I address the mountroot> prompt? > > Per the instructions at the prompt, I put in ufs:/dev/ad0s1a and hit > the return key. The system then reboots. To start with, you should definitely update your system to something more recent. 5.0 was, after all, a very early "technology preview" release from a branch that, after nearly a year, still isn't ready to produce a production release. Unless you have some (at least minimal) skills at tracking down these kinds of problems, you should probably move to the latest release, 4.9. That said, there will probably be some hints in a kernel dump.