initramfs-tools v0.146 branch introduced no issues affecting Reiser4 Software Format Release Number (SFRN) 4.0.2 until commit 0df1765e902e56d9698beacc1cc056f327ed58c2

Author: Ben Hutchings <benh@debian.org>
Date:   Tue Mar 25 23:58:06 2025 +0000

    Merge branch 'block-modules' into 'debian/latest'

    Filter block kernel modules by symbol regex from dracut

    See merge request kernel-team/initramfs-tools!149

Accordingly, for Debian Trixie new installations, initrams-tools v0.147 and upwards introduce booting failure on root '/' -formatted with Reiser4 SFRN 4.0.2 file system:

...

Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! PARTUUID=STUV-WXYZ does not exist.  Dropping to a shell!

 

BusyBox v1.37.0 (Debian 1:1.37.0-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

...

Notwithstanding, the reiser4 booting failure issue does not seem to affect upgrading from an existing Debian Bookworm with root '/' formatted in Reiser4 SFRN 4.0.2 file system.

Stripping away commit 0df1765e902e56d9698beacc1cc056f327ed58c2 from initramfs-tools v0.147 and v0.148.3, thus far, allows our Metztli Reiser4 / Debian Trixie / backports to boot normally again:

initramfs-tools_0.148.3+nmu1_all.deb
initramfs-tools-bin_0.148.3+nmu1_amd64.deb
initramfs-tools-core_0.148.3+nmu1_all.deb

i.e., Metztli Reiser4 hacked initramfs-tools v0.148.3+nmu1 fix reiser4 non-booting issue below:

(Please, use media controls -- to enlarge the video, for instance -- and/or right-select/click on the video, once it has begun playing, to open in another tab in larger dimensions.)