Bug 85741
Summary: | Duplicate label causes incorrect boot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Christian Jiresjö <ds98chji> |
Component: | mkinitrd | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-04-02 06:00:17 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
Christian Jiresjö
2003-03-06 19:12:44 UTC
the kernel doesn't know anything about labels... mkinitrd does Reassigning If we instead don't use labels, it causes problems for a different category of moving disks around. Labels are the best of the available evils right now. I ran into this too recently. I had a system that I was going to upgrade to FC1 from RH7. I took out the old disk. Put in a new one. Installed FC1. Put back the old disk as secondary master (hdc) in order to copy over all my old data to the new system. Booted and got all sorts of weird stuff, like the FC splash screen on boot but it was RH7 that actually was booted! I understand why labels might be preferable, but perhaps to mitigate this problem the system should use the first/earliest label match it finds rather than the last/latest. Almost certainly you'd prefer to boot off of hda in most circumstances where this problem might occur by accident. Think from a newbie's perspective. As Christian says, ditching the labels and hardcoding /dev/hda3 in grub.conf makes a good workaround. |