I was trying to install F18 using preupgrade (over F17) so should be using a recent anaconda. I searched for similar bugs and found the one closed, I doubt it's the same problem as I am seeing this in the preupgrade anaconda. The backtrace is shown as soon as anaconda starts and displays the choice of network devices, perhaps after a 1 second delay - certainly not enough to set up the network. After the backtrace is dismissed it seems impossible to continue and anaconda is stuck between rebooting or showing the same backtrace again. So it is impossible to use preupgrade. I have a bios boot partition that works for F17 so the related comments in the cloned bug probably don't apply. parted shows: 1 1049kB 2097kB 1049kB bios_grub 2 2097kB 526MB 524MB ext4 ext4 boot 3 526MB 37.1GB 36.6GB ext4 4 37.1GB 42.2GB 5067MB linux-swap(v1) 5 42.2GB 60.0GB 17.9GB ext4 The backtrace shows (transcribed from a cellphone photo): in _setupDevice log.info("setting up device %s and mounting on %s" % (device.name in _setUpMedia self._setupDevice I will attach the photo later. +++ This bug was initially created as a clone of Bug #752235 +++ [...] --- Additional comment from clumens on 2012-10-23 15:55:02 EDT --- This should be fixed in F18 versions of anaconda, I do believe.
Created attachment 637729 [details] photo of backtrace
I am seeing the same thing here. On the logging console I found a line stating that /dev/sda2 (which is /, only /home is on a separate volume) could not be mounted to /mnt/sysimage the reason being that it is mounted to /run/install/repo already. Looks somewhat similar to bug 810391.
preupgrade is not a supported way to do upgrades in F18. We will be using a completly separate process that does not involve anaconda. If you can reproduce this doing a fresh install, feel free to reopen this bug.