Date: Tue, 21 Jul 1998 08:30:02 -0700 (PDT) From: Stefan Eggers <seggers@semyam.dinoco.de> To: freebsd-bugs@FreeBSD.ORG Subject: Re: misc/7190: "Invalid partition table" after new install with multiple BSD slices Message-ID: <199807211530.IAA08046@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/7190; it has been noted by GNATS. From: Stefan Eggers <seggers@semyam.dinoco.de> To: nludban@salientsystems.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/7190: "Invalid partition table" after new install with multiple BSD slices Date: Tue, 21 Jul 1998 17:14:22 +0200 > >Fix: > Booted with a floppy, then used fdisk -a to set partition 1 active, and > it also set partion 2 inactive. System now boots without any problems. It actually is a bug in libdisk (checked in -current) I think! While searching the problem I was wondering why sysinstall didn't show my bootable FreeBSD partition as active. Fdisk correctly showed it as active after all. Then I began looking for where this flags gets read in. Nowhere! That is the main bug in there. The fix will be to add this to the code in disk.c in the libdisk directory. There is another bug in write_disk.c which is intended to fix a buggy partition table. If there is no bootable partition it will mark all FreeBSD partitions as bootable. As you created two such partitions it marked both bootable. This should either return an error or at least leave the partition table in a more reasonable state than this. Fdisk works because it bypasses libdisk and reads the MBR directly. That way this problem doesn't show up in fdisk use. Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807211530.IAA08046>