From owner-freebsd-questions Mon Jan 25 15:06:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28074 for freebsd-questions-outgoing; Mon, 25 Jan 1999 15:06:02 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from chopin.seattleu.edu (chopin.seattleu.edu [206.81.198.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28065 for ; Mon, 25 Jan 1999 15:06:00 -0800 (PST) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu ([172.17.41.90]) by chopin.seattleu.edu (8.8.5/8.8.5) with ESMTP id PAA29334; Mon, 25 Jan 1999 15:05:21 -0800 (PST) Message-ID: <36ACF8B0.A341635B@seattleu.edu> Date: Mon, 25 Jan 1999 15:05:20 -0800 From: Eric Hodel X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Laurence Berland CC: questions@FreeBSD.ORG Subject: Re: Uh oh References: <36ACC4EA.A4E7D078@confusion.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Laurence Berland wrote: > > I installed FBSD, sort of. I posted this before, now I'm getting > desperate for help. If anyone knows what to do please help!!!! > > we've installed freebsd. We rebooted the system and the boot manager > appeared, prompting us to > F1 for ??? (which turned out is what it meant as win98) > F2 for FreeBSD > > We hit f2, and the manager just repeats its window. It does this > always, and as of yet we've not been able to get to a BSD prompt at all, > or to get it to even begin booting fbsd. We've tried using the > installation software to rewrite the boot manager, but it doesn't change > anything. I'm completely stumped. Do we need to reinstall FreeBSD? > Could it be that the error was because we made a second dos partition > with the boot manager also? We deleted the second dos partition to try > and fix the problem, but nothing changes. What do I do now? I've had this problem a few times, and it is a bit tricky to circumvent with the default boot manager. The easiest way to fix it is to install os-bs beta (beta supports multi-disk booting) and set up the mbr that way. Using the default boot manager you need to be absolutely cetain that you've set both drives bootable and installed the boot manager on both (what you described seems to show that the 2nd drive doesn't have it.) -- Eric Hodel hodeleri@seattleu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message