Date: Mon, 28 Jun 2004 23:38:31 +1000 From: Gautam Gopalakrishnan <thatha@gmail.com> To: Dancho Penev <dpenev@mnet.bg>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Unable to boot FreeBSD (dual-boot) Message-ID: <a3ada2d104062806383f6b78b0@mail.gmail.com> In-Reply-To: <20040628115742.GA677@earth.dpsca.bg> References: <a3ada2d104062607257df9e34e@mail.gmail.com> <20040626171145.GB900@freebsd.vmware.dpsca.bg> <a3ada2d104062621073c064d8d@mail.gmail.com> <20040628115742.GA677@earth.dpsca.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 Jun 2004 14:57:42 +0300, Dancho Penev <dpenev@mnet.bg> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a3ada2d104062806383f6b78b0>