Failed setup.sh on Manjaro Linux : no loop device

[MadMcCrow]

When trying to build to ISO on Manjaro Linux I get this output (removed all the pacman output)

FEATURES=KEYMAP,ISO bash setup.sh cli arch                                                                                                                                                                                                                        

▄▄▄▄▄▄                                            ▄▄      
██▀▀▀▀██                                  ██      ██      
██    ██   ██▄████   ▄████▄    ▄█████▄  ███████   ██▄████▄
███████    ██▀      ██▄▄▄▄██   ▀ ▄▄▄██    ██      ██▀   ██
██    ██   ██       ██▀▀▀▀▀▀  ▄██▀▀▀██    ██      ██    ██
██▄▄▄▄██   ██       ▀██▄▄▄▄█  ██▄▄▄███    ██▄▄▄   ██    ██
▀▀▀▀▀▀▀    ▀▀         ▀▀▀▀▀    ▀▀▀▀ ▀▀     ▀▀▀▀   ▀▀    ▀▀
┌──────────────────────┐
│Made by MilkyDeveloper│
└──────────────────────┘
KEYMAP,ISO
What would you like the username to be?
NOTE: No UPPERCASE letters, spaces, backslashes, or special characters
perard

What would you like the hostname to be? (if no hostname is specified, it will be arch)
NOTE: No spaces, backslashes, or special characters
CarolinePro
Installing Dependencies
Installing sudo vboot-kernel-utils arch-install-scripts git parted wget cgpt
Downloading kernel files from cb-lines/breath
kernel.flags                                                                   100%
arch-rootfs.tar.gz                                                             100%
Building ISO at /home/perard/linux-build/breath.img
losetup: impossible de trouver un périphérique de bouclage inutilisé
ERROR: no loop device

trying to build directly to USB give me this instead (removed the identical begining)

Which USB Drive or SD Card would you like to use (e.g. /dev/sda)? All data on the drive will be wiped!
sdb         STORE N GO                usb
/dev/sdb
Ok, using /dev/sdb to install Linux
umount: /dev/sdb: non monté.
umount: /dev/sdb1: non monté.
umount: /dev/sdb2: non monté.
umount: /mnt: non monté.
umount: /media/*/*: Aucun point de montage indiqué.
Writing storage, may take more than 5 minutes.
Although it seems slow, consider this process like flashing an ISO to a USB Drive.
Below is an innacurate indicator of mB left to write. It may decrease hundreds of megabytes in seconds.
14.10MB
24120+0 enregistrements lus
24120+0 enregistrements écrits
12349440 octets (12 MB, 12 MiB) copiés, 0,914233 s, 13,5 MB/s
mke2fs 1.46.5 (30-Dec-2021)
En train de créer un système de fichiers avec 7560704 4k blocs et 1892352 i-noeuds.
UUID de système de fichiers=b6f269d6-e31e-4161-8bbf-bb1c464f27fb
Superblocs de secours stockés sur les blocs : 
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
4096000

Allocation des tables de groupe : complété                        
Écriture des tables d'i-noeuds : complété                        
Création du journal (32768 blocs) : complété
Écriture des superblocs et de l'information de comptabilité du système de
fichiers : complété

Writing storage, may take more than 5 minutes.
Although it seems slow, consider this process like flashing an ISO to a USB Drive.
Below is an innacurate indicator of mB left to write. It may decrease hundreds of megabytes in seconds.

umount: /mnt: non monté.
umount: /mnt: non monté.
mount: /mnt: type de système de fichiers « ext4 » inconnu.
dmesg(1) peut avoir plus d'informations après un échec de l'appel système du montage.

in both cases this looks like a mounting issue. I'm no linux expert so I can't really tell what's going on, but I can tell that my loop module exists :

sudo ls /lib/modules/5.18.3-1-MANJARO/kernel/drivers/block                                                                                                                                                                                                                      
aoe  brd.ko.xz  drbd  floppy.ko.xz  loop.ko.xz  mtip32xx  nbd.ko.xz  null_blk  pktcdvd.ko.xz  rbd.ko.xz  rnbd  sx8.ko.xz  virtio_blk.ko.xz  xen-blkback  xen-blkfront.ko.xz  zram

but may not be loaded:

sudo modprobe loop 
modprobe: FATAL: Module loop not found in directory /lib/modules/5.18.2-1-MANJARO

any way. this is a default Manjaro install on my side, so I guess something has to be done to make this script work with this distro.

Thank you for your help in advance.

[MilkyDeveloper]

Your system is definetly borked. modprobe loop is a common practice that should work regardless of distro.

umount: /mnt: not mounted.
umount: /mnt: not mounted.
mount: /mnt: unknown 'ext4' filesystem type.
dmesg(1) may have more information after the mount system call fails.

Also, how is ext4 not a supported filesystem? Your root filesystem is probably ext4, so is Ubuntu's, Fedora's, and most other distros's.

losetup: cannot find an unused loopback device

isn't possible on kernels without a loop device limit.

Or, you didn't reboot yet, explaining why modprobe loop doesn't work ;D. I would've made the same mistake on a fresh install of Linux.

[MadMcCrow]

yep ! rebooting did the trick. thanks!