Bug 124038
Summary: | Upgrades From Fedora Core 1 to Fedora Core 2 In Dual Boot Situation Renders Second Drive Unbootable | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bob Cochran <cochranb> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | ||
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: | 2004-05-24 02:35:35 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
Bob Cochran
2004-05-23 03:51:15 UTC
I think all is well now. I forgot to change the /kernel line in my grub stanza for /dev/hdb from /kernel vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/ acpi=on nogui to /kernel vmlinuz-2.4.22-1.2188.nptl ro root=LABEL=/1 acpi=on nogui when I did this, hdb booted into Fedora Core 1 very nicely and all is well. I do not now think I had data loss, this seems a case of a missing partition label in the grub stanza. But I still think grub shouldn't trash my existing grub.conf stanzas if there is a dual-boot situation. Why not just add an appropriate stanza for the new kernel instead? To me specifying 'upgrade' on the bootloader means upgrading the executable binaries to a new version, not overlaying the config file(s). I would have been okay if only a new grub.conf stanza was added. And there seems no reason from a new options standpoint to completely wipe out an existing grub.conf. So this bug can be downgraded from a serious bug to something lesser. The kernel got upgraded and thus the binary was no longer there and thus the reference to it got removed from the grub.conf. This is the expected behavior. If your grub line for the second drive had been correct to begin with, then it wouldn't have gotten removed. Jeremy -- I disagree with this statement: "If your grub line for the second drive had been correct to begin with, then it wouldn't have gotten removed." My grub line for the second drive had existed since I installed it, and was indeed correct to begin with. I've been dual booting two different Fedora Core 1 implementations for months before upgrading to Fedora Core 2. It originally did reference 'root-LABEL=/1'. When I upgraded Fedora Core 2, all the grub lines for the second drive were trashed. That forced me to manually type one stanza for that drive, which didn't reference the second drive correctly (no LABEL=/1). I corrected that after realizing my error. Grub was wrong to delete grub.conf stanzas for my second drive. It does indeed do that and I see no reason for the behavior. You might be able to justify deleting the stanzas for the drive being upgraded to the new Fedora release, but never for a second or nth drive that was not updated and might have a different OS on it. |