Red Hat Bugzilla – Bug 149401
Install fails on "install to empty space" installation
Last modified: 2007-11-30 17:11:00 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5)
Description of problem:
Attempted to install FC3 from released ISO's onto two different
computers (1 laptop, 1 tower) with the following characteristics:
1. Pre-existing NTFS partition on part of the drive
2. Empty space on the rest of the drive.
3. Drive spec: IDE, sizes > 10GB
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot FC3 disc 1 installation CD
2. Let Anaconda auto partition on empty space
3. Let Anaconda copy disk images over to drive.
Actual Results: Anaconda fails with message "There is an error in the
installation. You are probably out of disk space."
Expected Results: Successful install of FC3
Additional info: It appears to format the disk because I cannot go
back to the partition information once I get an error, but fails to
copy over the image(s).
Can you verify your media according to the instructions at
Yes. Media was successfully verified before installation started.
Can you provide the complete error you receive? Are you getting a
traceback after being told there's not enough space?
No as a matter of fact I don't. On the graphical install, I get a
dialog box with the message. If I switch to console where messages
appear during installation, it's a very brief "installation error"
with no other information.
A similar thing happens during text mode installation.
I might add that if I attempt to create the partitions and lvm in the
partition editor, I get the same message.
Exactly what's the partitioning on the drive before autopart and after?
I installed Win2k on a 2GB NTFS partition on a brand new laptop drive. - 18GB at
beginning was left empty.
Based on recollection: logical volume at beginning of 20GB drive that took up
about 18GB. It had a /boot, /(root) and Swap partitions.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
requested by Jams Antill
Is this better with F8 test 1?
I switched to debian long ago. Unless you want to test it yourself, I'd say
close the bug.