Bug 1110920
Summary: | LVM: Existing Fedora rendered unbootable after installing Fedora n+1, missing grub entry | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Murphy <bugzilla> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, vanmeeuwen+fedora | ||||
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: | 2014-06-19 19:07:06 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: | |||||||
Attachments: |
|
Description
Chris Murphy
2014-06-18 19:10:19 UTC
Created attachment 910124 [details]
program.log
See also bug 964828, which is similar but is a grub2-mkconfig bug creating the properly formed entry for the prior Fedora system. OK so this is probably a duplicate of bug 825236. Hence it's also not EFI specific. Until we sort out how this is going to work, I think anaconda needs to warn the user that their prior install will become unbootable and require manual post install work. Borking their previously working system without notice and expecting them to figure it all out is the work of a user hostile installer. Actually this behavior is worse on UEFI because Anaconda obliterates the /boot/efi/EFI/fedora contents in favor of all new contents. So the previous systems's grub.cfg is lost. So it's a data loss bug on UEFI. On BIOS it's slightly less bad because the old grub.cfg still exists, merely requiring esoteric knowledge on the part of the user to fix the problem correctly. *** This bug has been marked as a duplicate of bug 825236 *** |