Red Hat Bugzilla – Bug 466008
Anaconda installer crashes before installing anything
Last modified: 2008-10-07 16:55:17 EDT
Description of problem:Attempting to install Fedora10 Beta on a Dell XPS 410 on the second internal hard drive using the partitions from a successful install of Fedora 10 Alpha. The installer never asks for network configuration, but otherwise proceeds normally right up until it starts the actual installation. At that point it crashes with an unhandled exception.
Version-Release number of selected component (if applicable): Fedora 10 Beta
How reproducible: Happens every time whether using install DVD or install CD's. Downloaded ISO's check sums are OK and the media tests are successfull
Steps to Reproduce:
1.Boot from installation media
2.Enter language, time zone, root password
3.Set up partitions of install using "custom" layout. /dev/sdb3 for /boot, /dev/sdb5 for /root, and /dev/sdb6 for /home. /dev/sdb1 is an NTFS patition for a Windows install, and /dev/sdb4 is extended.
4.Accept default install package list
5.Click on "continue" to begin actuall installation
Failure to install anything despite reformatting of selected partitions
Install of Fedora 10 Beta
Please attach the exception to this bug report so we have some idea what's going on. Thanks.
I've tried saving the report, but afterward, it's no where to be found.
Before you reboot, it's /tmp/anacdump.txt. You can switch over to tty2 and scp it to another machine if you have somewhere to copy it to. Or you could take a picture.
There's no way to get the report off the system. Like I said, anaconda never asks for NIC configuration. When I tried to save the report or scp it to another box on my LAN, anaconda does throw up a screen asking for network configuration but does not allow any input. If I try to manually get an interface up from tty2, I get no such device not matter what interface I use.
I did try to take a picture but 1) my camera records too much Moire effect to make the image readable, and 2) I'd need to upload several dozen pictures to capture the entire log.
We don't need the entire thing (most of the time) - just the first part with the file names and line numbers, and then the next line that has the actual error message.
Created attachment 319694 [details]
first few lines of the report
here's the first few lines
Created attachment 319695 [details]
and the next ten lines or so
Created attachment 319697 [details]
this is the last of it I was able to capture
This is the last screen I was able to process into readability
*** This bug has been marked as a duplicate of bug 465127 ***