From owner-freebsd-current Tue Jan 5 06:25:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19820 for freebsd-current-outgoing; Tue, 5 Jan 1999 06:25:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19815 for ; Tue, 5 Jan 1999 06:25:47 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id IAA01562 for ; Tue, 5 Jan 1999 08:24:40 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id IAA01558 for ; Tue, 5 Jan 1999 08:24:39 -0600 (CST) Message-ID: <001201be38b7$38917520$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Bootblock and Disklabel problem!!! READ THIS!!! Date: Tue, 5 Jan 1999 08:25:18 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did a CVSUP on 12/29/98 and rebuilt world. Everything works great. Yesterday, I followed some instructions to put the new bootblocks and an ELF kernel on my system and things went bad. I have two IDE drives with Windows98 (8 Gigs) on my first drive and my second drive has two slices, the first is FreeBSD (4 Gigs) and the second is a DOS staging partition (2 Gigs). Here is what I did. I put the following in my /boot/boot.conf(ig) file: set currdev = disk2s1a load /kernel boot I then compiled and installed a new ELF kernel. That worked fine. I then ran disklabel: disklabel -B -b /boot/boot1 -s /boot/boot2 wd2 (according to http://www.freebsd.org/~rnordier/boot.txt) I rebooted. I was not happy to see the boot loader on my primary drive, but it was now there. When I tried to boot FreeBSD, it found the kernel and booted it, but the Kernel tried to mount the root partion on the first drive, which is wrong. Why is that? Worse, I found that I now had a FreeBSD partition and a DOS partition on my first drive also (obviously it had the old Windows98 information in it and not a true filesystem). It appears to me that the partition information from my second disk was copied to my first disk. Worse yet, my Windows 98 system became totally unbootable, even after I reset the partition information (using Linux bootdisks). My system was hosed (except for FreeBSD thank God!!!). Today I will have to rebuild my Windows 98 system again. Was all of this a known problem and fixed in recent days (since 12/29) or have I stumbled on something unique here? Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message