From owner-freebsd-qa@FreeBSD.ORG Fri Jun 16 19:00:44 2006 Return-Path: X-Original-To: freebsd-qa@hub.freebsd.org Delivered-To: freebsd-qa@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1302116A481 for ; Fri, 16 Jun 2006 19:00:44 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B45A843D67 for ; Fri, 16 Jun 2006 19:00:40 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5GJ0eGN022136 for ; Fri, 16 Jun 2006 19:00:40 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5GJ0e4g022134; Fri, 16 Jun 2006 19:00:40 GMT (envelope-from gnats) Date: Fri, 16 Jun 2006 19:00:40 GMT Message-Id: <200606161900.k5GJ0e4g022134@freefall.freebsd.org> To: freebsd-qa@FreeBSD.org From: Heiner Cc: Subject: Re: bin/48341: [sysinstall] sysinstall deletes mbr although it should not X-BeenThere: freebsd-qa@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Heiner List-Id: FreeBSD Quality Assurance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2006 19:00:44 -0000 The following reply was made to PR bin/48341; it has been noted by GNATS. From: Heiner To: bug-followup@freebsd.org, freebsd-qa@freebsd.org Cc: Subject: Re: bin/48341: [sysinstall] sysinstall deletes mbr although it should not Date: Fri, 16 Jun 2006 21:01:37 +0200 I have now tested the installation of FreeBSD 6.1 on a machine with some other OS already existing. I've choosen 'none' as described in the bug description. The goal was to use the existing boot manager and point it afterwards to the FreeBSD installation as well. Result: the system was not bootable after the FreeBSD installation. An analysis shows, that the mbr was not deleted or destroyed; just the active flag was removed and the FreeBSD slice was set active. Setting the previous slice active resolved the problem! So the bug text should be replaced by: sysinstall changes the active slice flag although the corresponding sysinstall question was answered with "None - Leave Master Boot Record untouched" Heiner