From nobody@FreeBSD.org  Thu Sep  9 18:45:20 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6254A16A4CF
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  9 Sep 2004 18:45:20 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1B66443D49
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  9 Sep 2004 18:45:20 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i89IjJmF027248
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 9 Sep 2004 18:45:19 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i89IjJSa027247;
	Thu, 9 Sep 2004 18:45:19 GMT
	(envelope-from nobody)
Message-Id: <200409091845.i89IjJSa027247@www.freebsd.org>
Date: Thu, 9 Sep 2004 18:45:19 GMT
From: Joe <fbsd_user@a1poweruser.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: multi-homed install trashes existing system & Freebsd will not boot
X-Send-Pr-Version: www-2.3

>Number:         71538
>Category:       i386
>Synopsis:       [install] multi-homed install trashes existing system & Freebsd will not boot [5.3beta3]
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    remko
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 09 18:50:14 GMT 2004
>Closed-Date:    Sun Sep 03 09:17:12 GMT 2006
>Last-Modified:  Sun Sep 03 09:17:12 GMT 2006
>Originator:     Joe
>Release:        5.3 beta3
>Organization:
Home
>Environment:
>Description:
   MS/Windows98 is first partition with 30% of 10 gig hard drive. This booted and worked as exspected. Downloaded 5.3-beta3 miniinstall.iso, ran md5 and verified correct hash with checksum.md5 file. burned to cdrom and installed second system on MS/Windows98 box with Freebsd default boot manager. Freebsd install went fine. On first reboot tried to load MS/Windows98. After F1 key boot just hung there doing nothing. Did pc reset and boot started again, this tim selected F3 key for 5.3 boot. After F3 key Freebsd 5.3 boot just hung there doing nothing.

Now hard drive is unusable. PC boot using MS/Windows98 floppy to get to native DOS prompt and ran fdisk which shows win98 and freebsd allocated as exspected. 
This also happened with 5.3-beta1 and had to DOS fdisk HD to single partition and format c: before was able to reinstall win98 from cdrom.

Just to test equipment I then installed 4.10 with default boot manager and every thing worked as exspected. 

5.3 install from downloaded iso image has show stopper problem using default boot manger.
>How-To-Repeat:
      
>Fix:
      
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: delphij 
State-Changed-When: Thu Sep 16 16:22:07 GMT 2004 
State-Changed-Why:  
Dear submitter, 

I am really sorry to hear that your existing system were destoried. 
With an similiar installation I was unable to reproduce your issue, 
did you marked two "bootable" partition during FreeBSD installation 
(say, two "A"s during you are creating the FreeBSD partition)? 

More technically: 

I have heard some complaints that when installing FreeBSD on a 
multi-boot configuration and mark two "bootable" partitions then 
system will go unbootable.  This is because that the "bootable" 
flag is actually "activate" flags on partitions, which is only 
allowed on one partition or the partition table would be considered 
to be invalid. 

With a safebelt introduced in src/usr.sbin/sysinstall/disks.c,v 1.153 
it's more likely that users wouldn't set two "active" partition 
at the same time, so if this was your problem, then we would likely 
to have an improved sysinstall(8) that won't cause an unbootable 
system. 

Please let me know if this is the issue so we can take more action 
on it, and thanks for supporting the release engineering of the 
upcoming 5.3-RELEASE! 


Responsible-Changed-From-To: freebsd-i386->delphij 
Responsible-Changed-By: delphij 
Responsible-Changed-When: Thu Sep 16 16:22:07 GMT 2004 
Responsible-Changed-Why:  
Dear submitter, 

I am really sorry to hear that your existing system were destoried. 
With an similiar installation I was unable to reproduce your issue, 
did you marked two "bootable" partition during FreeBSD installation 
(say, two "A"s during you are creating the FreeBSD partition)? 

More technically: 

