Date: Sat, 13 Mar 1999 03:04:59 +0200 (SAT) From: Robert Nordier <rnordier@nordier.com> To: julian@whistle.com (Julian Elischer) Cc: jkh@zippy.cdrom.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19990311-SNAP bootblock install weirdness Message-ID: <199903130105.DAA00868@ceia.nordier.com> In-Reply-To: <Pine.BSF.3.95.990312093922.3660A-100000@current1.whistle.com> from Julian Elischer at "Mar 12, 99 09:44:27 am"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903130105.DAA00868>