You need to resize the filesystem in the (now bigger) /dev/mmcblk0p66 (which is split-off from /dev/mmcblk0p5).
But why do you like to add the remains space to the root filesystem in first place? As rootfs overlay is re-created ever time you upgrade the system imho it doesn’t make sense to keep anything big there anyway. It’s much better to create additional volumes, e.g. using uvol or by simply creating one large additional partition.
What command should I use to resize the filesystem? Because resizefs.f2fs doesn’t work…
Do I also need to modify the /dev/mmcblk0p66 partition? I don’t clearly understand what I should do. Some tutorials explain differently and I can’t figure out what actually applies to the R3 model.
On the R3 the /dev/mmcblk0p66 device is automatically mapped as the remaining space on /dev/mmcblk0p5 after parsing the uImage.FIT for kernel, device tree and read-only squashfs rootfs (squashfs filesystem is mapped as /dev/mmcblk0p65). So those p65 and p66 partitions are not actual GPT partitions but rather p65 is the filesystem sub-image of the uImage.FIT stored in p5 and p66 is the remaining space on p5 after the uImage.FIT.
Hence you only need to edit the size of /dev/mmcblk0p5, then reboot, then use resizefs.f2fs with /dev/mmcblk0p66 which will automatically reflect the changed size of the /dev/mmcblk0p5 partition after reboot.
For extroot to work you need to install block-mount (or better to deal also with removable media: install blockd).
In general I’d still recommend you to install uvol which allows you to manage additional storage volumes more easily. In order to automatically allocate all unused storage on the device used to boot and store the root filesystem you can install the autopart package.
Sidenote: The first part of your post is in French and you should write in English here.
For others :
Boot in recovery or on nand (jumpers in H L H L [NAND] or L H H L [eMMC])
Install “parted” (“opkg install parted”)
Use parted to resize partitions 3 and 4 to the right size (that the sectors follow each other because there are empty spaces between the partitions).
Resize partition 5, the system will indicate that the disk (GPT) does not have its maximum size, “fix” and resize the partition to the maximum of its value (“unit s” [sectors], “print free” [show free space after last partition], “resizepart” then enter partition number , ending size [15269854s] in my case).
Then quit and install “autopart” (“opkg install autopart”), I don’t know what is used by autopart at the end, but it takes care of refreshing the partition size which will be at the correct dimension after reboot.
You cannot resize /dev/mmcblk0p66 because that’s not really a partition but rather just the remaining space left after the uImage.FIT on /dev/mmcblk0p5, I have explained this in detail just a few posts above.
Sorry, I may not have been fully awake when replying to your post. The partition table looks good, you have successful edited and expanded mmcblk0p5. To use resize.f2fs you need to boot into the recovery firmware or boot from SPI-NAND, so that the partition will not be in use while you are trying to resize it.