Most important is this link
https://gitlab.gnome.org/GNOME/gparted/-/issues/311
Gparted developer says the bug is not in Gparted but in f2fs-tools
The source of the error was:
the file system was not unmounted
F2FS file system check tool not cleaning everything and requiring
additional mount and unmount
From your above supplied output fsck.f2fs reports the file system as
sudden-power-off == not cleanly unmounted. But fsck doesn't fix this
state.
lubuntu@lubuntu:~$ sudo fsck.f2fs -f /dev/sda6
...
Info: checkpoint state = 42 : crc orphan_inodes sudden-power-off
For every other file system a successful check fully cleans the file
system of all faults. But for F2FS it doesn't clear the "I need log
replaying". Only the Linux kernel f2fs code does that on mount.
This is not GParted's fault.
Most important is this link
https://gitlab.gnome.org/GNOME/gparted/-/issues/311
Gparted developer says the bug is not in Gparted but in f2fs-tools
The source of the error was:
the file system was not unmounted
F2FS file system check tool not cleaning everything and requiring
additional mount and unmount
From your above supplied output fsck.f2fs reports the file system as
sudden-power-off == not cleanly unmounted. But fsck doesn't fix this
state.
lubuntu@lubuntu:~$ sudo fsck.f2fs -f /dev/sda6
...
Info: checkpoint state = 42 : crc orphan_inodes sudden-power-off
For every other file system a successful check fully cleans the file
system of all faults. But for F2FS it doesn't clear the "I need log
replaying". Only the Linux kernel f2fs code does that on mount.
This is not GParted's fault.