Bug 53677
Summary: | Embedded e2fs_stage1_5 won't boot on CHS=119150/16/63 | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Alexandre Oliva <aoliva> |
Component: | grub | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | roswell | ||
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-11-29 06:44:00 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
Alexandre Oliva
2001-09-14 19:41:52 UTC
What do you get if from the grub shell you type geometry (hd0) ? drive 0x80: C/H/S = 53614/16/63, The number of sectors = 120103200, /dev/hda looks reasonable, as far as the 32GB limit on CHS access goes. It shouldn't affect access to the /boot partition, though. Or should it? Or should I force LBA mode enabled or disabled? If you use lilo with lba32 in /etc/lilo.conf, do you have any problems? Please rephrase the question bearing in mind that the problem showed up in grub, i.e., without using lilo. Right, if you install lilo on the system and have the lba32 keyword in /etc/lilo.conf, are you able to boot? Basically, I'm trying to determine if it's the LBA32 stuff causing breakage (as I suspect) as GRUB and LILO both do it similarly Ok, I've set up lilo with lba32, and indeed it failed to boot too. It would print an infinite sequence of `2 '. |