What is the networking information you gave the installer?

Any other information about how your network is setup would be helpful.

I originally attempted to set up Linux for DHCP. We have a medium-sized
corporate Windows/PC network using DHCP for IP assignment. When I used a fixed
IP address during my Linux setup, I was able to successfully finish
the installation.

What type of DHCP server are you using?

We are using the DHCP server that comes with NT 4.0 Server.

This is probably a issue with pump, reassigning.

When this failed, what media were you installing from, CDROM?

It didn't work for me. (the static IP thing).
Anyway, I've heard about this intergrated networkcard problem with IBM Netfinity
M20 servers,
I gonna try that out as we speak.

This error occurred when installing from a HD on either a 16 bit FAT prtition 
or on a Native Linux partition.

I was installing it from CDROM, burned the ISO on to a blank cd, then booted up 
etc.

I have a very similar error message but it's different line. Especially the line "fsystem: /mnt/sysimage//mnt/extra", I try to create dos mount point at 
"/mnt/extra" while install. However, I try to install again and create only root mount point ("/") but don't create any mount points. It works fine. No error 
message at all.

Traceback (innermost last):
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run
    rc = self.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//mnt/extra

ToDo object:
(itodo
ToDo
p1
(dp2
S'method'
p3
(iimage
CdromInstallMethod
p4
(dp5
S'progressWindow'
p6

<failed>

I am not sure if this will help you at all but I am seeing something similiar 
to this.  Here is the traceback that I get :

Traceback (innermost last):
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py", line 20, 
in run
rc = self.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//dos

ToDo object:
(itodo
ToDo
p1
(dp2
S'method'
p3
(iimage
CdromInstallMethod
p4
(dp5
S'progressWindow'
p6

<failed>

Thanks,

Chad Dunlap
cld

I'm getting something similar:

Traceback (innermost last):
 File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py", line 20,
in run
  rc = self.todo.doInstall ()
 File "/tmp/updates/todo.py", line 1491, in doInstall
  self.fstab.mountFilesystems (self.instPath)
 File "/tmp/updates/fstab.py", line 715, in mountFilesystems
  raise SystemError, (errno, msg)
SystemError: (22, 'Invalid argument')

I'm using the anaconda update disk (the first one issued for 7.0), installing
from CD (an official boxed-set CD, even, ooh, ahh).

Never mind my comments; I dropped into the Python debugger, figured out how to
print some variables, and realized what the problem was.  User error, sort of: I
had a partition from a previous install that was formatted as ISO-9660, and
naturally mounting it as ext2 didn't work.  I can rerun and have it formatted
(there's nothing on there I need; it's a staging area).  The installer ought to
try more filesystem types on partitions it wasn't asked to install, though.

The original bug reporter has rea

Closing due to inactivity.