Can't boot f2fs root file system after suse-module-tools update to version 16.0.39

English Install/Boot/Login
1

After this update:

> rpm-lc suse-module-tools
suse-module-tools:
* Thu Dec 14 2023 Martin Wilck <mwilck@suse.com>
- Update to version 16.0.39:
  * Add more modules to file system blacklist (jsc#PED-6167)
    Blacklisted filesystem modules that aren't officially supported
    by SUSE: f2fs, hfsplus, jfss2, kafs, ntfs3, orangefs, pstore, romfs, zonefs.
    As usual, the blacklist entries can be removed by running an
    explicit "modrobe $FS_MODULE" command.ere

the two systems I have that run from f2fs root partitions on USB flash drives fail to boot. What steps do I need to follow to get them booting again?

Thanks for any help,
Gene

2

@Gene_S as it says in the output modrobe $FS_MODULE where that would be f2fs there is more detail (as per the Mailing List post) here https://en.opensuse.org/SDB:FilesystemBlacklisting

3

Thanks for the link, but how do I get the module loaded before the boot process tries to mount the root file system?

Gene

4

@Gene_S edit grub at boot and arrow down to the linux/linuxefi line, press the ‘end’ key and add insimod=f2fs press F10 to boot. I suspect you might have to boot from an installation media and chroot into the system and correct there…

5

Thanks, that’s what I was looking for. The only help I found was to add modprobe f2fs to the command line. That didn’t work. :slight_smile:

Gene

6

It was easiest to chroot into the stick from my main system, then

1: touch /etc/modprobe.d/60-blacklist_fs-f2fs.conf to override the blacklist in /usr/lib/modprobe.d/60-blacklist_fs-f2fs.conf

2: delete the newest kernel, and reinstall it. That restored the old behavior.

Now to do the other stick.

Thanks again,

Gene