Hi all! I have the error in installing EndeavourOS. This is a code of error:
Delete partition ‘/dev/sda1’ (465,73 GiB, exfat)
Job: Delete file system on ‘/dev/sda1’
Command: wipefs --all /dev/sda1
Failed to erase filesystem signature on partition ‘/dev/sda1’.
Could not delete file system on ‘/dev/sda1’.
Link: https://termbin.com/sz0m
Please, help me with this problem!
did you turn of secure boot / fastboot
yes
Open the partition manager while booted the from live iso, the right click on the /dev/sda1, then select delete, then hit apply, then finally star the installer again and go through the installation process again.
I’ll try it now
Doesn’t work 
Is there anything else installed on the same disk or are you installing a dual-boot?
Open a terminal and run the following(THIS WILL WIPE YOUR DISK SO MAKE SURE IT IS THE CORRECT DISK where you want to install EndeavorOS on and it will take a while):
sudo dd if=/dev/zero of=/dev/sda bs=1M count=4
Wait for it to finish, then might be a good idea to reboot and boot from usb flash drive again and then try installing again.
I use Toshiba Disk
2023-07-29 - 17:57:29 [6]: … Job 7 “Создать новый раздел 468235МиБ на /dev/sda (TOSHIBA MK5059GSXP).” +wt 0.0769231 tot.wt 1.46154
Do you have Windows installed on any other disk or is EndeavourOS the only operating system you will be using?
Yes, I have Windows on other disk
Don’t run this yet then, I don’t really have recent experience with dual-booting and it could be that Windows installs an efi partition on /dev/sda and if you wipe that you will have an unbootable Windows. So I would wait till someone with recent dual-boot experience replies to your topic.
Can you share the output of the following though when you run it from a terminal?
lsblk -f
Also it’s useful if you mention from the start of your topic if you are going to be dual-booting when asking a question about installing or running into a problem with installing.
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/archiso/airootfs
sda
└─sda1 exfat 1.0 Ventoy 4E21-0000
└─ventoy iso9660 Joliet Extension EOS_202305 2023-05-28-11-02-36-00 0 100% /run/archiso/bootmnt
nvme0n1
├─nvme0n1p1 vfat FAT32 SYSTEM 8AD4-E1B6
├─nvme0n1p2
├─nvme0n1p3 ntfs Windows 2A54F3A054F36CC7
└─nvme0n1p4 ntfs 3E7EC68C7EC63C81
[liveuser@eos-2023.05.28 ~]$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/archiso/airootfs
sda
└─sda1 exfat 1.0 Ventoy 4E21-0000
└─ventoy iso9660 Joliet Extension EOS_202305 2023-05-28-11-02-36-00 0 100% /run/archiso/bootmnt
nvme0n1
├─nvme0n1p1 vfat FAT32 SYSTEM 8AD4-E1B6
├─nvme0n1p2
├─nvme0n1p3 ntfs Windows 2A54F3A054F36CC7
└─nvme0n1p4 ntfs 3E7EC68C7EC63C81
You cannot install to the same drive from which you are running the installer (the live usb).
Looking at that output /dev/sda is your usb flash drive(Ventoy) where you are booted from and /dev/nvme0n1 is your ssd where you have Windows installed and where the efi partition for Windows resides. So you were trying to install EndeavourOS on the the usb flash drive you are booted from. Where were you expecting to install EndeavourOS?
On USB
I understood
‘/dev/sda1’ (465,73 GiB, exfat)
If you want to install EndeavourOS on that usb hard disk, you will have need another usb flash drive where you can boot EndeavorOS installation media from so that the usb hard disk is free to have something installed on.
Hey there, I just had this same issue, so I tried to replicate everything I was doing in gparted (partition manager). Turns out the installer lets you enter bad info. in gparted, if you try to enter a label for a fat32 partition that’s too long (not sure it’s only fat32, but it happened for my grub boot partition), gparted will only let you enter the max amount, but the installer allows entering a label as long as you like. I was using “endeavour_boot” as my label. gparted told only “endeavour_b” would fit, but the installer didn’t. I decided to try to just label it “eos_boot” and the problem was resolved.
I think this error is kind of catch all, so if you’re having problems (for anyone following the thread later), I would try to create your entire partition setup in gparted first and see if it complains. If not, you can just select those partitions for your swap/boot/etc. I hope this helps someone else out!
It did, thank you! In my case, I was doing manual partitioning and wasn’t providing labels at all. It worked after I provided names for partitions (eos_boot / eos_root respectively).
Glad to hear it @sukhoi191, and welcome to the community. 
Thank you @MonkCanatella for the useful tip. 
I will go ahead and close this old topic. If anyone still needs help with this, please open a new topic and link to this one for reference.