From owner-freebsd-current Fri Mar 12 17: 7:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m1-30-dbn.dial-up.net [196.34.155.30]) by hub.freebsd.org (Postfix) with ESMTP id 3E3DE15413 for ; Fri, 12 Mar 1999 17:07:27 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id DAA00868; Sat, 13 Mar 1999 03:05:01 +0200 (SAT) From: Robert Nordier Message-Id: <199903130105.DAA00868@ceia.nordier.com> Subject: Re: 4.0-19990311-SNAP bootblock install weirdness In-Reply-To: from Julian Elischer at "Mar 12, 99 09:44:27 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 13 Mar 1999 03:04:59 +0200 (SAT) Cc: jkh@zippy.cdrom.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > 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.. If anyone else runs into the same problem, it would probably be a help if they could save the output from the following script before proceeding: #!/bin/sh DRIVE=da0 SLICE=s1 fdisk ${DRIVE} disklabel ${DRIVE} dd if=/dev/r${DRIVE} count=1 dd if=/dev/r${DRIVE}${SLICE} count=17 However, the problem in Julian's case is most likely that fdisk -b writes a completely standard MBR which effectively assumes that the drive being booted from is BIOS drive 0x80 (drive 0). You have to have a boot manager (or some kind of non-standard MBR) on higher-numbered drives in order to boot from them. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message