Bug 29390
Summary: | lba32 not configured during install | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Brian Ryner <bryner> |
Component: | anaconda | Assignee: | Matt Wilson <msw> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
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: | 2001-03-20 19:09:45 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
Brian Ryner
2001-02-25 15:51:28 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 data. 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. We should take another look at this to be sure, assigning to an engineer. 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. I am making a change to always write lba32 if the boot partition is above the 1023 limit. This should handle your case correctly. |