Bug 810207
Summary: | Unable to upgrade to Fedora 17 pre-release | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas Spear <Speeddymon> |
Component: | preupgrade | Assignee: | Richard Hughes <hughsient> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | alexander, alex, hughsient, lee.newton, mark, sgireeshmail |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-13 14:42:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Thomas Spear
2012-04-05 10:47:48 UTC
I have the same Dracut error message upon booting and doing the upgrade. This is on a HP laptop and /var is not on its own partition. Im using a encrypted filesystem and does not get a password prompt for the filesystem. I am facing the issue with my desktop. I have a single 15GB partition for / of size 15GB out of which 3.6GB is free after downloading all the files required for preupgrade. On reboot, I get the Upgrade to F17 option but it suddenly says "root volume not found" and drops me to a dracut shell. Possibly the same problem as in bug 798779? I do not believe this is the same as bug 798779, because that bug applies to after the preupgrade install finishes when you are to reboot into the just upgraded OS. In addition, that bug also references bug 813973 which is due to a small /boot partition causing dracut to download the necessary boot files from the web, but failing to do so due to a recursion bug. At any rate, I read somewhere that this was a known problem with the beta preupgrade, and that it was scheduled to be fixed before final. I am not certain if this is fixed in final or not, as I do not have an F16 machine any longer to test on (I went ahead and wiped the VM and installed the F17 beta to it via LiveCD). If anyone does know, feel free to update. I have the same Dracut error message upon booting and doing the upgrade. This is on a Sony laptop and /var is not on its own partition. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |