Installer doesn't detect HDs

Having been a long time Linux user, decided to try out Clear Linux, created a USB installation media and booted it. Pleasantly surprised to see it boot remarkably fast, faster than my BLFS system !

Wanted to install it an existing partition on my internal HDD, but the installer (both GUI and ncurses based installers) fails to see my HDD or the USB drive, the drop down is empty. I wanted to ask if it is a known issue, before I go about debugging it.

The installer is quite primitive, reminds me of the 90’s Red Hat days, even those days the installers provided more control and options. I’m quite disappointed with the installer.

Anyways, is these a work around for the part where the installer doesn’t find any HDDs and displays a message “Warning: No media found for installation” ?

@mhorn can you help with this question.

Thanks. I do not see any option to PM @mhorn.

Do you see your media under the “Destructive Installation”? That would be the full list of media the installer could use; but it would wipe the drive and create a new partition table to install Clear Linux.

The “Safe Installation” is media for which is either unallocated (no partition table) or has a ‘gpt’ partition table and has enough free space to install Clear Linux. If the disk has a mounted partition, it will also be excluded from possible install targets.

Can you share the output of lsblk?

Thanks. I don’t have my laptop with me right now, which is what I’m trying to install Clear Linux on.

I have tried both Safe and Destructive options and neither sees the HDDs.

lsblk can see both the internal HDD and the USB drive that is used to boot Clear Linux.

I have 5 GPT partitions on the internal HDD. EFI, Win10, 30GB ext4, 64GB ext4 and 60GB NTFS. I intend to install it on /dev/sda3 which has my BLFS system.

The installer cannot see the HDD, even if it did, it probably won’t list /dev/sda3 as a candidate, since you said it would only list free/unallocated space which, is strange and unexpected. You are assuming that every user would have either a free unused partition or have an entire disk drive to use for installation, which I don’t see as a very smart decision, no offense. One should be able to choose an existing partition, the installer should provide the option to either format it or install to it anyways, at least under advanced options.

If I can get the installer to detect my HDD, I could delete the partition and make it available for the installer as free space. That step should have been unnecessary, but whatever it takes.

The “Safe Installation” will only use free space, hence the “safe” part. :slight_smile:

Adding Advanced Disk configuration to the graphical installer is in the backlog, but not currently available. The current workaround would be to launch ‘gparted’, delete the existing partition you plan to use for Clear Linux OS install, and relaunch the installer (or use the Rescan button). The newly freed partition will be listed under the “Safe Installation” choice.

If the “Destructive Installation” is not seeing any disks, then there is some other problem. But without the output of lsblk and maybe dmesg it will be difficult to provide any direction on how to proceed.

The text-based installer does allow under the Advanced Configuration to select the partitions to overwrite, but it will still require you identifying partitions for ‘/boot’ (which must be VFAT), a swap, and the partition for ‘/’. But again, if there are no media listed under “Destructive Installation”, this method will not help either.

A safe installation is any that does what the user wants and doesn’t execute the commands right away, but then again viewpoints may vary.

I am going to try and debug the installer. Does the installer have a debug option ? Does the installer force the use of /boot and swap ? If yes, do you have the source code for the installer available, a URL please ?

I do not want a swap partition and as for /boot, I intend to use EFI partition. A separate partition for /boot would be a waste, I can always use a live CD or USB for rescue.

We get lots of people who found our first installer too complex. You can’t really satisfy everyone!

That’s not what we need. We need to see the exact output of lsblk. If you can give that to us, we can probably fix the issue with your HD detection.

A reboot seemed to have fixed the HDD detection. The installer is written in Go language, which I’m not familiar with so, I’m not going to attempt to modify the source code to fit my needs. I went ahead and installed successfully. I didn’t like the installer creating a swap partition and another EFI partition, it could have very well have given me the option to omit swap and use the existing EFI partition.

Uninstalled Gnome and installed KDE, it seems pulseaudio is forced as well, regardless of the DM used, which isn’t a very smart move either. I don’t need yet another set of tools to achieve something that ALSA is very much capable of by itself.

Now, I need to figure out how to pull in only the packages I need, rather than pull in all the packages a bundle brings in. If that is not possible, I’d rather stick with BLFS.

I hope you guys don’t turn Linux into Windows, taking away the freedom of choice and control.

Though it’s not recommended, if you know which CL package you want to install without bringing in other packages in the included bundle, you can download that specific RPM package (and its dependencies) from the release server [1], and cd / && rpm2cpio <RPM> | cpio -idmv to extract that RPM package at /

[1] for example, for release 29490:

1 Like

Thank you for the info, seems useful, will check it out.