The issue has been fixed upstream with improvements to ext4 support in u-boot 2016.11,
in Fedora I backported these fixes to uboot-tools-2016.09.01-2.fc25 and they've now
been verified and that release is now stable so we should be good to revert the ext3
partition workaround for F-25 GA.
With e2fsprogs after 1.43 the 64bit and metadata_csum features are
enabled by default. These features are not currently supported in
u-boot and the 64bit feature introduces changes such that it cannot
be read by implementations that do not support it. U-Boot does not
support the functionality and hence now won't mount it just in case
it corrupts the filesystem, which is a reasonable response, this how
ever stops us from booting when we have a ext4 /boot file system
which means basically we end up with a pot plant. Go back to using
ext3 for the time being as the mkfs.ext3 option doesn't enable these
features and we get booting systems!! YAY \o/
initail-setup.service now handles running both the gui mode and text
mode running of initial-setup so just enable the one service and no
longer do any special handling rhbz#1296495
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
remove vfat kickstarts, we are going to use u-boot in raw space
without needing two sets of images with different partitioning we
can remove the seperate partitioning snippets and put the
partitioning in base.
Peter Robinson
Dennis Gilmore