Description of problem: While mounting filesystem using labels avoids the need to locate the specific device it can easily lead to catastrophic situations. For example, if one mounts a root filesystem from another system for passive examination or whatever, this can lead to accidental mounting (and alteration) of the wrong filesystem. So one has no choice but to alter the filesystem label. Version-Release number of selected component (if applicable): setup-2.6.10-1 How reproducible: Always Steps to Reproduce: 1. Add an extra disk with root filesystem (with same label, eg /root) from another system 2. Boot up 3. What will the root filesystem be? Actual results: Either root filesystem might activate according to some indeterminate rule. Expected results: If multiple filesystems with the same label are found the user should be prompted to select the correct one. Additional info:
Sorry, that's something what could not be solved by setup and /etc/fstab modification. Although likely will be closed notabug, only place where something like that could be handled is mount utility... and therefore reassigning component to util-linux-ng.
The root filesystem is mounted by nash (initrd). You have to use UUID (also in grub.conf for root FS) if you want to avoid collision between two filesystems -- the recent fedora installer uses this solution. The way how mount(8) resolving LABEL/UUID is deterministic, higher priority has previously mounted device (according to the /etc/blkid/blkid.tab cache file). Sorry, but solution which is based on interaction with user is useless.