Installation fails at creating partition

I’m trying to install cachyOS on an external M.2 SSD on a Laptop that has two internal ssds, one of which has win10. This is the first distro I had problems installing so far( I used endeavour, garuda, nobara and Ubuntu before).Windows is able to create a partition on it, cachy is not.
I’m not very experienced and I don’t have very good Internet right now to download some other distro.
I tried partitioning with kde partition manager, also didn’t work.
Here is the log: https://termbin.com/rr6d

Any help is greatly appreciated

WARNING: Partition-module setting defaultPartitionTableType is unset, will use gpt for efi or msdos for bios
2024-12-29 - 21:39:07 [6]: virtual void Calamares::ViewModule::loadSelf()
2024-12-29 - 21:39:07 [6]: ViewModule “partition@partition” loading complete.
2024-12-29 - 21:39:07 [6]: void fillModel(PackageListModel*, const QVariantList&)
2024-12-29 - 21:39:07 [6]: Loading PackageChooser model items from config
2024-12-29 - 21:39:07 [6]: DEBUG (Qt): getting temp failed for “/dev/nvme0n1” : No such file or directory

As far as I understand, the error may be happenning because the installer doesn’t know what file system to use. Perhaps, you could try manually choosing one. I’m kind of a noob, so take it with a grain of salt, but it wouldn’t hurt to try it out.

I tried that, it unfortunately fails as well. I also tried to manually partition with the official guide, that fails too.

Could you run sudo fdisk -l and see if everything looks OK in the output?

The only thing that stands out to me is the I/O size of the first SSD(which is the one I want to install cachyOS on), but I don’t think it matters.

Have a look
Disk /dev/sda: 476.94 GiB, 512110190592 bytes, 125026902 sectors
Disk model: 2 VPN100        
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
**I/O size (minimum/optimal): 4096 bytes / 268431360 bytes**



Disklabel type: gpt
Disk identifier: 6A5AB734-AAF9-4918-AE0E-1FD3ACFBC5D8


Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: INTEL SSDPEKNU512GZ                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E84989E8-11D7-472C-A68E-C068C5F5A80E

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1      2048     206847    204800   100M EFI System
/dev/nvme0n1p2    206848     239615     32768    16M Microsoft reserved
/dev/nvme0n1p3    239616  999136628 998897013 476.3G Microsoft basic data
/dev/nvme0n1p4 999137280 1000212479   1075200   525M Windows recovery environment


Disk /dev/nvme1n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Lexar SSD NM620 1TB                     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 45EE610C-BE35-49C8-9561-162702668D5B

Device         Start        End    Sectors   Size Type
/dev/nvme1n1p1    34      32767      32734    16M Microsoft reserved
/dev/nvme1n1p2 32768 2000406527 2000373760 953.9G Microsoft basic data


Disk /dev/sdb: 28.65 GiB, 30765219840 bytes, 60088320 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00018855

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1  *     2048 60088287 60086240 28.7G  c W95 FAT32 (LBA)


Disk /dev/loop0: 2.21 GiB, 2374090752 bytes, 4636896 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 15.36 GiB, 16492003328 bytes, 4026368 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Yeah, I’m sorry, I have no idea. You’ve probably already done that, but make sure you’re using the latest ISO.