From owner-freebsd-current Fri Mar 12 9:48:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D8E1114CAC for ; Fri, 12 Mar 1999 09:48:52 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA06088; Fri, 12 Mar 1999 09:44:34 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdMF6081; Fri Mar 12 17:44:30 1999 Date: Fri, 12 Mar 1999 09:44:27 -0800 (PST) From: Julian Elischer To: "Jordan K. Hubbard" Cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19990311-SNAP bootblock install weirdness In-Reply-To: <6747.921230684@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problem.. I had to reinstal the old booteazy off a backup before my system would boot again. I have booteasy on dsk0, and used fdisk -b on dsk1 after installing hte new bootblocks (3stage). It stopped booting and nothing I could do woul dmake it boot till I manufactured a new booteasy block by concattinating the booteasy code from dsk0 and the MBR table from dsk1 (by hand). root is on da1sd1a and it all worked fine (and now again) with the old booteasy code on both disks. ( replace the booteasy code on da1 because there si no choice there and wanted silent bootblock.. julian On Fri, 12 Mar 1999, Jordan K. Hubbard wrote: > > to wipe out the front-end of the boot disk. I then re-installed > > the 4.0 system a 3rd time and it now boots normally. I am unable to > > explain why this happened, but hope that someone with more experience > > with the sysinstall/boot code can shed some light on it. > > No, that's just pretty weird. :-) I wonder if the geometry was > calculated differently in the two cases, did you manage to compare > numbers in the fdisk screen in the before-and-after case? Now that > you've zero'd it, it makes analysis of the original condition a little > more difficult. :) > > > lrwxrwxrwx 1 2035 207 19 Feb 12 04:09 compat22 -> ../current/compat22 > > Yep, if you're mirroring these bits, you need to fetch "through" that > link and populate compat22. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message