Bug 163978

Summary: Installer crashes when reading the packet list
Product: [Fedora] Fedora Reporter: Blacklotus <darkblacklotus>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CANTFIX QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-21 21:10:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Anaconda Crashlog none

Description Blacklotus 2005-07-22 16:09:51 UTC 
Description of problem:
I am trying to install Fedora Core 4 on my AMD Athlon 800 Mhz, 384 MB RAM,
Geforce 2 TI with an FIC SD11 Mainboard. Anaconda always crashes when reading
the packets. In graphical an text mode. The media check reports no problems. In
Fedora Core 3 Anaconda worked without a problem.


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


How reproducible:
Every time.

Steps to Reproduce:
1. Boot the DVD
2. Start the installation
3. work until anaconda reads the packets
4. It crashs
  
Actual results:
Anaconda show the debug log and I have to reboot the PC


Expected results:
Normal you can select the Packets fot the installation


Additional info:
See the attachment
Comment 1 Blacklotus 2005-07-22 16:09:51 UTC 
Created attachment 117070 [details]
Anaconda Crashlog
Comment 2 Jeremy Katz 2005-07-26 04:14:27 UTC 
There are read errors on your drive.  Can you verify your media according to the
instructions at http://rhlinux.redhat.com/anaconda/mediacheck.html?
Comment 3 Jeremy Katz 2005-09-21 21:10:45 UTC 
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.