From owner-freebsd-questions@FreeBSD.ORG Mon Jun 28 13:38:35 2004 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 229A016A4CF for ; Mon, 28 Jun 2004 13:38:35 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.245]) by mx1.FreeBSD.org (Postfix) with SMTP id E23CA43D39 for ; Mon, 28 Jun 2004 13:38:34 +0000 (GMT) (envelope-from thatha@gmail.com) Received: by mproxy.gmail.com with SMTP id u22so334487cwc for ; Mon, 28 Jun 2004 06:38:31 -0700 (PDT) Received: by 10.38.88.78 with SMTP id l78mr76885rnb; Mon, 28 Jun 2004 06:38:31 -0700 (PDT) Message-ID: Date: Mon, 28 Jun 2004 23:38:31 +1000 From: Gautam Gopalakrishnan To: Dancho Penev , FreeBSD Questions In-Reply-To: <20040628115742.GA677@earth.dpsca.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040626171145.GB900@freebsd.vmware.dpsca.bg> <20040628115742.GA677@earth.dpsca.bg> Subject: Re: Unable to boot FreeBSD (dual-boot) 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: Mon, 28 Jun 2004 13:38:35 -0000 On Mon, 28 Jun 2004 14:57:42 +0300, Dancho Penev wrote: > >> On Sun, Jun 27, 2004 at 12:25:24AM +1000, Gautam Gopalakrishnan wrote: > >> For label use /boot/boot file, /boot/boot0 is for mbr. > >> > >> > > >> >/hd is the temporary directory I created to mount /dev/ad0s2a, > >> >so I guess my slice is still ok. > > > >Does not help! I even tried "disklabel -B /dev/ad0s2" because a > >diff between /hd/boot/boot and /boot/boot on the fixit yielded > >nothing. > > > ># disklabel /dev/ad0s2 > >lists the various partitions properly. > > > >I do have an MBR because I get a boot menu. Just can't get the > >MBR to talk to boot1 and boot2... > > If you can remember what were you did to broke configuration it will be > very helpful. At this point I can't say anything else. Sorry. I think I did "boot0cfg -B /dev/ad0s2" or maybe ad0 instead. Wish I could remember what I did exactly. Don't even remember why I did it. Was that helpful? :-) Gautam