My system is as follows: PII 350, 96MB RAM, 8G IDE HD with Win98 installed
(No additional partitions). I have over 5GB free on the HD.
I am new to linux and I am attempting the partitionless install; however,
I can't get past the disk druid partition phase. When I select my FAT
partition as root, I get the warning message ("You have selected a DOS FAT
style partition..."). I hit OK to confirm, this leaves the "next" button
ungrayed. When I hit next, the installer throws an exception.
ERRATA: I have already tried downloading the installer update from the
errata section, it did NOT work. I wrote the image to a floppy and
typed "linux updates" at the boot prompt, and inserted the update disk
when prompted. I see the message "reading anaconda updates" before the
install begins, but it makes no apparent difference, the installer still
crashes at the exact same spot. I really want to get started with this OS;
any help would be greatly appreciated.
Here's my trace:
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/gui.py", line 336, in run
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 678, in run
File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop
File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__
ret = apply(self.func, a)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 428, in
self.setScreen (self.currentScreen, self.nextClicked)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 466, in
new_screen = screen.getScreen ()
7.0.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 133, in getScreen
avail = apply(isys.spaceAvailable, self.todo.fstab.getRootDevice())
File "/usr/lib/anaconda/isys.py", line 10, in spaceAvailable
mount(device, "/mnt/space", fstype = fsystem)
File "/usr/lib/anaconda/isys.py", line 99, in mount
rc = _isys.mount(fstype, device, location, readOnly)
SystemError: (22, 'Invalid argument')
Local variables in innermost frame:
Please give us the exact sequence of steps required to reproduce this issue.