[SOLVED] fsck checks f2fs partition at boot every time after an update.

[haughty widget]

Today, after a successful update, I rebooted my system and since then fcsk would just check and try to fix a "reported corruption" in my root partition every time I boot up my system. That update also had the new linux-zen kernel version (6.9.1), but either that isn't the source of the problem or whatever it did isn't reversible. Here's some info:

System

Kernel: linux-zen 6.8.9 (pre-update), linux-zen 6.9.1 (post-update)
File system: f2fs
(you can find other info below in the fstab/boot.log)

What I already tried

• Ran mkinitcpio -P. No change.
• Used a different kernel (linux). No change.
• Downgraded to the previous version (6.8.9). No change.
• Ran fsck /dev/nvme0n1p2 from a Live boot image. Same result as on system boot (exit code: 0).
• Set fs_passno to 0 in /etc/fstab. No change.
• Prepend nofail to fs_mntops. No change.

Any kind of help will be very appreciated cause I don't know what to do other than reinstalling Arch. This isn't a severe problem as it doesn't impact the system's integrity, but it still added a minute to the boot time, where before it took mere seconds to boot.

here's the boot.log

here's the fstab

here's the mkinitcpio.conf

[haughty widget]

As I also said earlier, running fsck /dev/nvme0n1p2 from a Live environment will give the same result with exit code 0.

[haughty widget]

The issue has been solved on the Archlinux forums.

TL;DR I just had to reboot twice after downgrading to 6.8.9, my bad lol.