PDA

View Full Version : FC2 Can't transfer install image to hard drive


dedales
25th June 2004, 04:16 AM
System:

Dell XPS B1000r

PIII 1Ghz
512 Rambus memory
Western Digital WD1200BB 120GB
Nvidia Ti500
Soundblaster Live 5.1
Hauppauge PVR250
3Com 3c905tx

When I try to install FC2, regardless of Auto Partition or choose my own, I get an error that I'm out of disk space when it attempts to transfer the installation image to the hard drive. In fact, this happens with FC1, FC2, SuSE 9.1, RH9. I can however install WinXP or Lindows without issue.

I hunted through the Fedora FAQ, this Forum, and the Web and found/tried the following with no luck so far:

boot: linux allowcddma
boot: linux acpi=off apm=off
boot: linux allowcddma acpi=off apm=off
boot: linux text
boot: linux text [with all the above options]

Also tried a Win98 boot disk and when I use the fdisk utility it's as if it doesn't read the whole disk and won't allow me to use all the space available. I also did the fdisk /mbr.

I have run SuSE 9.0 and 9.1 previously on this box and haven't made any Hardware or BIOS changes. I'm no Newbie but I just don't get it!!!!

I've also downloaded the utilities from WDC and tried that. Unfortunately, they don't have any utilities for Linux. However, they're utility acts the same way. It will format and use the entire capacity if I format the disk NTFS but I can't seem to get the disk geometry to jive with Linux.

Thanks in advance for any help!
dedales@msn.com

gmontag
25th June 2004, 07:12 AM
I had this happen switching an had to delete and re add the suse partition because it was using reiserfs

dedales
25th June 2004, 07:30 AM

Maybe I didn't explain clearly, but there are no partitions to start with so there's nothing to delete. The entire problem is taking a supposed blank drive and creating the partitions in either the Automatic sizes or sizes that I choose for the installation.

Additionally, this is not a dual boot issue so please disregard anything that has to do with winblows. The only reason I mentioned it is because Win will use the whole drive but linux will not.

Thanks

dedales
26th June 2004, 06:38 AM
This was solved by writing zeros to the entire drive.