From owner-freebsd-questions@FreeBSD.ORG Thu Sep 4 14:58:42 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 61CF116A4BF for ; Thu, 4 Sep 2003 14:58:42 -0700 (PDT) Received: from fep3.cogeco.net (smtp.cogeco.net [216.221.81.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 489D543FA3 for ; Thu, 4 Sep 2003 14:58:39 -0700 (PDT) (envelope-from pnmurphy@cogeco.ca) Received: from earth.upton.net (d141-18-230.home.cgocable.net [24.141.18.230]) by fep3.cogeco.net (Postfix) with SMTP id 9E4D43A5B; Thu, 4 Sep 2003 17:58:38 -0400 (EDT) Date: Thu, 4 Sep 2003 17:58:38 -0400 From: Paul Murphy To: Paul Murphy Message-Id: <20030904175838.5e7d4e94.pnmurphy@cogeco.ca> In-Reply-To: <20030904173804.6000c9cb.pnmurphy@cogeco.ca> References: <20030903181348.5cbfcabb.pnmurphy@cogeco.ca> <200309031800.30413.dkelly@HiWAAY.net> <20030904121125.GC88888@happy-idiot-talk.infracaninophile.co.uk> <20030904173804.6000c9cb.pnmurphy@cogeco.ca> X-Mailer: Sylpheed version 0.9.3claws (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="=.KoG9SAGko0khqI" cc: FreeBSD-Questions@freebsd.org Subject: Re: Undo MBR X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2003 21:58:42 -0000 --=.KoG9SAGko0khqI Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Thu, 4 Sep 2003 17:38:04 -0400 Paul Murphy wrote: > On Thu, 4 Sep 2003 13:11:25 +0100 > Matthew Seaman wrote: > > > On Wed, Sep 03, 2003 at 06:00:30PM -0500, David Kelly wrote: > > > On Wednesday 03 September 2003 05:13 pm, Paul Murphy wrote: > > > > I have just installed FBSD-CURRENT on a test box. During > > > > install I > > > > unwittingly installed a BootMgr entry for the second HDD (it > > > > will just be a data disk, no need to boot from it). > > > > > > > > If I do 'dd if=/dev/zero of=/dev/rad2 count=15' will this > > > > "erase" > > > > the BootMgr or will I have to redo Fdisk and etcetera. There is > > > > no data on the disk yet so this would be no hardship, but is > > > > there a"proper" way of doing what I want? > > > > > > > > > > > > Just to clarify, upon booting I get: > > > > > > > > F1 FreeBSD > > > > F5 Drive 1 > > > > > > > > but I just want to boot straight into FreeBSD, no "dual-boot". > > > > > > I don't know why you are fretting about this prompt and > > > momentarily pause in the boot process. Also think you are confused > > > about the MBR thing on the 2nd drive. > > > > > > The prompt above is coming from your first HD. If the BIOS did not > > > know about the 2nd drive the F5 entry would not be there and the > > > FreeBSD F1 entry would still be there. You could hide this prompt > > > by retuning the MBR to pause 0 or 1 seconds. Zero might be > > > infinite. > > > > > > To eliminate the prompt, wipe the HD and reinstall "dangerously > > > dedicated." The result will be a disk which lacks the headers > > > which allows other x86 OS's to understand what/how the disk is > > > used. > > > > Errr... That's a little excessive. The quick way to remove the > > FreeBSd boot manager and restore a standard MBR is: > > > > # boot0cfg -B -b /boot/mbr ad0 > > > > (The OP might want to do that on his data disk ad2 as well). No > > changes to the filesystems on those disks should be necessary. > > > > THAT'S what I was looking for! I knew it should have something to do > with boot0cfg, just didn't read the man page closely enough I guess. > Hmm, problems... # boot0cfg -B -b /boot/mbr ad0 # boot0cfg: /boot/mbr: unknown or incompatible boot code Now, a little bit of history: This is a new install if FBSD-CURRENT from binaries, after which I realized I shouldn't have installed BootMgr. Then I tried to 'undo' it but having no success I did the email thing. _Meanwhile_ I did a CVS upgrade to FBSD-HEAD (for unrelated problems). I shouldn't think this would cause the boot0cfg error though. The /boot/mbr file is pretty stable code isn't it? -- Cogeco ergo sum --=.KoG9SAGko0khqI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/V7WOTv5Mxsi/WPMRAhsrAJ9iz2e+3XFFGu3NKg3jCdrezspw9QCgqjyc jbjXl7QHh8CEcTTF6HtdENI= =eqdK -----END PGP SIGNATURE----- --=.KoG9SAGko0khqI--