On 2018-02-26, Marc Haber wrote: > the system in question is a Banana Pi, booting off an sd card. /boot is > already on the SATA disk, and was an ext4 file system when the issue > appeared. > > According to the availability of the ext4* commands, this u-boot should > be able to handle an ext4fs, I therefore used it as /boot. This has > worked until recently, when I installed the 4.15.6 kernel. .... > The (now gone) ext4fs had the following attributes: > Filesystem features: has_journal ext_attr resize_inode dir_index > filetype needs_recovery extent 64bit flex_bg sparse_super large_file > huge_file dir_nlink extra_isize metadata_csum > > Is is possible that u-boot won't handle some of the advanced ext4 > features?
I believe most recent versions *should* support ext4, though there were definitely bugs in older versions. It's possible some newer features now enabled by default would trigger issues like this, of course. I've been running numerous systems with ext4 for /boot for a while now... are you sure you're running the current version of u-boot? It requires manual installation and upgrading; the package does not handle this, see the instructions in /usr/share/doc/u-boot-sunxi/README.Debian* live well, vagrant
signature.asc
Description: PGP signature
