Bug 882534
| Summary: | After an upgrade from F17 to F18 using fedup, F18 can't boot (unable to mount FS). | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Olivier LEVILLAIN <olivier.levillain> |
| Component: | grub2 | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | bcl, dcantrell, dennis, mads, pjones |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-12-02 12:28:15 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
Olivier LEVILLAIN
2012-12-01 18:26:16 UTC
Will grub2-config create a correct grub.cfg ? I guess the problem is that grubby is trying to clone the upgrade entry when it is creating the entry for the new kernel. This would thus essentially be a duplicate of Bug 873455; they do in my opinion have the same root cause and the same solution. (In reply to comment #1) > Will grub2-config create a correct grub.cfg ? > > I guess the problem is that grubby is trying to clone the upgrade entry when > it is creating the entry for the new kernel. > > This would thus essentially be a duplicate of Bug 873455; they do in my > opinion have the same root cause and the same solution. Hi Mads yes, grub2-config created a correct grub2.cfg file (at least with an initrd line). Yet, the system doesn't crash anymore at startup but doesn't start correctly (telling that "something went wrong" and that's all) I mark this bug as a duplicate of Bug 873455; as the remaining problem has nothing to do with this bug I think. *** This bug has been marked as a duplicate of bug 873455 *** Others might argue that it is a bug in grubby that it can't clone the upgrade entry or a bug in fedup that it doesn't uninstall the upgrade kernel before installing the new kernel (which creates the new boot entry using grubby). |