The following was filed automatically by anaconda:
anaconda 14.22 exception report
Traceback (most recent call first):
File "/usr/lib64/python2.7/site-packages/pyanaconda/backend.py", line 147, in mountInstallImage
File "/usr/lib64/python2.7/site-packages/pyanaconda/yuminstall.py", line 937, in run
if self.anaconda.backend.mountInstallImage(self.anaconda, stage2img):
File "/usr/lib64/python2.7/site-packages/pyanaconda/yuminstall.py", line 1730, in doInstall
rc = self.ayum.run(self.instLog, cb, anaconda.intf)
File "/usr/lib64/python2.7/site-packages/pyanaconda/backend.py", line 286, in doInstall
File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 212, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 131, in gotoNext
File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1190, in nextClicked
File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1211, in handleRenderCallback
IndexError: list index out of range
Created attachment 474049 [details]
Attached traceback automatically from anaconda.
*** This bug has been marked as a duplicate of bug 640893 ***
Do you still have this system available for data collection?
If so, go to tty2 (ctl+alt+f2) and run the following commands, then post the
full output to this bug report:
grep sysimage /proc/mounts
Created attachment 474092 [details]
Created attachment 474093 [details]
grep sysimage /proc/mounts
My system i'ts a raid software
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 sda2 sdd2 sdc2 sdb2
1463609280 blocks super 1.0 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 7/466 pages [28KB], 512KB chunk
md0 : active raid1 sda1 sdd1 sdc1 sdb1
513044 blocks super 1.0 [4/4] [UUUU]
bitmap: 0/8 pages [0KB], 32KB chunk
unused devices: <none>
md0 : /boot
md1 : lvm : /
I have found the solution.
I have modified the uuid in the /etc/fstab by the path of the device and the installation is ok
Yes, the problem is that you have quotation marks around the UUIDs in /etc/fstab.
I am proposing a patch that would fix this for Fedora 15.
This bug prevents us from properly parsing an /etc/fstab that quotes the values of UUIDs and/or labels in device specifications. The fix is very low-risk and could certainly be viewed as a strengthening of the algorithms.
the quote "" is incorrect in the fstab ?
the correct use is : UUID=29d54a1d-75ee-4ed3-8ab2-9fb00256bb23 ???
The quote is unnecessary. Your correct use example is correct.
I have added a patch to anaconda so that we can recognize quoted UUIDs and labels. I am trying to get it into Fedora 15.
Fixed for Fedora 15 in anaconda-15.22-1.
anaconda-15.22-1.fc15 has been submitted as an update for Fedora 15.
Discussed at 2011-03-11 blocker review meeting. This issue is fixed and available for testing in anaconda-15.22-1. The issue has been accepted as a beta blocker.
anaconda-15.22-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.