Red Hat Bugzilla – Bug 88315
Crash in Custom Install (Text)
Last modified: 2007-04-18 12:52:52 EDT
Description of problem:
I chose a custom install and deselected a number of groups (X, Gnome, Printing).
The box then comes up telling me that a log file will be stored in
/tmp/install.log, and I should press OK to continue. After pressing OK, it then
informs me that it is formatting /.
Right after that I get a python trace, something about no match in an RPM header
or in comps. I tried to save the trace to floppy as requested, but that didn't
work either :( Half the trace was saved but it was incomplete. I guess I'll
attach that in case it helps.
I'm now just installing a "workstation" on a larger drive and this seems to be
working so far.
Created attachment 91016 [details]
Partial Error Trace
Unfortunately, the complete trace was not saved before the installer shut down
and told me i could power off.
Hopefully this will give you enough of a clue to figure out the problem.
What install source were you using (FTP, NFS, CDROM...)?
It looks like either a bad CD or a corrupt network transfer, depending.
I'm using a CD install. I scanned it and it comes back pass. I have also used
the same set of CD's to upgrade two other machines and install a workstation on
I reproduced the error, so I guess i'll just type in the trace by hand.
Starting after the last complete line:
File "/usr/lib/anaconda/image.py", line 50 in mergeFullHeaders
File "/usr/lib/anaconda/comps.py", line 180 in mergeFullHeaders
rpm.mergeHeaderListFromFD(self.hdlist, fd, 1000004)
error: match tag missing in new header
I'll leave it in it's current state for as long as possible in case you have any
more questions or you can tell me what to do with the Debug button. Otherwise
it is easy to reproduce.
This problem is occurring the the text installer. I put it in the summary, but
didn't make it clear in the bug report.
I have been attempting to install this on a 1.2 GB hard drive. There is not
enough room to copy the CD image to the hard drive and then do the install.
I've noticed that this happened on my other machines with larger drives.
I repeated the steps I used to cause this problem originally, but with a larger
hard drive. The problem did not reoccur. It is a bit annoying that I can't
install onto small hard drives, but I can probably live with it.
What type of partitioning were you using on the 1.2G drive? I've done minimal
installs on that size drive before w/o problems some I'm curious what was
different in your case.
It was a month ago, but I think I just set myself up to have swap and /.
I don't think this was a totally minimal install. I think I had some
development tools selected along with the base installation. I seem to recall
that the size of the installation was going to be a bit more than 700 MB.
There are some assumptions about a minimal amount of space being available for
some temporary files, but the space estimate we give is pretty conservative and
should take that into account.
If you can come up with a reproducible case I'd be happy to investigate further.
Closing due to inactivity - please reopen if you have additional information to add.