Calamares gets stuck on infinitely loading on "Scanning storage devices"

I am trying to reinstall manjaro after unfortunate accident with terrible advice from this post Cannot use valgrind - #4 by jrwrigh
But I cannot get past the partitioning section. It is just stuck on “scanning storage devices”

There is no error in the debug mode. Also when I launch the calamares installer second time it gets stuck at the very beggining on

22:35:46 [6]: void Calamares::RequirementsChecker::reportProgress()
    Remaining modules: 1 

I have a windows on the drive. But it is completely standard installation. So I am a bit confused what is wrong. I had similar issue Calamares installation wizard crashes immediatly after running it - #11 by cscs but that time it just crashed, now it does not.
the blkid output (I am trying to install on the sda drive):

/dev/sda1: UUID="E642-51A9" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="c2c6fc16-d
/dev/sda3: BLOCK_SIZE="512" UUID="6004519004516A54" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="022
/dev/sda5: UUID="a991f713-eef5-4c62-9f54-3f9ba5fd2137" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6b8087c3-49f1-4
/dev/sda4: UUID="4f2b0c3f-a780-4c5c-8e95-cb6a31e5742d" TYPE="swap" PARTUUID="47973be5-0233-403b-9052-582076ce4
/dev/sda7: UUID="D916-BC3E" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="cb471941-beb4-44a7-8950-6bcc9c1cc851"
/dev/sda6: UUID="CD94-B4B3" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f97d0e4a-6f51-43c7-9f10-caf42a230884"
/dev/sdb1: LABEL="Large" BLOCK_SIZE="512" UUID="489E1D629E1D4A38" TYPE="ntfs" PARTUUID="21e86908-01"
/dev/sdb3: UUID="bb479b27-3df3-48b5-a871-174198018fa8" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="21e86908-03"
/dev/sdb2: UUID="b380cf91-8330-425e-957d-bceed4346494" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="21e86908-02"
/dev/sdb4: UUID="7BEF-2237" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="21e86908-04"
/dev/loop1: BLOCK_SIZE="262144" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="262144" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="262144" TYPE="squashfs"
/dev/sdc1: BLOCK_SIZE="2048" UUID="2024-04-06-03-22-56-00" LABEL="MANJARO_KDEM_2314" TYPE="iso9660"
/dev/loop3: BLOCK_SIZE="262144" TYPE="squashfs"

I attempted the install with the newest manjaro kde image and even the manjaro cinnamon. No luck either way.
System info:

██████████████████  ████████   manjaro@manjaro 
██████████████████  ████████   --------------- 
██████████████████  ████████   OS: Manjaro Linux x86_64 
██████████████████  ████████   Host: MS-7C52 1.0 
████████            ████████   Kernel: 6.6.25-1-MANJARO 
████████  ████████  ████████   Uptime: 23 mins 
████████  ████████  ████████   Packages: 1149 (pacman) 
████████  ████████  ████████   Shell: bash 5.2.26 
████████  ████████  ████████   Resolution: 1920x1080 
████████  ████████  ████████   DE: Plasma 5.27.11 
████████  ████████  ████████   WM: KWin 
████████  ████████  ████████   Theme: [Plasma], Breeze [GTK2/3] 
████████  ████████  ████████   Icons: [Plasma], breeze [GTK2/3] 
████████  ████████  ████████   Terminal: konsole 
                               CPU: AMD Ryzen 5 1600 (12) @ 3.875GHz 
                               GPU: NVIDIA GeForce GTX 1660 Ti 
                               Memory: 3157MiB / 15914MiB 


I got over that issue with manjaro-architect, but the system did not install correctly, and it always fails on running /sbin/init. From what I gathered, it probably means that the fstab did not generate correctly and it is true that the fstab is empty. But I do not have energy for this anymore I just gave up and now I am trying to install Linux mint lol.

Where is /dev/sda2? Maybe that is the hangup cause.

And Sbin/init? You mean SysV init? That must be years and years old. I’m not surprised Architect doesn’t work.

When performing a re-installation, I have found it best to completely wipe the installation drives by creating a new partition table. Open Gparted and from the Device menu, select “Create Partition Table…”, be sure to select GPT for type.

It usually works.

I vaguely remember I have seen the issue myself - it was a long time age - I don’t recall the specifics - it could be LVM related as Calamares does not support installing to a disk that has LVM on it.

I am beginning to recall

If the device in question has been used with a system which creates LVM by default such as Fedora or Red Hat - the device preselected in the dropdown will be the LVM device.

Sometimes there is two devices in the dropdown where the other is the raw disk.

If that is so - select the raw disk.

Another option is to open a terminal, locate the device and clear all partition info.

sudo sgdisk --zap-all --clear /dev/foo
1 Like

after unfortunate accident with terrible advice from this post Cannot use valgrind - #4 by jrwrigh

Sorry. That post is almost 2 years old at this point and I do mention in it:

For anybody else seeing this, it’s not a permanent solution, just a workaround.

Three messages down from that I added an update saying that the issue was resolved in later versions of glibc.

Why isn’t this topic not locked? The OP don’t care about help anyways.