The following was filed automatically by anaconda: anaconda 11.5.0.26 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicelibs/swap.py", line 85, in swapon raise SwapError("swapon failed for '%s'" % device) File "/usr/lib/anaconda/storage/formats/swap.py", line 118, in setup swap.swapon(self.device, priority=self.priority) File "/usr/lib/anaconda/storage/__init__.py", line 1313, in turnOnSwap device.format.setup() File "/usr/lib/anaconda/packages.py", line 193, in turnOnFilesystems anaconda.id.storage.fsset.turnOnSwap(anaconda.intf) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() SwapError: swapon failed for '/dev/mapper/vg_virtual-lv_swap'
Created attachment 334668 [details] Attached traceback automatically from anaconda.
You have a lot of squashfs read errors in your exception log, which could very well be the cause of a problem like this. Could you try again with different boot media, making sure to verify both your download and burn (if you are booting off a CD)? Thanks.
Yes, I see those FS errors, so it is worth checking indeed. Re downloading http://download.fedora.redhat.com/pub/fedora/linux/development/x86_64/os/images/boot.iso produced the same error (as this is a VM, I am booting off the .iso without burning it to a CD). There is no md5 signature I can use to check that the .iso is not corrupted, let me know if I missed something.
Created attachment 334712 [details] Attached traceback automatically from anaconda.
Created attachment 334713 [details] /tmp/program.log
Created attachment 334792 [details] Attached traceback automatically from anaconda.
Seeing this while booting a KVM guest with a single disk. 1) I select: "Use entire disk" 2) Select Next and allow anaconda to partition the disk
I *think* this might be related to the squashfs zlib corruption (see bug#489698)? At least, I can't reproduce this problem anymore ... but hit bug#489698 instead.
*** This bug has been marked as a duplicate of bug 489698 ***
Created attachment 334873 [details] Attached traceback automatically from anaconda.
Created attachment 334889 [details] Attached traceback automatically from anaconda.
Created attachment 336210 [details] Attached traceback automatically from anaconda.
Created attachment 337133 [details] Attached traceback automatically from anaconda.
Created attachment 337836 [details] Attached traceback automatically from anaconda.
Created attachment 338651 [details] Attached traceback automatically from anaconda.
Created attachment 338862 [details] Attached traceback automatically from anaconda.
Created attachment 340566 [details] Attached traceback automatically from anaconda.
Created attachment 346119 [details] Attached traceback automatically from anaconda.