From owner-freebsd-questions Mon Oct 9 21:41:15 2000 Delivered-To: freebsd-questions@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 0E6BF37B66D for ; Mon, 9 Oct 2000 21:41:12 -0700 (PDT) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.3/8.9.3) id VAA01212 for ; Mon, 9 Oct 2000 21:41:33 -0700 (MST) Received: from radsl-busy.tus.primenet.com(207.138.88.126), claiming to be "crazyhorse" via SMTP by smtp05.primenet.com, id smtpdAAAVWaGpc; Mon Oct 9 21:41:22 2000 Message-Id: <3.0.5.32.20001009214056.0098e660@pop.primenet.com> X-Sender: paschal@pop.primenet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 09 Oct 2000 21:40:56 To: questions@freebsd.org From: Richard Paschal Subject: install creates invalid partition table Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This is an FYI intended for those maintaining the installation disk slicing/partitioning code. I tried to install FreeBSD 4.0 from the powerpak CD today. The 9GB SCSI UW target disk is one which previously contained four (4) slices. The first is MSDOS 125MB (OS code 06). Effectively, the second and third were deleted to form a non-partitioned space and the fourth is a Windows NTFS 4048MB data partition/slice (code 07). 3 stable used to be the last slice. I needed more space and wanted to create two new slices inside the non-partitioned space for FreeBSD, 2500MB for system and 2000MB for data. There is another disk present, part of which is used for swap and /usr/obj. The installation program found the two existing slices, da0s1 and da0s2, and I created two new slices that it called da0s3 and da0s4. A red flag went up, they were out of order. It should have created da0s2 and da0s3. At no time did I mark either of these partitions active. It should have created da0s2 then da0s3, each time moving the NTFS slice so that all starting sectors would be ordered lowest to highest as their sector addresses increase. I let the installation continue to see what would happen. Everything else went well except for the 6x13 X font that didn't get copied. Upon rebooting, the MBR-partition table was bad. It indeed had the two A5 entries last. They were both marked active (80)! The MSDOS entry was marked inactive (00). I saved the sector just in case someone asks for it. I restarted the BSD installation, removed the A5 slices, exited, rebooted MSDOS from an emergency diskette, checked the table, and ran FDISK.EXE, marking the MSDOS slice active. After a little more work and two reboots, the system was restored to its prior state. As a work-around, I created the two slices using the NT Disk Administrator and marked them A5 with Diskprobe. If you must reply, do so by e-mail, I'm not subscribed to questions. Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message