Bug 52713

Summary:	Need sanity checking on location user selects for boot loader to be written
Product:	[Retired] Red Hat Linux	Reporter:	Chris Rouch <cro>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9
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:	2006-02-21 18:48:07 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 Chris Rouch 2001-08-28 12:24:51 UTC

Description of Problem:

I did a fresh install on /dev/sda1 (first scsi disk), leaving my ide disks alone. I 
selected grub as the boot loader. I forget whether i selected /dev/sda or 
/dev/sda1 for the MBR. After installation, on reboot, the machine hung at 'LI'

Version-Release number of selected component (if applicable):


How Reproducible:
yes

Steps to Reproduce:
1.  unplug ide disks
2.  install seawolf on scsi disks (/dev/sda1 = /)
3. plug in ide disks
4. install roswell, selecting grub as boot loader

Actual Results:

system hangs at 'LI'

Expected Results:

Grub splash screen followed by boot

Additional Information:
	I saw this before on seawolf, and fixed it the same way - I unplugged 
my ide disks and re-installed as before. After installlation and first boot, plug in ide disks, and everything works as it should.

	I'm sure this was user error, but it would have been nice for the 
installation to have removed (or offered to remove) any LILO intsallation.

Comment 1 Jeremy Katz 2001-08-28 20:03:14 UTC

Yes, you MUST continue to install your boot loader to the same place on a new
install or upgrade (well, you can move to the MBR from the partition, but not
vice versa). 

I'm going to look into adding some more sniffing for the boot loader in the
future to try to keep people from having this problem, but it's too late for
this release due to screen freezes.

Comment 2 Michael Fulbright 2002-03-26 17:46:02 UTC

Deferring to future release.

Comment 3 Red Hat Bugzilla 2006-02-21 18:48:07 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.