Bug 213111

I have verified that /dev/md0, /dev/sda1, /dev/sdb1 indeed contain the same
label ('/home/media') via e2label(8). I think I will mess up my RAID1 setup if I
change that, am I correct ? If it is so then this is bug in anaconda.

I have used the following workaround:

1. remove /dev/md0 from /etc/fstab
2. move /etc/mdadm.conf to /etc/mdadm.conf.disabled
3. disconnect sda1, sdb1 from SATA cables (physically)
4. reboot from FC6 DVD
5. upgrade the system
6. get the RAID configuration back

After that I have booted FC6 from upgraded hard-drive and everything was fine.

Could someone plase confirm that this is a bug ?

Yeah, looks like this is even a known bug according to this comment in fsset.py:

# XXX fix RAID
def readFstab (path, intf = None):

What does /etc/fstab look like on the system you are trying to upgrade?

This is the way it looks after upgrade:

/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /dev/shm                tmpfs   defaults        0 0
#LABEL=/home/media       /home/media             ext3    defaults        1 2
# /home/media je RAID 1 (mirror) of /dev/sda1 and /dev/sdb1
# /dev/md0 nekontrolovat via fsck - proto "0 0"
/dev/md0                /home/media             ext3    defaults        0 0
none                    /proc                   proc    defaults        0 0
none                    /sys                    sysfs   defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0


I am pretty sure it looked the same before the upgrade.

This bug is still present in FC7. I had to go through the dirty cable work again :)

This is still present in FC8. I had to open the case and disconnect the disks in RAID in order to complete 
the upgrade. It's interesting notion - in order to modify software one has to modify the hardware.. Is this 
really so hard to fix this ?

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

This bug is still present in the upgrade program in FC8.

Please give F10 Beta a try.  I've since removed the code that checks for duplicate labels in all cases, except if you have LABEL= in your fstab.  In that case if multiple things are labelled the same, we really will have to error out.  However if you're not actually using the label in your /etc/fstab (which it looks like you aren't), there's no reason we should be checking and failing there.

This bug is still present in F10. I tried upgrading from F8 to F10, and I received this same error. It's a show-stopper. Please re-open this ticket.