From owner-freebsd-bugs@FreeBSD.ORG  Mon Nov 24 18:58:03 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id EACE84A5
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Nov 2014 18:58:03 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D32C069
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Nov 2014 18:58:03 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAOIw3b7024302
 for <freebsd-bugs@FreeBSD.org>; Mon, 24 Nov 2014 18:58:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195294] FreeBSD overwrote Windows BIOS
Date: Mon, 24 Nov 2014 18:58:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 8.4-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: lgfbsd@be-well.ilk.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-195294-8-KB8pbJWFO1@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195294-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195294-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Nov 2014 18:58:04 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195294

lgfbsd@be-well.ilk.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lgfbsd@be-well.ilk.org

--- Comment #1 from lgfbsd@be-well.ilk.org ---
The BIOS is not involved here; the bootloader is where the problem is coming
from (if someone with the appropriate powers could change the subject, that
would be helpful). This would have been easier to take care of on the technical
support mailing list, because there isn't enough information in the report to
figure out what has gone wrong here.

The first step in looking at the problem will be to determine whether the disk
is using an old-style "MBR" partitioning or a newer "GPT" partitioning. This
can be determined from the gpart(8) command, "gpart show /dev/<whatever device
your disk is>". 

The second step is to make sure that the Windows partition is still present.
That should also be present in the output from "gpart show". 

Assuming that you have an MBR-partitioned disk, the third step is to reinstall
the bootloader and configure it to show all partitions. See the FreeBSD
Handbook section on bootloaders to be sure, but I think the command would be
"boot0cfg -B -m 0xf".

-- 
You are receiving this mail because:
You are the assignee for the bug.