I have heard some complaints that when installing FreeBSD on a 
multi-boot configuration and mark two "bootable" partitions then 
system will go unbootable.  This is because that the "bootable" 
flag is actually "activate" flags on partitions, which is only 
allowed on one partition or the partition table would be considered 
to be invalid. 

With a safebelt introduced in src/usr.sbin/sysinstall/disks.c,v 1.153 
it's more likely that users wouldn't set two "active" partition 
at the same time, so if this was your problem, then we would likely 
to have an improved sysinstall(8) that won't cause an unbootable 
system. 

Please let me know if this is the issue so we can take more action 
on it, and thanks for supporting the release engineering of the 
upcoming 5.3-RELEASE! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71538 
State-Changed-From-To: analyzed->open 
State-Changed-By: delphij 
State-Changed-When: Thu Sep 16 17:30:17 GMT 2004 
State-Changed-Why:  
According to the feedback from the originator this is more likely to be 
something wrong with certain processes happens after the MBR so return 
this back to pool.  


Responsible-Changed-From-To: delphij->freebsd-i386 
Responsible-Changed-By: delphij 
Responsible-Changed-When: Thu Sep 16 17:30:17 GMT 2004 
Responsible-Changed-Why:  
According to the feedback from the originator this is more likely to be 
something wrong with certain processes happens after the MBR so return 
this back to pool.  

http://www.freebsd.org/cgi/query-pr.cgi?pr=71538 

From: david <davidrussell@bellnet.ca>
To: fbsd_user@a1poweruser.com, bug-followup@FreeBSD.org
Cc:  
Subject: Re: i386/71538: [install] multi-homed install trashes existing
	system & Freebsd will not boot [5.3beta3]
Date: Fri, 24 Feb 2006 06:16:28 +0000

 similar problem but had boot magic on otherportion of disk,install that
 and it fixes problem
 

From: "fbsd_user" <fbsd_user@a1poweruser.com>
To: "david" <davidrussell@bellnet.ca>,
	<bug-followup@FreeBSD.org>
Cc:  
Subject: RE: i386/71538: [install] multi-homed install trashes existing system & FreeBSD will not boot [5.3beta3]
Date: Fri, 24 Feb 2006 06:44:12 -0500

 I fall to see how using this "boot magic" program
 fixes FreeBSD from causing this problem in the first place.
 This is no solution.
 Its a work around after the FreeBSD sysinstall causes the problem.
 
 I hope you don't think this closes this problem report.
 
 -----Original Message-----
 From: david [mailto:davidrussell@bellnet.ca]
 Sent: Friday, February 24, 2006 1:16 AM
 To: fbsd_user@a1poweruser.com; bug-followup@FreeBSD.org
 Subject: Re: i386/71538: [install] multi-homed install trashes
 existing system & Freebsd will not boot [5.3beta3]
 
 
 similar problem but had boot magic on other portion of disk, install
 that
 and it fixes problem
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: remko 
State-Changed-When: Sun Sep 3 09:12:22 UTC 2006 
State-Changed-Why:  
Hi, 

We are a couple of releases further in life today and I wanted 
to see whether the problem still persists (esp since the used 
version appeared to be a -BETA).  Can you confirm that this 
problem is still there in 5.5 and 6.1? 

Thanks! 


Responsible-Changed-From-To: freebsd-i386->remko 
Responsible-Changed-By: remko 
Responsible-Changed-When: Sun Sep 3 09:12:22 UTC 2006 
Responsible-Changed-Why:  
Grab the PR. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=71538 
State-Changed-From-To: feedback->closed 
State-Changed-By: remko 
State-Changed-When: Sun Sep 3 09:16:20 UTC 2006 
State-Changed-Why:  
We cannot recieve feedback from the submitter anymore 
since his mail address had vanished from the internet. 

Close the PR with this reasoning, if someone steps over 
this issue, please feel free to update me and we can see 
what we can do about the PR's then. 

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