Bug 161113

Summary:	bsdinstall(8): 9.0-BETA3: overwrites Win*-bootcodes without warning?
Product:	Base System	Reporter:	Kalten <kalten>
Component:	bin	Assignee:	freebsd-sysinstall (Nobody) <sysinstall>
Status:	Closed Overcome By Events
Severity:	Affects Only Me	CC:	rdawson
Priority:	Normal	Keywords:	install
Version:	1.0-CURRENT
Hardware:	Any
OS:	Any

Description Kalten 2011-09-28 23:30:08 UTC

Created new partitions and slices (MBR-Mode).
bsdinstall has overwritten Win7 boot code, es it seems---no questions
any more (like in sysinstall) whether we want it to do this or not!?

(Win7 still there (mountable in freeBSD), but not bootable.
Neither ``Startup repair'' nor bootrec in the ``command Prompt'' of
Win7's DVD could repair it---althoug dir works on it in the mentioned
win-cmd-prompt.)

I am sure, that I am not the only one who would appreciate it very much,
if we had the chance to choose whether to write down a bootloader into
the disk or not (as we had with sysinstall)

How-To-Repeat: Created new partitions and slices (MBR-Mode) in new installer called
bsdinstall.

Comment 1 Eitan Adler freebsd_committer

2011-10-06 06:00:07 UTC

Responsible Changed
From-To: freebsd-bugs->freebsd-sysinstall


fix synopsys and assign

Comment 2 Nathan Whitehorn freebsd_committer

2011-10-23 16:23:49 UTC

State Changed
From-To: open->feedback

Can you provide some more detail on how this happened? bsdinstall never 
touches the MBR under any circumstances, so this having happened may indicate 
a kernel bug.

Comment 3 Eitan Adler freebsd_committer

2018-05-28 19:46:50 UTC

batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.

Comment 4 Mark Linimon freebsd_committer

2024-11-17 03:43:11 UTC

^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of suppoprt.
Please re-open if it is still a problem on a supported version.