Phil Schaffner wrote:
On Wed, 2004-06-09 at 06:52 -0500, Alexander Dalloz wrote:
I've just spent quite a while trying to get FC2 installed and in the end had to revert to FC1. The install logs show that some packages installed fine but others didn't. Doing an "everything" install, the first 1 to fail is glibc and the log looks like
Installing glibc-2.3.2-101.i686. error: %post(glibc-2.3.2-101) scriptlet failed, exit status 115
I ended up with a system with no glibc and no kernel!
I would say it is a hardware problem. Check your RAM - run memtest86. If you overclocked your system in any way, undo it.
Alexander
Good advice. If that doesn't work...
I don't think it's a disk space problem as the log shows lots of other packages that do install, however I only had about 400M for / (with /var,
/usr/ and /home their own partitions) and 100M for /boot, I would have
thought this was enough...
I was using LVM, which caused me lots of trouble. In fact I got 2 stack
traces from Anaconda but I didn't have a floppy to save them on.
LVM has been problematic:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119975 http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125405
Either of these sound relevant?
I'd start fresh and try letting anaconda partition with a workstation or
server install. Having separate /, /var, and /usr can cause problems
with running out of space even when there is free space available on the
other partitions, as well as possibly being less efficient than a
single / if they are all on the same physical disk. Usually just
have /, /boot, and /home (preferably on a separate physical disk) with a
large separate chunk of shared storage mounted elsewhere - optional.
A bit OT, but your partitioning may lead to other problems.
/var holds the databases, web site, mail, dns, news, and much other very important data for your servers. I ALWAYS put /var on a separate partition so the data it contains can be easily recovered during a restore/reload, just as the data in /home.
Phil
