Okay … what nvme drive is it? Make & model?
So, it isn’t just Calamares.
Not sure but I wonder if it might be a case for low level formatting?
Please do some research. I don’t want to be held responsible for any material or other damages 
There are two newer Bios updates for this Motherboard. You may want to update to the latest version 3202 dated 2021/08/05
1 Like
TCSUNBOW M.2 PCIE Gen3 x 4 512gb
This is a odd chinese brand drive. Never heard of it before.
@StefanoMarton
When you installed did you try running gparted and create a new GPT partition first. Then close gparted and run the installer and use erase disc with swap file and ext4.
It’s a strange, not usual case. Do post output
sudo fdisk -l
sudo inxi -dpuoLRa
1 Like
Could use Active Kill Disk and create a boot-able usb to run a low level format on the drive.
Do you think it might help in cases like this?
Won’t just dd-zeroing do? (or some such)
It’s hard to say without trying it. I’m used to name brand hardware such as seagate or western digital etc so i would use the low level format utility they have.
1 Like
Yes dd-zeroing should do the same and that’s most likely what i would do.
1 Like
1 Like
fdisk -l
Disk /dev/sda: 111,79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SA400S3
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: 92129137-8464-1341-BC98-4113C6ADF934
Device Start End Sectors Size Type
/dev/sda1 34 1050623 1050590 513M EFI System
/dev/sda2 1050624 234441614 233390991 111,3G Linux filesystem
Disk /dev/sdb: 465,76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: SAMSUNG HD502HJ
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: 0x5ee65ee6
Disk /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: NVME SSD 512GB
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: 408594DE-D0E9-4062-BFBE-5A0C5DCCD464
Device Start End Sectors Size Type
/dev/nvme0n1p1 34 97656250 97656217 46,6G Linux filesystem
Disk /dev/loop2: 4 KiB, 4096 bytes, 8 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/loop1: 55,52 MiB, 58212352 bytes, 113696 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/loop0: 76,5 MiB, 80220160 bytes, 156680 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/loop3: 164,76 MiB, 172761088 bytes, 337424 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/loop4: 65,21 MiB, 68378624 bytes, 133552 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/loop5: 44,68 MiB, 46845952 bytes, 91496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytesand the other
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 1.03 TiB used: 35.2 GiB (3.3%)
ID-1: /dev/nvme0n1 maj-min: 259:0 model: NVME SSD 512GB size: 476.94 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
type: SSD serial: 2020111200220 rev: T0609B0L temp: 28.9 C scheme: GPT
SMART: yes health: PASSED on: 155d 18h cycles: 755
read-units: 17,584,100 [9.00 TB] written-units: 27,136,695 [13.8 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37120G
family: Driven SSDs size: 111.79 GiB block-size: physical: 512 B
logical: 512 B sata: 3.2 speed: 6.0 Gb/s type: SSD
serial: 50026B77838A10F8 rev: 0010 temp: 23 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 158d 17h cycles: 827
read: 1666 GiB written: 1708 GiB
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: HD502HJ
family: SpinPoint F3 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B sata: 2.6 speed: 3.0 Gb/s type: HDD rpm: 7200
serial: S27FJ9CZ304214 rev: 0002 temp: 24 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 3y 57d 1h cycles: 10787
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 111.29 GiB size: 108.98 GiB (97.93%)
used: 35.2 GiB (32.3%) fs: ext4 block-size: 4096 B dev: /dev/sda2
maj-min: 8:2 uuid: 431a764c-1189-4539-a492-b373115ccb3a
ID-2: /boot/efi raw-size: 513 MiB size: 512 MiB (99.80%)
used: 300 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
uuid: EBAD-002F
Unmounted:
ID-1: /dev/nvme0n1p1 maj-min: 259:2 size: 46.57 GiB fs: N/A uuid: N/AAlready been update before starting
I checked for low-level format and it isn’t compatible
Interesting! Thanks!
I tried dd-zeroing and it keeps loading to the inifinite 
Looks like the filesystem, UUID are not “seen”
The Calamares logs also complained about unknown filesystem:
Can not resize “/dev/nvme0n1” , filesystem “unknown” does not support resize.
Because of a lot of discussion and several changes on the disk partition, we may be misunderstanding the real problem here.
I would suggest a rest and start from the beginning.
Now it seems the nvme drive is with GPT table and has one large partition.
I understood that you prefer UEFI installation, so the best is to
- delete the existing partition and shutdown to make sure the changes are saved properly.
- It’s a desktop, so remove (or disconnect the cables from MB) the other two drives, leaving only the nvme in the box.
- Boot with the Installer ISO and use gparted to create a UEFI/GPT layout: 512MB vfat, 100GB ext4 (or btrfs, whatever you intended to). Apply/Save gparted actions and reboot again.
- Make sure you boot to the UEFI option of the USB
- Check again the disk layout (it terminal with
sudo fdisk -l, DO NOT OPEN ANY File Manager) and if OK, go start the installer in a terminal (IIRC issudo calamares -d)
Post results
After the other operation, partition is ok
[liveuser@eos-2022.04.08 ~]$ sudo fdisk -l
Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: NVME SSD 512GB
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: 3D9E3263-AD32-483D-A205-A753CFD71570
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 205850623 204800000 97.7G Linux filesystembut the second one give me kind of error, I can’t launch calamares from terminal
22:10:21 [1]: static Calamares::Settings* Calamares::Settings::init(bool)
ERROR: Cowardly refusing to continue startup without settings.
"/home/liveuser/settings.conf"
"/etc/calamares/settings.conf"
"/usr/share/calamares/settings.conf"
22:10:21 [1]: static Calamares::Settings* Calamares::Settings::init(bool)
ERROR: FATAL: none of the expected configuration file paths exist. Calamares opens normally from gui
Thanks you a lot for your time and patiance
1 Like