Traceback (innermost last): File "/usr/bin/anaconda", line 438, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 1030, in run rc = apply (step[1](), step[2]) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 507, in __call__ if todo.doInstall (): File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1480, in doInstall if self.method.systemMounted (self.fstab, self.instPath, self.hdList.selected()): File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/image.py", line 46, in systemMounted self.loopbackFile = mntPoint + fstab.filesystemSpace(mntPoint)[0][0] + \ File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/fstab.py", line 258, in filesystemSpace space.append((mntpoint, isys.fsSpaceAvailable(topMount + '/' + mntpoint))) File "/usr/lib/anaconda/isys.py", line 16, in fsSpaceAvailable return _isys.devSpaceFree(fsystem) SystemError: (2, 'No such file or directory') Local variables in innermost frame: fsystem: /mnt/sysimage//win ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
Created attachment 3569 [details] text dump file generated from RH7.0 setup in text mode
This bug only happens when I try to add an existing Win-Fat32 partion to fstab during the install procedure. I tried the install now without adding the mount point for the win partion and it worked fine.
Please verify brock.
Was this an install where you were installing Red Hat Linux to a FAT partition?
*** Bug 17869 has been marked as a duplicate of this bug. ***
*** Bug 17862 has been marked as a duplicate of this bug. ***
Related to bug 17846.
I installed in in a ext2 partition.
*** Bug 18032 has been marked as a duplicate of this bug. ***
I had the same problem. I have a 486 laptop and am doing an NFS custom install from a mounted RH 7.0 CD #2. The laptop had (and still has until formated) a FAT16 parition on it, but the install is being done completely over the network. I'm at a complete stand still till this is fixed. Any more info I can provide, please let me know.
I encountered this bug (or one indistinguishably similar to it). The system had one FAT32 partition [Win98] as /dev/hda1, which I assigned a mount point at installation time. Linux was installed to several other partitions [ext2] -- /dev/hda1 was involved in the installation only in that I set up a mount point for it. I used a custom installation [via CD] and opted to select individual packages. The installer then crashed after formatting the relevant filesystems but before displaying the "transferring installation image [...]" progress bar. I was able to perform a successful installation by EITHER not setting up a mount point for /dev/hda1 OR by not opting to select individual packages. I didn't try both together, but I assume that would work too.
Please verify Brent.
*** This bug has been marked as a duplicate of 18032 ***