But in my sad experience, if there is a possibility of an fatal error, it will certainly happen.
I already had an error in typing a command in the console and... trump-pump-pump, all over again.
Therefore, gparted live to prepare the disk, select commands, then, after checking, confirm execution.
But this is just my path.

Regards.

So instead you'll need to fiddle with the shell at that point, which of course is far from ideal. Basically enter the shell with C-A-F2 and erase the partition with dd.

Simpler solution : execute a shell within the install, format the EFI partition with mkfs.fat -F 32 /my/partition, exit the shell to return to the installer and ta-da ! : D

It sure does seem that the partman developers try to be clever about the "EFI System Partition" and exclude the offer to erase a pre-existing ESP.

So instead you'll need to fiddle with the shell at that point, which of course is far from ideal. Basically enter the shell with C-A-F2 and erase the partition with dd.

What hinders you to set up the exact same scheme again with gparted?

Well you have to set up luks again, but you can you the same PW. What hinders you? I do that all the time when I am not happy with what I got.

Okay, I can just make the same partionning layout but that was not the question. I don't try to erase my drive and reinstall, I ask if it's possible to re-format the existing EFI partition within the installer like I can do it with Arch installation medium.

rolfie wrote:

In a second step, you may use a gparted live iso to write a new partition table to the nvme. Then all exisiting partitions are history., and you may set up you desired partitioning scheme.

As I said, I want to keep my partition table. Like this I don't have to erase the luks header and have to learn another password.

What hinders you to set up the exact same scheme again with gparted?

Well you have to set up luks again, but you can you the same PW. What hinders you? I do that all the time when I am not happy with what I got.

In a second step, you may use a gparted live iso to write a new partition table to the nvme. Then all exisiting partitions are history., and you may set up you desired partitioning scheme.

As I said, I want to keep my partition table. Like this I don't have to erase the luks header and have to learn another password.

It's the solution I thought about. Formating it before to clean it and then it will be automatically used by the installer. I was just wondering if there were another way to do it from the installer instead of using a command line.

I mark the subject SOLVED. Thank you everybody for your answers

PS: and @fsmithred, I read about UEFI and systemd bricking some motherboard. I'm scared know x) I'll check if this issue is also on Devuan and sysvinit : )

The problem is that the installer keep and use the EFI partition automatically. There is no option to re-format this partition.
You can tell the installer not to use it but not to format it.
Now I know how to delete old EFI files and entries it's not a big deal but I'm still curious to know if we can do it or not.

Thank you for your link. But I already format my EFI partition while installing Arch Linux before and nothing happened, l'm lucky.
About this, the expert installer of Devuan ask if we want to write on NVRAM, is it okay ? I did it because I thought it was the right way to install the booloader but now I'm in doubt.

Be forewarned that some motherboards with poor uefi implementations may be bricked by formatting the efi partition. Here's some info about that:
https://superuser.com/questions/1318593 … -dangerous

How to re-format the Boot EFI partition within the installer ?

efibootmgr -b XXXX -B

where XXXX is the boot order number given by efibootmgr without any arguments.

I thought formatting it in a shell at the same time I use cryptsetup to open my encrypted partition but is there another way to do it ?

Here's my partition layout

$ lsblk -f /dev/nvme0n1
NAME                 FSTYPE      FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1          vfat        FAT32 ESP   3075-B1FE                               505M     1% /boot/efi
├─nvme0n1p2          ext4        1.0   boot  ddd9f57d-603b-423f-ac55-8b626e13d427  812,8M    10% /boot
└─nvme0n1p3          crypto_LUKS 2           3b33f705-8877-480d-9555-a3df72b944b8
  └─cryptlvm
    ├─arch_vg-swap                                                                               [SWAP]
    ├─arch_vg-rootfs                                                                25,1G     9% /
    └─arch_vg-home                                                                 824,6G     0% /home

Thanks : )
(I forgot to rename my volume group -___-)