Red Hat Bugzilla – Bug 197844
clean FC5 install to Poweredge 2400 w/ PERC2/DC throws exception after formating /boot directory
Last modified: 2007-11-30 17:11:36 EST
Description of problem:
Doing a clean install of FC5 where /(ext)3, /boot(ext3) and SWAP were going to
the first disk of sda. All other 5 disks were supposed to become a RAID6
software raid. PERC2/DC is set to MASSSTORAGE. Just before it starts
installing packages it threw an exception that I've caught on a floppy.
Version-Release number of selected component (if applicable):
Attempting second install now.
Steps to Reproduce:
Install fails, throws exception, then reboots.
Installs cleanly, then reboots.
Created attachment 132019 [details]
dump from anaconda
Just reproduced the error. It formatted all the filesystems, transferred the
image to the hard disk for the install and then throws an exception again. I've
got a copy of it as well if anyone wants it.
In the Exception details it says
Traceback (most recent call last):
File "/usr/lib/anaconda/gui.py", line 1253, in handleRenderCallback
File "/usr/lib/anaconda/iw/progress_gui.py", line 245, in renderCallback
File "/usr/lib/anaconda/gui.py", line 951, in nextClicked
File "/usr/lib/anaconda/dispatch.py", line 146, in gotoNext
File "/usr/lib/anaconda/dispatch.py", line 217, in moveStep
rc = apply(func, self.bindArgs(args))
File "/usr/lib/anaconda/backend.py", line 156, in doPreInstall
backend.doPreInstall(intf, id, instPath, dir)
File "/usr/lib/anaconda/yuminstall.py", line 923, in doPreInstall
File "/usr/lib/anaconda/fsset.py", line 1213, in write
cf = self.mdadmConf()
File "/usr/lib/anaconda/fsset.py", line 1202, in mdadmConf
cf = cf + ent.device.mdadmLine()
File "/usr/lib/anaconda/fsset.py", line 2029, in mdadmLine
return "ARRAY %s/%s level=%s num-devices=%d uuid=%s\n" \
IndexError: list index out of range
Caused by RAID6 -- fixed in CVS
I'm new to logging a bug. So, how would I now try to install this again?
Install from source RPMs, or download a "test" ISO from
I'm fairly experienced at unix, but since this is happening upon install, I'm
a bit baffled as to how I should continue. I sure don't want to wait until
October for the full release of FC6.