Bug 215226
| Summary: | Boot stalls at "Loading stage 2.." after a fresh install | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Jørgensen <mij> |
| Component: | anaconda | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6 | CC: | triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | bzcl34nup | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-05-06 16:47:25 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
Michael Jørgensen
2006-11-12 16:38:20 UTC
*** Bug 215227 has been marked as a duplicate of this bug. *** After a fresh install of FC6 (and verifying that the boot stops after "Loading stage2.." I physically moved the SATA disk to a Dell dimenstion 9150 computer I recently bought. Here the system boots and loads the kernel, but fails to mount the root file system, presumably because of incorrect SATA drivers. The driver loading by the Fedora installation is sata_via. Then I replaced the SATA disk with a PATA disk in my original system and reinstalled FC6. This time the systems boots fine. Going back to the SATA disk (where it stops at Loading stage2..), I tried going into rescue mode and then 1. chroot /mnt/sysimage 2. /sbin/grub 3. configfile /boot/grub/grub.conf This once again presents me with the "Error 28: Selected item cannot fit into memory". The I tried getting GRUBs memory information: grub> displaymem EISA Memory BIOS Interface is present Address Map BIOS Interface is present Lower memory: 640K, Upper memory (to first chipset hole): 3072K [Address Range Descriptor entries immediately follow (values are 64-bit)] Usable RAM: Base Address: 0x0 X 4GB + 0x0, Length: 0x0 X 4GB + 0xa0000 bytes Reserved: Base Address: 0x0 X 4GB + 0xa0000, Length: 0x0 X 4GB + 0x60000 bytes Usable RAM: Base Address: 0x0 X 4GB + 0x100000, Length: 0x0 X 4GB + 0x300000 bytes grub> Don't know if that is useful. Workaround found! I followed the suggestion in <http://forums.fedoraforum.org/forum/showthread.php?t=108936> and changed the setting in the BIOS for SATA mode from RAID to IDE. This has solved my problem. However, I still believe there are several issues with GRUB/anaconda. Firstly, the error reporting is terrible. It was pure luck that brought me to the solution mentioned above. This has cost me (and other people) many hours of debugging. Presumably the anaconda installation could check for "incorrect" BIOS settings, or someone should write a note about it in the release notes. Secondly, what if I *did* need raid support? Surely, it is not acceptable to say that hardware raid is not supported. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |