Bug 349

Summary: Overwritten Master Boot Record
Product: [Retired] Red Hat Linux Reporter: pete.nelson
Component: installerAssignee: David Lawrence <dkl>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1998-12-08 16:57:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description pete.nelson 1998-12-08 14:38:00 UTC
I was installing RH 5.2 on a dual-boot system with a Western
Digital Hard Drive that needs it's own proprietary drivers
loaded at start-up (the drive is only used under Windows).

When I got to the step in installation to determine the
method of booting (where would you like LILO?), I chose
'Skip' (I already made my boot floppy).  It still managed to
overwrite the master boot record, so I had to rewrite the
MBR with the western digital junk.

Not a big deal for me, but I know there are plenty that
would have been dead in the water at that point.

Otherwise, wow!  Linux that can talk to my printer & sound
card!  I love it!  (Maybe I can convince my wife we don't
need the Windows boot!)

Comment 1 Derek Tattersall 1998-12-08 16:57:59 UTC
Unable to reproduce problem.  Choosing SKIP did not overwrite MBR in
test cases.