Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 109657

Summary: Ananconda fails to transfer install image to disk
Product: [Fedora] Fedora Reporter: dsswift
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: high    
Version: 1CC: mkanat
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:59:56 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:

Description dsswift 2003-11-10 18:59:16 UTC
Description of problem:
Whilst installing I get and error message saying an error ocurred 
transferring the install image to you hard drive. You are probably 
out of disk space. The partition is 6.5GB and anaconda has just 
formatted it.

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


How reproducible:
Every time

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Error message as above

Expected results:
Installation to continue

Additional info:

Comment 1 Jeremy Katz 2003-11-10 21:47:46 UTC
Does booting with 'linux allowcddma' help?

Comment 2 Max Kanat-Alexander 2003-11-11 07:04:51 UTC
'linux ide=nodma' usually resolves this problem. At least, with the
Intel D845 it does.

-M

Comment 3 dsswift 2003-11-11 15:51:45 UTC
Booting with 'linux allowcddma' appears to have fixed the problem

Comment 4 Dave Jones 2003-11-17 20:15:40 UTC

*** This bug has been marked as a duplicate of 109462 ***

Comment 5 Red Hat Bugzilla 2006-02-21 18:59:56 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.