Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 227

Summary: Installer writes bad lilo.conf with multiple DOS partitions
Product: [Retired] Red Hat Linux Reporter: mvarso
Component: installerAssignee: David Lawrence <dkl>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5.2CC: mvarso
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-11-30 16:03:40 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 mvarso 1998-11-30 05:45:08 UTC
Note: Here I assume that the root.img and boot.img -files in
official RedHat ditribution (ie. CD-ROM) are identical with
those found in ftp.redhat.com. If that is not the case this
applies only to the files found in ftp site and its mirrors.

If there is already more than one DOS/Win partitions on the
disk(s), install program writes a section for all of them in
/etc/lilo.conf.
Problem is, that is gives all of them same label and lilo
refuses to understand that.
Result is that install program pops up an error in
"installing lilo" stage.
Install program continues othervice normally and quits
cleanly, but lilo will (of cource) not boot the system after
reset as expected.

Trivial solution is to use "custom boot" -disk and manually
clean up /etc/lilo.conf.
But I think it is not the first thing a newbie
wants/can do :)

It may well be that if DOS partitions are not marked as
"assessible" within install program, this bug won't appear.

I have heard at least two other people having same problem.
One of them had scsi disks and was upgrading from
RH5.1. Problem was still excactly the same.
(My system was normal pentium with two IDE disks)

Comment 1 Bill Nottingham 1998-11-30 16:03:59 UTC
*** This bug has been marked as a duplicate of 204 ***