ClearLinux not showing disks on "Destructive Installation"

General Discussion
1

I have a laptop with a samsung nvme where I have installed Pop_OS. I want to give ClearLinux a try. It is a personal laptop so I just want to wipe the disk.

I downloaded the latest image from the website and opening the installer, it doesn’t show any disk in the combobox. However it is visible in disks management:

third
third1230×873 116 KB

I have secure boot disabled, on UEFI, and disk option is AHCI. The output of lsblk is the following one:

clrlinux@clr-live~ $ sudo !!
sudo lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0   2.7G  1 loop 
sda           8:0    1  28.9G  0 disk 
├─sda1        8:1    1  28.8G  0 part 
│ └─ventoy  252:0    0   2.9G  1 dm   
└─sda2        8:2    1    32M  0 part 
sdb           8:16   1     0B  0 disk 
nvme0n1     259:0    0 238.5G  0 disk 
├─nvme0n1p1 259:1    0   498M  0 part 
├─nvme0n1p2 259:2    0     4G  0 part 
├─nvme0n1p3 259:3    0   230G  0 part 
└─nvme0n1p4 259:4    0     4G  0 part 
clrlinux@clr-live~ $ sudo lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0   2.7G  1 loop 
sda           8:0    1  28.9G  0 disk 
├─sda1        8:1    1  28.8G  0 part 
│ └─ventoy  252:0    0   2.9G  1 dm   
└─sda2        8:2    1    32M  0 part 
sdb           8:16   1     0B  0 disk 
nvme0n1     259:0    0 238.5G  0 disk 
├─nvme0n1p1 259:1    0   498M  0 part /run/media/clrlinux/F8CD-6A5B
├─nvme0n1p2 259:2    0     4G  0 part /run/media/clrlinux/F8CD-6A7F
├─nvme0n1p3 259:3    0   230G  0 part /run/media/clrlinux/1467a273-e2d3-4c00-a1a7-cfd977a5d336
└─nvme0n1p4 259:4    0     4G  0 part [SWAP]
clrlinux@clr-live~ $

Even after mountingthe partitions of the nvme, the disk is not shown in the installer. What I’m doing wrong? Thanks in advance

2

I know we have had issues with NVME drives - I don’t know if this is relevant.

See also the advice paulcarroty gives - Clear will not install to nvme - #24 by mhorn

3

Thanks for answering! I’m not sure if it is the same issue, as it doesn’t even detect the drive in the first step of the installation process (maybe I would experience that issue later on?)