The first partition (within a block of freespace) that anaconda creates does not get properly aligned. For example on an empty disk anaconda starts the first partition at sector 63 rather then at sector 2048. As this is a regression compared to anaconda from the alpha snapshots (the alpha itself actually has the bug), and is this seriously impacts performance on new 4k sector disks (which are in the stores now). I'm proposing this as an F13Blocker.
I concur with Martin's results - the IMG patch works fine on the Advanced Foramt drives to align to 4K (or multiples of 4K) boundaries. The first partition start point of 63 on the drive with offset +1 jumper installed is unexpected. Nothing wrong with it as it is aligned to 4K, but odd. To reiterate the earlier findings, without the patch, the default installation on FC13 alpha fails with an exception - install will not complete. This should be addressed by the 1.41.11 e2fstools which allow the bypassing of the misalignment question but for now, the default installation fails. Regards Steve
*** Bug 573628 has been marked as a duplicate of this bug. ***
The patch for this has been added to the f13-branch of anaconda, the next anaconda version: anaconda-13.37-1, will contain the fix for this. Moving to modified.
anaconda-13.37-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.37-1.fc13
anaconda-13.37-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.