The installer gets stuck on “Waiting for 1 module(s).” And I’ve definitely waited a while, but no success.
Hardware information: https://clbin.com/XWck2
Boot Log: https://clbin.com/Jm8yW
The installer simply stays on this step forever. I’ve reached over 1000 second(s) and still no progress forward.
Also, GParted does not detect any of my drives. Stays endlessly on “Scanning /dev/sda”. I only have two drives. One NVME and one SSD.
Any assistance would be appreciated.
Can’t think ATM what to tell you - but I strongly suspect that the issues are not unrelated. The module that won’t load is probably having the same problem with drive access! (I HAVE had that slow module, although NOT that slow).
Have you tried accessing the drives with any alternate programs? Specifically command line programs. There is parted and fdisk and several others I can’t think of right now) - there might be an error message that would move us along that way…
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS SIZE OWNER GROUP MODE
loop0
squash 4.0 0 100% /run/archiso/airootfs
1.6G root disk brw-rw----
sda 931.5G root disk brw-rw----
├─sda1
│ vfat FAT32 DEC9-913C 100M root disk brw-rw----
├─sda2
│ 16M root disk brw-rw----
├─sda3
│ ntfs A886CACA86CA97E8 930.8G root disk brw-rw----
└─sda4
ntfs 9E302BD5302BB367 604M root disk brw-rw----
sdb iso966 Jolie EOS_202209
2022-09-10-10-51-40-00 7.6G root disk brw-rw----
├─sdb1
│ iso966 Jolie EOS_202209
│ 2022-09-10-10-51-40-00 0 100% /run/archiso/bootmnt
│ 1.7G root disk brw-rw----
└─sdb2
vfat FAT16 ARCHISO_EFI
C8C0-D262 104M root disk brw-rw----
nvme0n1
931.5G root disk brw-rw----
└─nvme0n1p1
ntfs New Volume
849CD9A49CD99152 931.5G root disk brw-rw----
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WDBNCE0010P
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: 12BBFFAC-F1FC-4E12-A98A-BF3F533D97A5
Device Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda2 206848 239615 32768 16M Microsoft reserved
/dev/sda3 239616 1952284671 1952045056 930.8G Microsoft basic data
/dev/sda4 1952284672 1953521663 1236992 604M Windows recovery environment
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDS100T1X0E-00AFY0
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: 56260EAD-A306-F24C-9677-EA95800A264C
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1953523711 1953521664 931.5G Microsoft basic data
Disk /dev/sdb: 7.61 GiB, 8166703104 bytes, 15950592 sectors
Disk model: USB 2.0 FD
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: 0x1e784590
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 3583359 3583296 1.7G 0 Empty
/dev/sdb2 3583360 3796351 212992 104M ef EFI (FAT-12/16/32)
Disk /dev/loop0: 1.61 GiB, 1724010496 bytes, 3367208 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
EDIT: I’ve tried two different USBs with the same ISO download link “Github - World Wide - ISO download option”.
Created two separate bootable USB drives using Rufus.
Using the latest available “EndeavourOS_Artemis_nova_22_9.iso”.
I would try using etcher on Windows to create the live ISO. Rufus sometimes people have issues using it.
Hey. Etcher worked. Installed EndeavourOS with Gnome de.
Thank you for the suggestion. No other issues presented themselves during the install. All smooth after using Etcher.
I don’t particularly like or recommend rufus myself. It seems to create multiple partitions on the live usb that don’t always work properly. Some people have luck with it but i always use etcher on Windows and i use popsicle on EndeavourOS which can be installed from the AUR.
For me BalenaEtcher has been hit and miss. I went for Suse Image Writer instead, and it has worked every time since.
Etcher has always worked for me on Windows. Matter of fact i used it on EndeavourOS also until i found popsicle. I have never ever had an issue with it. It is always what i recommend if the user is creating a live usb from Windows. There are lots of other tools that work well on Linux but on Windows people tend to go to Rufus which can be a problem as in this case.
dd is the best! 
I hardly ever use dd because it’s too hard to remember. I would have to look it up. 
For me, BalenaEtcher has been most reliable. I have used it now as needed, for a length of time without any issues, ever.
I use Fedora Media Writer, very simple and has always worked
That’s why I keep it written down
I’m bad for trying to do everything from memory but it’s too much. 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.