From nobody@FreeBSD.org  Wed Feb 23 18:56:02 2000
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id 61A0437B9C8
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 23 Feb 2000 18:56:02 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id SAA52033;
	Wed, 23 Feb 2000 18:56:02 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Message-Id: <200002240256.SAA52033@freefall.freebsd.org>
Date: Wed, 23 Feb 2000 18:56:02 -0800 (PST)
From: wayne@staff.msen.com
Sender: nobody@FreeBSD.org
To: freebsd-gnats-submit@FreeBSD.org
Subject: Sysinstall/disklabel: bad partition table when single->multiple slices
X-Send-Pr-Version: www-1.0

>Number:         16948
>Category:       bin
>Synopsis:       sysinstall(8): sysinstall/disklabel: bad partition table when single->multiple slices
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-sysinstall
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb 23 19:00:01 PST 2000
>Closed-Date:    
>Last-Modified:  Sun Jan 23 22:04:24 UTC 2011
>Originator:     Michael R. Wayne
>Release:        3.4 STABLE
>Organization:
Msen, Inc.
>Environment:
FreeBSD manor.msen.com
3.4-STABLE FreeBSD 3.4-STABLE #4: Sat Feb 12 00:33:23 EST 2000
root@cave.msen.com:/usr/src/sys/compile/CAVE
i386
>Description:
When converting a SCSI disk from dedicated to FreeBSD with a single
partition to multiple slices, sysinstall leaves the OLD label on the
disk. Sysinstall reads and writes the new information but O/S fails
to boot because it is still reading the old, invalid table.
>How-To-Repeat:
Using sysinstall, dedicate the entire disk to FreeBSD.  I was doing
newfs and s/w installs of minimal config but that should not matter.
Reboot from floppy and allocate 2 slices of approximately equal size.
Problem occurs with both standard MBR and the FreeBSD boot
manager (the boot manager will simply beep when you hit F1).
Sysinstall will permit you to install s/w again but when you reboot
after the second install, up comes the dreaded 
"Missing Operating System"
Going back in w/ sysinstall will show the NEW information, even though
the MBR is using the OLD info.  To see what is actually being used on 
the disk, boot the fixit floppy and 
disklabel -r sd0

>Fix:
Once I determined what was going on, I worked around the problem by 
doing a dd of /dev/zero to the disk and then re-doing the install.

I suggest that when the user deletes a slice from sysinstall, the 
operation should be performed immediately, unlike creates which 
can be deferred.

>Release-Note:
>Audit-Trail:

From: Sheldon Hearn <sheldonh@uunet.co.za>
To: wayne@staff.msen.com
Cc: freebsd-gnats-submit@FreeBSD.ORG, jkh@FreeBSD.org
Subject: Re: conf/16948: Sysinstall/disklabel: bad partition table when single->multiple slices 
Date: Tue, 29 Feb 2000 18:06:02 +0200

 On Wed, 23 Feb 2000 18:56:02 PST, wayne@staff.msen.com wrote:
 
 > When converting a SCSI disk from dedicated to FreeBSD with a single
 > partition to multiple slices, sysinstall leaves the OLD label on the
 > disk. Sysinstall reads and writes the new information but O/S fails
 > to boot because it is still reading the old, invalid table.
 
 Are you able to verify that this is a problem in the current FreeBSD 4.0
 RELEASE CANDIDATE?  Sysinstall's maintainer is under quite a lot of
 pressure at the moment with the upcoming release, and if you could check
 this on the 4.0 branch, I'm sure it'd be a massive help to him.
 
 Ciao,
 Sheldon.
 

From: "Michael R. Wayne" <wayne@staff.msen.com>
To: freebsd-gnats-submit@FreeBSD.org
Cc: jkh@FreeBSD.org, Sheldon Hearn <sheldonh@uunet.co.za>
Subject: Re: conf/16948: Sysinstall/disklabel: bad partition table when single->multiple slices
Date: Thu, 20 Jul 2000 12:10:32 -0400

 This problem is still present in 4.0 RELEASE.  Unfortunately, I
 did not re-examine the open PR database prior to my last FreeBSD
 conversion so I got bit by it again today.  So I have a completely
 installed and configured system ready to go, that will not boot.
 
 Is there any possibility of getting this into 4.1 RC?  It should
 be a fairly simple fix to either zero the prior contents of blocks
 1 & 2 on the disk before writing the partition table and boot blocks
 or to simply zero all contents of the old partition table when
 writing a non-dangerously-dedicated one.
 
 /\/\ \/\/
 
Responsible-Changed-From-To: freebsd-bugs->murray 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Thu Jul 20 09:49:28 PDT 2000 
Responsible-Changed-Why:  
Murray, could you take a look at this one?  I don't remember a fix 
going in for it, and it's quite a nasty. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=16948 
Responsible-Changed-From-To: murray->eric 
Responsible-Changed-By: murray 
Responsible-Changed-When: Thu Aug 30 15:43:23 PDT 2001 
Responsible-Changed-Why:  
Eric is the man 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=16948 
Responsible-Changed-From-To: eric->freebsd-qa 
Responsible-Changed-By: eric 
Responsible-Changed-When: Mon Oct 1 11:49:00 PDT 2001 
Responsible-Changed-Why:  
assign idle sysinstall bugs to freebsd-qa, as suggested by murray 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=16948 
Responsible-Changed-From-To: freebsd-bugs->brucec  
Responsible-Changed-By: brucec 
Responsible-Changed-When: Sat Mar 13 00:12:15 UTC 2010 
Responsible-Changed-Why:  
Take. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=16948 
Responsible-Changed-From-To: brucec->freebsd-bugs 
Responsible-Changed-By: brucec 
Responsible-Changed-When: Sun Jan 23 20:52:25 UTC 2011 
Responsible-Changed-Why:  
Back to the pool. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=16948 
Responsible-Changed-From-To: freebsd-bugs->freebsd-sysinstall 
Responsible-Changed-By: brucec 
Responsible-Changed-When: Sun Jan 23 22:04:05 UTC 2011 
Responsible-Changed-Why:  
sysinstall PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=16948 
>Unformatted:
