Bug 29390 - lba32 not configured during install
Summary: lba32 not configured during install
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-25 15:51 UTC by Brian Ryner
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-20 19:09:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brian Ryner 2001-02-25 15:51:28 UTC
During installation, anaconda claimed that my system is not capable of
booting from past 1024 cylinders (lba32).  My system IS lba32-capable.  It
therefore used the "linear" option instead of "lba32" in lilo.conf, giving
me a non-booting system.

The system is a Dell Dimension 4100; let me know if there is any other
information that would be helpful.

Comment 1 Michael Fulbright 2001-02-25 16:15:40 UTC
This would most likely mean that when we used the EDD BIOS call to ask if your
board supports lba32, it returned that it did not.

Just boot from the boot floppy you were encouraged to make during the install
process, edit the /etc/lilo.conf and switch it to using lba32, rerun lilo and
then see if you can login.

We have encountered ALOT of problems with different BIOSes supported lba32
differently, so we touch the current conservative approach until we have more

Comment 2 Brian Ryner 2001-02-25 16:43:35 UTC
Oops, I guess I should have mentioned that.  I booted from the CD in rescue
mode, edited lilo.conf as you suggested, re-ran lilo, and all is fine.

Comment 3 Michael Fulbright 2001-02-27 23:28:19 UTC
We should take another look at this to be sure, assigning to an engineer.

Comment 4 Brian Ryner 2001-03-06 21:39:01 UTC
Still happening as of RC2.  This results in a non-bootable system, and there is
no way during the install to force it to use lba32.

Comment 5 Michael Fulbright 2001-03-20 19:09:41 UTC
I am making a change to always write lba32 if the boot partition is above the
1023 limit. This should handle your case correctly.

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