Description of problem: An exception occured during installation right after image intalled to HD and (I think) right before RPMs get transfer from the disks. Version-Release number of selected component (if applicable): How reproducible: Happens everytime Steps to Reproduce: 1. Full Install of FC2 2. 3. Actual results: exception occurred Expected results: no exceptions Additional info:
Created attachment 100394 [details] anaconda dump file
I get exactly the same error/problem with x86_64 FC2 final. As the person above mentioned, it happens just after the image has been transferred. Problem does not occur with 32bit FC2. My system: K8T800 MSI Neo-FISR AMD64 3000+ IDE disk attached to IDE for WIN SATA disk (200gb Maxtor) on VIA controller used for FC2 installation PS/2 keyboard (usb would cause another crash) Mouse USB ATI Radeon 9600, ASUS Regards, Ben
The only system commonality my sys has with Mr. Haines is that I have a 200 GB Maxtor SATA The other components are: ASUS SK8V (VIA K8T800) mobo w/AMD64 FX-53 PS/2 mouse and KB GeForce FX5700
The problem is with the SATA I replace the SATA HD with an IDE HD and the installation worked.
Hi Don, thanks for the information, did you try using the Promise controller instead of the VIA one? I will give it a try next week as I only have the SATA drive to play with. Regards, Ben
Good News! I have narrowed the problem down (at least on my sys). First, I have partioned the SATA HD using disk druid as: hde1: 10 GB "/" ext3 hde2: 5 GB "/usr/local/" ext3 hde3: 1024 MB swap hde4: remainder of 200 GB "/home" ext3 I can get it to work properly (i.e. install) on both the VIA SATA or the Promise SATA if I do not select "Format" for the "/home" partition. (Basically you format it the first time which bombs the install and then start the install again and don't format it the 2nd time)
Hi Don, I know its been a while, but have you had any further success? Perhaps an alternative solution to the above? Many thanks, Ben
*** This bug has been marked as a duplicate of 119447 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.