Red Hat Bugzilla – Bug 426093
2 anaconda installations on a single system use conflicting partition labels
Last modified: 2008-06-21 12:07:58 EDT
Description of problem:
I installed RHEL5.1 on sda. Then I did another install onto sdb to test my kickstart.
anaconda used the same labels on sdb as on sda (as it does on everything), meaning that when I
booted from sdb1 (/boot), I got the rest of the filesystems from sda, and lots of things broke.
Since anaconda doesn't check for the presence of labels before using assigning labels to partitions, it's
impossible to do two anaconda installs onto the same system without conflicts which require manual
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install onto partitions on sda.
2.Install onto partitions on sdb.
anaconda leaves GRUB pointing to sdb, but when booted /boot on sdb1 mounts the earlier filesytems
on sda by labels.
Things break, particularly modules.
anaconda should not assign labels without checking to see if they're in use.
kickstart should have an option to use partition devices rather than labels.
The next major release of RHEL will be using UUIDs for partition identification
instead of labels, so you should no longer be seeing these sorts of problems.
If you require this fix in an update release of RHEL5, please talk to your
support representative who will raise it to us through the appropriate channels.