Red Hat Bugzilla – Bug 63821
RFE: Improve error handling when a fstype is specified for RAID partition
Last modified: 2007-04-18 12:42:10 EDT
Description of Problem:
Anaconda crashes on a kickstat
Version-Release number of selected component (if applicable):
bootnet.img from redhat-7.2
Steps to Reproduce:
Anaconda crashes and asks you to save anacdump.txt to floppy.
Should just work.
ks.cfg and anacdump attached.
Created attachment 54525 [details]
The anacdump.txt dump file
Created attachment 54526 [details]
The kickstart configuration file (ks.cfg)
Have you tried this update?
I found this change to my ks.cfg fix the problem.
part raid.1 --size 1 --grow --ondisk hda
part raid.2 --size 1 --grow --ondisk hdb
part swap --size 512 --ondisk hda
part swap --size 512 --ondisk hdb
raid / --fstype ext3 --level 1 --device md0 raid.1 raid.2
I moved the --fstype ext3 to the raid entry.
Jeremy do you have an idea what is going on here?
The partitions making up the software RAID can't be ext3, they have to be of
type software RAID, thus specifying that they should be ext3 is fouling
something up. Should probably be error checked better, but the modifications
you made actually fix the invalid kickstart config which you previously had.
Made changes so that anaconda won't let you do this in the future in CVS
Time tracking values updated
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.