Closed dndx closed 7 years ago
Man this bug is a pain in my butt ;). I keep going back and forth. I'm going to try and revisit how I do this to be more robust, thanks for letting me know it's back again.
Just started using this script. This thread says that updated packages have been applied to the Rasbian mirrors recently. Though I still get the issue.
https://www.raspberrypi.org/forums/viewtopic.php?t=186769&p=1178842
it's just the options I use when building the image, I'm still trying to find a more sane method to deal with this, I thought taking the defaults for the HOST OS and the defaults from the IMAGE, and crossing them would work but seems something is wrong in that logic that I'm trying to figure out.
@dndx can you run this and post the results for me please
echo $(cat /etc/mke2fs.conf | grep "base_features = " | cut -d "=" -f2 | tr -d '[[:space:]]'),$(cat /etc/mke2fs.conf | grep -A3 "ext4 =" | grep "features = " | cut -d "=" -f2 | tr -d '[[:space:]]')
Believe this is fixed now
The build script started failing recently with the following message:
I am running Debian Jessie with all packages up to date.
I was able to fix this by manually editing
rootfs/etc/mke2fs.conf
and removemetadata_csum
from theext4
features line, then runcreateimg
manually, but it would be great if we can fix this in the build script as well.Looks like the
mk2fs
Jessie installs is too old to support this new file system option.