From owner-freebsd-hackers Wed Dec 6 18: 7:22 2000 From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 18:07:20 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id EEAC837B400 for ; Wed, 6 Dec 2000 18:07:18 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id eB727C506188; Wed, 6 Dec 2000 21:07:13 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200012070207.eB727C506188@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Nathan Boeger Cc: "freebsd-hackers@FreeBSD.ORG" X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: 4.2-RELEASE will not boot after install ? References: <3A2ECD7A.1E6A1FF3@khmere.com> In-reply-to: Your message of "Wed, 06 Dec 2000 15:36:26 PST." <3A2ECD7A.1E6A1FF3@khmere.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 21:07:12 -0500 Sender: louie@TransSys.COM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problem on an old PPro box. The BIOS seemingly doesn't like the new (2 sector long) boot manager. If you fire up sysinstall again, and tell it to install the "standard bootblocks" (forgot the exact phrase), rather than the boot manager, you'll probably be OK. louie > Don't know if I should post here but.... > > I just installed 4.2-RELEASE onto a ppro 200 (had linux) the install > went without a hich. Then when I rebooted, the box just stopped. It > seemed like it could not read the mbr. So I booted again off the > floppies and I used the loader to switched the currdev to the harddrive > (disk1s1a) it found the hardrive. I then loaded the kernel from the > harddrive and booted off the harddrive. After I was up on the box I then > ran disklabel -B ad0 and thought that maybe the installation did not add > the boot reccord info. Rebooted agian to have the same problem as > before. I then tried it agian with the flags for the boot code, no > luck. Finally I dd out the first 512 blocks of the harddrive and ran > strings on it. Seems that thier was nothing their ! so I was lucky > enough to have another 4.2 box and I just copied its first 512 blocks. > Now it boots fine ! > > Is their a known issue with this ? or maybe I did something wrong ? > > thank you > > nathan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message