fsck: Get a newer version of e2fsck

[TheSnowfield]

What happened?

This issue is just a cheat sheet for people creating the old Armbian image who encountered this problem

The problem was caused by the host using a newer mke2fs(>=1.47) to create the root filesystem.
however, Armbian packed the old version e2fsck(<=1.46) into the initramfs, which is not supported EXT4_FEATURE_COMPAT_ORPHAN_FILE. It can't check the newer filesystem, so hang the kernel boot.

It happens on the new systems (bullseye bookworm...) build the old Armbian image with e2fsprogs package version >=1.47. I confirmed this problem on the branch v23.02 (maybe the older version too?).

2024.11.14 update:
To deal with this problem temporarily, manually add these lines in the lib/functions/image/partitioning.sh,
to remove orphan_file flag, see 1ff783d, thanks to @rpardini figure it out.

Alternative, upgrade the e2fsck for your initrd

Add the hook script under `packages/bsp/common/etc/initramfs-tools/hooks/upgrade-e2fsck.sh`, ensure the script file has execute permission: "chmod +x upgrade-e2fsck.sh"

#!/bin/sh
# Upgrade e2fsck for initrd
#

curl http://ftp.us.debian.org/debian/pool/main/e/e2fsprogs/e2fsck-static_1.47.1-1+b1_armhf.deb \
     -o /tmp/e2fsck-static_1.47.1-1+b1_armhf.deb

dpkg -x /tmp/e2fsck-static_1.47.1-1+b1_armhf.deb \
     /tmp/e2fsck-static

cp /tmp/e2fsck-static/usr/sbin/e2fsck.static \
   "${DESTDIR}"/sbin/e2fsck

rm -rf /tmp/e2fsck-static

exit 0

and then, re-build the image file, and flash it to the board.

ref: https://packages.debian.org/en/sid/armhf/e2fsck-static
ref: #988

[github-actions]

Jira ticket: AR-2532

[EvilOlaf]

This branch is no longer supported. Please retry v24.11.

[TheSnowfield]

This branch is no longer supported. Please retry v24.11.

Oh sure. I'm creating the old Armbian image on a newer system. I created this issue for people to save their day.
So I closed it. :)

[rpardini]

No. See 1ff783d