Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 6740 - RH installation program broke my LILO
Summary: RH installation program broke my LILO
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-11-05 01:37 UTC by dserodio
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-02-22 15:03:28 UTC

Attachments (Terms of Use)

Description dserodio 1999-11-05 01:37:50 UTC
I was using RH 6.0, on /dev/sda5, with LILO installed on
/dev/sda5 (and /etc/lilo.conf also knew that). I use System
Commander on my MBR and winndows on /dev/sda1. When I
upgraded to 6.1, by booting from the CD-ROM and choosing the
custom upgrade option, the RH setup program installed LILO
on my MBR!!!
	As a result, I couldn't boot my windows partition
(/dev/sda1) but Linux booted ok. I had to reinstall System
Commander. Then I couldn't boot Linux!!! Maybe because the
kernel changed, lilo (the one on /dev/sda5) stopped after
saying 'LIL-'.
	I spent 2 days trying to install lilo again, from a boot
disk, because it complained about 'First boot sector does
not contain a valid boot sector' whether I tried it on
/dev/sda or /dev/sda5. The other day, when I was trying to
install it for the last time, before tragically formatting
my Linux partition, it installed (with no special options
	Well, sorry if I wrote too much, but I really got pissed at
the RH setup stuff. It REALLY should read /etc/lilo.conf or
something to know where lilo is.

Comment 1 Cristian Gafton 2000-01-04 22:20:59 UTC
Assigned to dledford

Comment 2 Bernhard Rosenkraenzer 2000-02-17 20:30:59 UTC
This is a bug in the installer, not lilo itself. Reassigning.

Comment 3 Jay Turner 2000-02-22 15:03:59 UTC
This issue was fixed with errata available for 6.1.

Note You need to log in before you can comment on or make changes to this bug.