Bug 112161 - Installer exited abnormally
Summary: Installer exited abnormally
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-15 15:39 UTC by Chris Smith
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-12-16 17:56:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Smith 2003-12-15 15:39:06 UTC
Description of problem:

Dual Athlon MP 2800+ on Tyan Tiger S2466 m/b fails to install Fedora 
Core 1.0

Version-Release number of selected component (if applicable):


How reproducible:

Every time!


Steps to Reproduce:
1. Boot from CD
2. Hit Enter at prompt
3.
  
Actual results:

Eventually console message 'Installer exited abnormally' appears


Expected results:

Fedora Core installation


Additional info:

Sometimes the following console messages appear before the X windows 
system starts:

.
.
.
running install...
running /sbin/loader
error 2 reading header: cpio: Bad magic (sic!)

gzlib: stdin: invalid compressed data--format violated
error -2147483630 reading header: cpio: read failed - Success (what?)

If I try installing over the network from an NFS image, the kernel pa 
nics when the driver disk has been read.

Comment 1 Jeremy Katz 2003-12-16 17:56:10 UTC
The looks like bad boot media to me.  Please verify your installation
media and if that doesn't work, check your hardware with memtest86. 
This is sort of "can't happen" failures.

Comment 2 Chris Smith 2003-12-17 13:52:01 UTC
Jeremy

I forgot to include the fact that I had already checked the media and 
run the memtest86 for one complete pass without error (takes forever 
with 2GB!). Tech support at Tyan have come up with a query about the 
memory we are using. They say it isn't in their supported list, so we 
are about to swap it out for a supported type. But that doesn't say 
much for memtest86 does it?

Chris


Note You need to log in before you can comment on or make changes to this bug.