Anaconda crashes and burns when arriving at the hard drive partitioning when
doing a hard drive install from my external USB/firewire drive (250 GB maxtor).
Created attachment 94767 [details]
debug file saved to floppy by anaconda
please make it possible to save to something else soon, floppies are hard to
Fixed in CVS.
The dump is also in /tmp/anacdump.txt and you have scp to be able to get it off
One of my systems did not even get to the partitioning stage.
Attempted to install from an external 120GB drive in a USB2.0 enclosure to a
SCSI hard drive on an IBM ServeRAID controller. Anaconda crashed just after it
started up X.
Probing for video card: ATI Mach64 3D Rage IIC
Probing for monitor type: Unknown monitor
Probing for mouse type: Generic - Wheel Mouse (PS/2)
Attempting to start native X server
Waiting for X server to start...log located in /tmp/X.log
1...2...3...4...5.... X server started successfully.
Traceback (most recent call last):
File "/usr/bin/anaconda", line 996, in ?
File "/usr/bin/anaconda/harddrive.py", line 208, in __init__
File "/usr/bin/anaconda/harddrive.py", line 89, in mountDirectory
readOnly = 1);
File "/usr/bin/anaconda/isys.py", line 162, in mount
rc = _isys.mount(fstype, device, location, readOnly, bindMount, remount)
SystemError: (22, 'Invalid argument')
install exited abnormally
I suspect that this may be because usb-storage is treated as a scsi
controller. I booted from floppy, it loaded usb-storage, I selected language
and keyboard layout, it loaded isp and usb-storage (again), I selected loading
files from hard drive (/dev/sda1). Given that my SCSI hard drive (internal)
should be sda after the O/S is installed having the USB drive load first will
be a problem.
I then moved the USB drive to a non-SCSI system and got the same results as
Trond - anaconda crashed at partitioning stage.
test3 gets past partitioning stage on my non-SCSI system but fails during
install of openoffice (claiming corrupted image or out of space [certainly not
that - I doubled disk allocation and got same error]). Need to do more testing
to see what is happening - will try from IDE instead of USB to confirm not USB
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product. If you have further information, feel free to
add to the report and reopen.