Bug 143380

Summary: Anacoda crashes on reloading onto a dual boot machine
Product: [Fedora] Fedora Reporter: Matthew Grimes <matthew.grimes>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: 3CC: matthew.grimes, nobody+pnasrat
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-20 18:19:06 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
When failure occured it said to copy to floppy
none
Second occurance of crash report none

Description Matthew Grimes 2004-12-20 03:52:22 UTC 
Description of problem:
I had sucessfully installed Fedora core 3 on a new drive of my dual 
boot windows xp box, did an up2date. I deleted the wrong thing as a 
newbie and have been tring to reinstall FC3.  Anaconda crashes as it 
is about to copy files off of the cd onto the hard drive.  I have a 
floppy dump file

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


How reproducible:
Happens every time I try to reinstall FC3

Steps to Reproduce:
1. Delete partiions on drive
2. Boot to CD and start install process
3.
  
Actual results:
I follow all of install directions and install crashes before loading 
OS.

Expected results:
Create new partitions and load software

Additional info:

I found bug problems of people upgrading and did not understand the 
solutions presented for a similar but different problem.
Comment 1 Matthew Grimes 2004-12-20 03:57:07 UTC 
Created attachment 108873 [details]
When failure occured it said to copy to floppy
Comment 2 Matthew Grimes 2004-12-20 03:58:54 UTC 
Created attachment 108874 [details]
Second occurance of crash report
Comment 3 Jeremy Katz 2004-12-20 18:19:06 UTC 
This is caused by partial volume groups being left on the disk.  Some
changes have gone into CVS to fix this, but you can work around by
naming your volume something other than VolGroup00 on the install.