Traceback (innermost last):
line 20, in run
rc = self.todo.doInstall ()
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1472, in
File "fstab.py", line 715, in mountFilesystems
raise SystemError, (errno, msg)
SystemError: (22, 'Invalid argument')
Local variables in innermost frame:
self: <fstab.GuiFstab instance at 8275ec8>
msg: Invalid argument
Please give the steps required to reproduce this issue.
I tried three times to install Redhat Linux 7. Once by Disk Druid, once by
fdisk since I have used this with Slackware, Redhat 5 and then Redhat 7. I
have tried to keep the install on a separate disk, sda... Unfortunately this
did not succede. However using your "automagic partitioning" the installation
was successfull. During the Druid install, the error sent to you produced
the "bug" please report to Redhat from firstname.lastname@example.org 2001-03-07 10:23:46 ------
- (actually bugzilla.redhat.com). However this error was requested by your
software and was sent to you. hda and hdb are Maxtor 7200 rpm DMA/66 drives
with Windows 2000 SR1. The sda1 is a Seagate SCSI drive.
What really bothers me is that the automatic LILO install clobbered the MBR on
hda1 and gets only to L in the L-I-L-O loader and hangs the system. I can boot
from a floppy. I haven't been able to clear the MBR using the Windows 2000
fixmbr and fixboot which I can usually do. Should I use a third party boot
manager? Can LILO not handle NTFS? Is this what the error means.
Please contact me with more questions.
Paul Wolfson, PhD
CEO of PWCC
(972) 492-1271 (fax)
So the error reported originally did NOT happen when you choose to use automatic
partitioning? When you chose to use automatic partitioning, is that when LILO
did not allow your system to reboot correctly?
I am confused what the actual failure mode is, so if you could explain a single
scenario from start to end that would really help out.
Closing due to inactivity - please reopen if you have anything to add to the bug