This is a known issue, and history captured in:<br><br><span>Bugzilla Bug 160622: Installer does not upgrade from previous versions when there is more than one unlabled swap partition</span><br><br><a href="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160622">
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160622</a><br><br>If only google searching for the error message had shown me the light... Hopefully if I capture some useful information here on fedora-list, the archives will match searches, and future users won't be left in the dark.
<br><br>Steve<br><br><div><span class="gmail_quote">On 3/7/07, <b class="gmail_sendername">Steve Lacy</b> <<a href="mailto:slacy@slacy.com">slacy@slacy.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This issue was caused by having multiple, unlabeled swap partitions, which anaconda then improperly identified as all having the same "label".<br><br>The fix was to run "swapoff -a" to turn off all swap, then, for each swap partition, run "mkswap /dev/XXX -L swap_XXX" where "XXX" is the name of the swap device.
<br><br>After doing this, the anaconda upgrader worked just fine, and I'm writing this from my new FC6 system. Hooray!<br><br>I'll be filing a bug against anaconda about this issue.<br><span class="sg"><br>Steve
</span><div><span class="e" id="q_1112dbb1e00398d0_2"><br><br><div><span class="gmail_quote">
On 3/5/07, <b class="gmail_sendername">Steve Lacy</b> <<a href="mailto:smlacy@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">smlacy@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi, <br><br>I'm trying to upgrade from FC4 to FC6 before this DST bug hits... <br><br>I boot the FC6 installer, get to anaconda where I can select the upgrade, and I get a dialog box that says:<br><br>"Multiple devices on your system are labeled k?;[]qu??lqBs,?|. Labels across devices must be unique for your system to function properly. Please fix this problem and restart the installation process."
<br><br>The "[]" in that is actually a unicode box with the numbers 0,0,1,3 in it. Anyway, I certainly didn't manually label any of my filesystems with that string. Here's my /etc/fstab:<br><br>/dev/md0 / ext3 defaults 1 1
<br>/dev/sda1 /boot ext3 defaults 1 2<br>/dev/devpts /dev/pts devpts gid=5,mode=620 0 0<br>/dev/shm /dev/shm tmpfs defaults 0 0
<br>/dev/proc /proc proc defaults 0 0<br>/dev/sys /sys sysfs defaults 0 0<br>/dev/sda2 swap swap pri=1 0 0
<br>/dev/sdb2 swap swap pri=1 0 0<br>/dev/sdc2 swap swap pri=1 0 0<br>/dev/sdd1 /media/usbdisk ext2 pamconsole,exec,noauto,managed 0 0
<br>/dev/fd0 /media/floppy auto pamconsole,exec,noauto,utf8,managed 0 0<br>/dev/hda /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0<br><br>/dev/md0 is labeled "md0" and /dev/sda1 is labeled "/boot", although those names aren't used in /etc/fstab.
<br><br>I think the problem is that / is RAID5 and on /dev/md0, and if anaconda is going through all partitions in the system and running "e2label" on each of them, it'll see that /dev/sda3 and /dev/sdc3 return the same value: "md0", due to the RAID configuration. But, that doesn't jive with the wacky label printed in the dialog box (above). When it says "label" I assume its referring to the e2label, is that true? Is it possible to label a swap partition?
<br><br>Any help on how to get around this would be greatly appreciated. <br><span><br>Steve<br>
</span></blockquote></div><br>
</span></div></blockquote></div><br>