Dear
@fehlix,
I have deactivated the saving (remember) of the last boot choice.
I no longer get the "sparse..." message.
When I do a sudo update-grub, everything works fine with an f2fs partition.
Code: Select all
wallon@msi:~
$ sudo update-grub
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found linux image: /boot/vmlinuz-6.1.0-10-amd64
Found initrd image: /boot/initrd.img-6.1.0-10-amd64
done
I know that MX boot-repair doesn't work with f2fs.
Does this come from Debian or MX Linux?
It's hard to check because with Debian, installation on an f2fs partition is not possible.
For your information, I've done a lot of speed tests on this very good Samsung 400MB/s USB 3.1 stick with Gnome-disk.
With Windows exfat average for reading 400 MB/s
With linux f2fs formatting average for reading 390 MB/s
With linux ext4 formatting average for reading 280 MB/s
When writing, I also found the same differences between the 3 formats. But ext4 formatting is bad because there are peaks at zero due to journaling.
There's an option missing in the MX Installer; it should be possible to remove journaling from an ext4 partition during installation.
Wouldn't it be possible at the end of the installation to deactivate journaling and remove the journal from the ext4 partition?
Kind regards,
Wallon