From owner-freebsd-questions Fri Jun 9 11: 5:33 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cornflake.nickelkid.com (cornflake.nickelkid.com [216.116.135.26]) by hub.freebsd.org (Postfix) with ESMTP id 9DBE437BBC1 for ; Fri, 9 Jun 2000 11:05:29 -0700 (PDT) (envelope-from jooji@cornflake.nickelkid.com) Received: from localhost (jooji@localhost) by cornflake.nickelkid.com (8.9.3/8.9.3) with ESMTP id OAA33517; Fri, 9 Jun 2000 14:05:26 -0400 (EDT) (envelope-from jooji@cornflake.nickelkid.com) Date: Fri, 9 Jun 2000 14:05:26 -0400 (EDT) From: "Jasper O'Malley" To: freebsd-questions@freebsd.org Cc: Mark Ovens Subject: REVISED: Active partition problems with FreeBSD 4.0/NT dual-boot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG REVISION NOTE: I left a portion of my story out initially, because I figured it was irrelevant. It probably wasn't :) Here's the revised account of what blew up: I've got NT 4.0 installed on a the first partition (NTFS) on da0, and FreeBSD 4.0 installed on the first partition of da1. When I installed FreeBSD, I instructed it to install a bootloader on da1, but not da0, with the intention of allowing NTLDR handle the OS selection. After installation, I FTPed /boot/boot0 to another box (since I don't have any FAT partitions on my machine) and rebooted. I got the NTLDR screen, booted into NT, FTPed boot0 back to the NTFS partition, renamed it bootsect.bsd, and added the following line to C:\boot.ini: C:\BOOTSECT.BSD="FreeBSD 4.0" When I rebooted, I selected "FreeBSD 4.0" from the list, and got the FreeBSD loader with a single option: F5 Drive 1 I hit F5, and got a second loader menu: F1 FreeBSD F5 Drive 0 I hit F1 to boot into FreeBSD, and I thought all was well. However, when I rebooted to get back into NT, I was presented with the following error message: Not found any [active partition] in HDD I rebooted from a Win98 floppy, and ran a utility called MBRWORKS to reset the active flag on the NTFS partition (da0s1). I then rebooted, but I got the same error message. I rebooted with the Win98 floppy again, and ran FDISK. It showed that the da0s1 partition had vanished entirely. While I initially assumed that MBRWORKS utility had somehow wiped out my partition table, I'm not so sure anymore. It may have been (based on Mark Ovens' reply to my earlier post) that boot0 had written itself into the MBR of da0, and had overwritten the partition table on da0 with a blank table in the process. I reinstalled Windows NT from scratch, and this set the da0s1 partition active again. When I rebooted during the NT install process, I was presented with the following loader menu: F1 ?? F5 Drive 1 I thought this was weird, since I never explicitly installed the FreeBSD loader onto da0. Pressing F1 brought me to the NTLDR screen, as I expected, and I was able to boot into NT again (to finish the install process). When I rebooted, I got the same loader menu again, and this time I hit F5, then F1 to boot into FreeBSD. Upon a reboot, bam, back to: Not found any [active partition] in HDD I booted from a Win98 startup floppy, used Win98 fdisk to set the NTFS partition (da0s1) partition active again, and I got the following boot menu again: F1 ?? F5 Drive 1 This allowed me to boot back into NT (without a reinstall, this time ;), but every time I boot into FreeBSD, I need to use fdisk to set da0s1 active again. After doing some reading, I'm guessing the problem is that I've a brain-dead Award BIOS variant on my GA-686LX4 motherboard that assumes you're using an M$ OS and checks for active partitions on the lowest numbered BIOS disk present (da0, in this case) before it hands control over to any MBR bootloader. If there aren't any active partitions, the BIOS craps out with the above error. Now, for the questions: 1) How did the FreeBSD loader find its way onto the MBR of da0? It obviously wasn't there before I selected "FreeBSD 4.0" from the NTLDR menu the first time, but it seems that it's been there ever since. Is this by design? And, now, did it overwrite the partition table on da0 in the process? 2) Is there any way to keep whatever is clearing the "active" flag on the first partition of da0 from doing so? I tried upgrading the BIOS for the motherboard to the latest version, but the active partition checking "feature" is still present. Thanks, Mick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message