Bug 44379 - Disk druid don't add lba32 to lilo.conf when making a raid array above cyl 1024
Disk druid don't add lba32 to lilo.conf when making a raid array above cyl 1024
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-06-13 04:34 EDT by Geir Thomassen
Modified: 2007-04-18 12:33 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-06-13 04:34:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Geir Thomassen 2001-06-13 04:34:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; rv:0.9.1)
Gecko/20010607

Description of problem:
Disk druid (anaconda) need to add the "lba32" option instead of the
"linear" option to lilo.conf when making a bootable raid array above cyl
1024. The result is that lilo fails to install, and the system won't boot.

How reproducible:
Always

Steps to Reproduce:
1.Create two partitions on two discs above cyl 1024
2.Add these two partitions to a raid 1 array (eg. md0) and assign this
array to / (root)
3.Continue installation, you will get an error message when anaconda tries
to run lilo.
4. Restart ....
	

Actual Results:  Lilo can't boot the system since lilo.conf was created
with the linear option instead of lba32. You have to boot on a floppy, and
fix lilo.conf.

Additional info:
Comment 1 Brent Fox 2001-06-21 15:19:59 EDT
The entire partitioning subsystem is being rewritten, so this bug should not
appear in the future.

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