From nobody  Mon Jul  6 14:30:02 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA22304;
          Mon, 6 Jul 1998 14:30:02 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199807062130.OAA22304@hub.freebsd.org>
Date: Mon, 6 Jul 1998 14:30:02 -0700 (PDT)
From: nludban@salientsystems.com
To: freebsd-gnats-submit@freebsd.org
Subject: "Invalid partition table" after new install with multiple BSD slices
X-Send-Pr-Version: www-1.0

>Number:         7190
>Category:       misc
>Synopsis:       "Invalid partition table" after new install with multiple BSD slices
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    phk
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul  6 14:30:00 PDT 1998
>Closed-Date:    Fri Nov 16 15:01:03 PST 2001
>Last-Modified:  Fri Nov 16 15:01:10 PST 2001
>Originator:     Neil Ludban
>Release:        2.2.6-RELEASE
>Organization:
Salient Systems
>Environment:
New install off 2.2.6-RELEASE CD (no uname output since it's now running
a custom kernel)
>Description:
Did a custom install and split a 2G scsi disk into (2) 1G slices to get
around the 8 partitions/slice limit.  sysinstall marked both slices
active, and the standard boot loader halted with "Invalid partion
table" error.  Was able to boot the system using a floppy.
>How-To-Repeat:

>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.

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->suspended 
State-Changed-By: phk 
State-Changed-When: Tue Jul 7 02:39:09 PDT 1998 
State-Changed-Why:  
Yeah, well, I guess it is a bug, but the short version is: Don't do that then. 

From: Stefan Eggers <seggers@semyam.dinoco.de>
To: nludban@salientsystems.com
Cc: freebsd-gnats-submit@freebsd.org, seggers@semyam.dinoco.de
Subject: Re: misc/7190: "Invalid partition table" after new install with multiple BSD slices 
Date: Tue, 21 Jul 1998 16:11:46 +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.
 
 The propper fix is to change sysinstall.  It shall not mark a new
 slice active unless it would be the only active one.  Then it will
 work.
 
 I'll take a look into its source and try to get a simple and under-
 standable fix ready.
 
 Stefan.
 -- 
 Stefan Eggers                 Lu4 yao2 zhi1 ma3 li4,
 Max-Slevogt-Str. 1            ri4 jiu3 jian4 ren2 xin1.
 51109 Koeln
 Federal Republic of Germany

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.
Responsible-Changed-From-To: freebsd-bugs->jkh 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Tue Mar 23 04:58:20 PST 1999 
Responsible-Changed-Why:  
libdisk is Jordan's baby. 
Responsible-Changed-From-To: jkh->phk 
Responsible-Changed-By: jkh 
Responsible-Changed-When: Mon Dec 13 12:15:44 PST 1999 
Responsible-Changed-Why:  
This is a libdisk bug and actually for phk to fix.  I also don't see 
Stefan's attached patches, though he alludes to having some. 
State-Changed-From-To: suspended->closed 
State-Changed-By: phk 
State-Changed-When: Fri Nov 16 15:01:03 PST 2001 
State-Changed-Why:  
timed out 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=7190 
>Unformatted:
