Bug 488788
Summary: | Unable to complete post-installation of Fedora11. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Christoph van der Reijden <christophvanderreijden> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | anaconda-maint-list, vanmeeuwen+fedora |
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: | 2010-06-28 11:24:18 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
Christoph van der Reijden
2009-03-05 18:40:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Is this reproducable with F12 beta? Hi Chris, Thank you for your request. The short answer is that the problem I reported for F11-alpha is not reproducible with F12 beta on exactly the same hardware platform. The detailed answer is that both F11 (not alpha) and F12-beta needed F10 preinstalled to enable installation using the "replace existing Linux system" option. Using this installation path, I was able to install F11 and F12 beta. However, after finalizing the F11 installation unlike F10, a program on the upper panel kept on complaining about a possible bad condition (i.e. the reallocated sector count was 44 which was classified as "too high") of my harddrive. After finalizing the F12 beta post-installation and login as a user and after the upper panel appeared on the screen, the screen turned itself off. Starting from a completely zero-ed harddisk, using a software-tool from harddisk company Seagate, F11 and F12 beta were not able to initialize the harddrive properly, F10 had the "retry" option but F11 and F12 beta did not had one. Concluding remark: it seems that F10 had a more tolerant check of the harddrive condition than F11 and F12beta. This might have contributed to installation problems of F11 and F12 beta. If you need more info, please let me know. Regards, Christoph. This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |