[DUPLICATE] Waiting for modules in Calamares takes indefinitely long

General system EndeavourOS installation
1

Well this is a duplicate of an issue I posted at the Garuda Linux forums and well this issue has been plaguing me on nearly all new arch-calamares based distros’ ISO files including EOS. All the details can be found at the link (including logs) below:

TLDR

All instances show same logs with them
looping around same module: partition and get
hung on closing with the same logs. Calamares gets stuck and has the instance running because a job for grub-mount and os-prober hangs and keeps running in the background. Logs below:
TLDR END

Current TLDR
Logs below reveal that a job for grub-mount and/or os-prober runs when Calamares is started and hangs on either of my quadruple boot Linux partitions. It seems that os-prober and/or grub-mount tried perhaps to mount my ext4 Linux partitions as ext2. This is prevalent in newer versions of Calamares in two distros I tried, Garuda and Archcrsft, and absent in an older version of EndeavourOS.
TLDR End

I am unsure as to whether I should re-post the logs and the entire post here again.

2

Can you share the output of sudo parted -l

3

From the usb or any running linux system ? Btw I have a quadruple boot, with 3 linux distros and windows 10 ltsc. Also I should mention it, endeavour os galileo iso, the very first one, works really fine.

sudo parted -l from OpenSUSE install:

Model: ATA WDC WD10EZEX-60W (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  106MB   105MB   fat32           EFI system partition          boot, esp
 2      106MB   123MB   16.8MB                  Microsoft reserved partition  msftres
 3      123MB   74.4GB  74.2GB  ntfs            Basic data partition          msftdata
 4      74.4GB  74.9GB  537MB   fat32                                         boot, esp
 5      74.9GB  142GB   67.6GB  ext4
 6      142GB   143GB   537MB   fat32                                         boot, esp
 7      143GB   208GB   65.0GB  ext4
 8      208GB   209GB   537MB   fat32                                         boot, esp
 9      209GB   257GB   48.8GB  btrfs
10      257GB   262GB   4287MB  linux-swap(v1)                                swap
11      262GB   404GB   142GB   ntfs                                          msftdata
12      404GB   404GB   537MB   fat32                                         boot, esp
13      404GB   451GB   47.1GB  ext4
14      451GB   524GB   73.1GB  btrfs
15      524GB   525GB   537MB   fat32                                         boot, esp
16      525GB   617GB   92.4GB  ext4
17      617GB   748GB   130GB   ext4
18      748GB   802GB   54.5GB  ext4
19      802GB   865GB   62.9GB  ext4
20      865GB   1000GB  135GB                                                 msftdata


Model: SanDisk Cruzer Blade (scsi)
Disk /dev/sdb: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  31.4GB  31.4GB  primary
 2      31.4GB  31.4GB  33.6MB  primary  fat16        esp
4

It doesn’t matter, it should be the same in all distros.

Ahh…have you tried cleaning that up at all. Even if you quadruple boot, you shouldn’t have 6 EFI partitions.

5

One separate for each distro’s Grub ? Also my EFI entries are perfectly managed so no issue there I think, os-prober hangs on my linux installs instead I think. Btw one of the EFI partitions is empty.

6

Sure but 4 installs should not have 6 EFI partitions.

Probably, it is in an os-prober issue, yes.

I would start by deleting any unused partitions and see if that improves things.

7

Tried that, just hangs on another partition.

8

Can you run os-prober successfully from an arch-based distro or the latest ISO?

9

I currently have Garuda Linux on my usb, you want me to do that or run os-prober from the latest Garuda install instead, its fully updated.

10

You can run it from the garuda install

1 Like
11

What exactly must I run ?

12 
sudo os-prober
13

Output:

sudo os-prober
/dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sda16:Fedora Linux 41 (Workstation Edition):Fedora:linux
/dev/sda5:openSUSE Tumbleweed:openSUSE:linux
/dev/sda7:Void Linux:Void:linux

Runs successfully and takes 10 seconds at most.

14

It might be that you don’t have package lsb-release (or equivalent) installed on the other systems?

15

Just verified, they do have it installed. Also it makes sense that all of my distros have it installed because 4 out of 5 of my distros are standard desktop installs whereas only one, Artix Linux is the barebones install and yet Artix still has this package preinstalled.