Bug 449889 - Exception in Anaconda during F9 Live CD install to hard drive
Summary: Exception in Anaconda during F9 Live CD install to hard drive
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 9
Hardware: i686
OS: Linux
low
low
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-04 06:20 UTC by Bill Hensley
Modified: 2008-07-20 18:20 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-06-04 16:03:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Detailed bug report from Anaconda. (25.36 KB, text/plain)
2008-06-04 06:20 UTC, Bill Hensley
no flags Details

Description Bill Hensley 2008-06-04 06:20:07 UTC
Description of problem:  During installation of Fedora 9 Live CD, in "copying
live image to hard drive", and Exception Occured.  The text is attached.


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


How reproducible:  Several times


Steps to Reproduce:
1.  Boot off Live CD
2.  Follow prompts for English, North Dakota/Center, automatic partition layout
with review
3.
  
Actual results:


Expected results:


Additional info:  Dell Latitude D630, dual processors, Centrino, 2 GB of memory,
120GB hard drive with two partitions, first 30GB with XP on it.

Comment 1 Bill Hensley 2008-06-04 06:20:07 UTC
Created attachment 308324 [details]
Detailed bug report from Anaconda.

Comment 2 Chris Lumens 2008-06-04 16:03:12 UTC
This looks like bad media to me.  Did you run media check to verify your
installation media?  Regardless, we have modified anaconda in Rawhide to catch
this exception and offer a retry/reboot option.

Comment 3 Bill Hensley 2008-07-20 18:20:48 UTC
Resolution:  I downloaded the 64bit version of Fedora 9.  It installed the first
time with no problems and has been operational with daily heavy use for more
than a month.  

So, I would say that there is no bug, just another user education issue :).


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