Build iso new errors

ERROR: file not found: ‘/usr/lib/initcpio/udev/11-dm-initramfs.rules’
and
usr/lib/manjaro-tools/util-iso.sh: line 89: 274624 Segmentation fault (core dumped) mksquashfs “${mksfs_args[@]}”
==> ERROR: A failure occurred in make_iso().
Aborting…

Are you sure your build system is up-to-date?

The following is only applicable if using linux 6.18rc4+

I recall a recent change to mkinitcpio as mentioned in the Announcements > Unstable Updates thread [Unstable Update] November 2025 - #2 by GaVenga

I noted yesterday the community edition manjaro-sway had an ISO rebuild 251109 and I have heard of no issues with the tools - but then - I am not the first to hear about it :slight_smile:

verification

For the sake of verifying I am current running a default build of xfce.

buildiso -p xfce -k linux612 -b stable -n

And we have a winner - I can confirm the issue - @philm @Yochanan

Creating 4.0 filesystem on /a/projects/builddir/root/buildiso/xfce/iso/manjaro/x86_64/desktopfs.sfs, block size 262144.
[=========================|                                                                                           ]  34559/157841  21%/usr/local/lib/manjaro-tools/util-iso.sh: line 89: 94627 Segmentation fault         (core dumped) mksquashfs "${mksfs_args[@]}"
==> ERROR: A failure occurred in make_iso().
    Aborting...

The aforementioned issue with mkinitcpio resulted in a special version of mkinitcpio on Manjaro.

I have downgraded mkinitcpio to

sudo pacman -U /var/cache/pacman/pkg/mkinitcpio-39.2-4-any.pkg.tar.zst
 $ mkinitcpio --version
mkinitcpio "39.2"

Then rerunning the build

buildiso -p xfce -k linux612 -b stable -n

Using the previous version result in the same error.

(mkinitcpio 40-1 is in Arch stable)

Looking closer at the output - after building mhwdfs - in preparing the boot

==> Prepare [/iso/boot]
 --> overlayfs mount: [/a/projects/builddir/root/buildiso/xfce/x86_64/bootfs]
  -> Copying initcpio ...
==> Starting build: '6.12.57-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [miso_shutdown]
  -> Running build hook: [miso]
==> ERROR: file not found: '/usr/lib/initcpio/udev/11-dm-initramfs.rules'
[...]

Ultimately leading to

  -> Creating SquashFS image, this may take some time...
Parallel mksquashfs: Using 24 processors
Creating 4.0 filesystem on /a/projects/builddir/root/buildiso/xfce/iso/manjaro/x86_64/desktopfs.sfs, block size 262144.
[======================\                                                                                              ]  28677/150540  19%/usr/local/lib/manjaro-tools/util-iso.sh: line 89: 279502 Segmentation fault         (core dumped) mksquashfs "${mksfs_args[@]}"
==> ERROR: A failure occurred in make_iso().
    Aborting...

In case this may be useful in the interim; the content of
/usr/lib/initcpio/udev/11-dm-initramfs.rules:

# needed with new udev/mkinitcpio and as implemented in dracut:
# <http://git.kernel.org/?p=boot/dracut/dracut.git;a=commitdiff;h=12b9736228f2b34c15a9cb63be79cf7b6e865b54>
SUBSYSTEM=="block", KERNEL=="dm-[0-9]*", ACTION=="add|change", OPTIONS="db_persist"

Putting the above in still produces the error

@robin0800 Good to know I am not the only one that sometimes has ISO building issues :slight_smile:

Here is what I have learned in the last two years,

First, instead of adding your parameters in the command line, add them to your
~/config/manjaro-tools/manjaro-tools.config

So that when you run buildiso -p xfce the parameters are pulled from that config file, yes I know you can use the parameters in the command line, but for some reason, I have always had better luck with the config file.

Second, always eliminate the iso-profiles by backing up your iso-profiles, “cleaning your hard drive” as detailed in the wiki, at the bottom: Build Manjaro ISOs with buildiso - Manjaro

The reinstall iso-profiles, run buildiso -p xfce and see if it builds the default, if it does, then transfer you settings from the backup iso-profiles to the new one and move on. If the issue is still there, then you have something else that is the problem.

I can’t tell you how many times I have chased down buildiso issues to only have them be an issue with iso-profiles.

FYI, I just built a new iso of my spin using kernel 6.17 and cinnamon and it built perfectly with no issues.

It still fails! Did you manage to get rid of the error message?

I just tried building XFCE on my build machine, and it built with no issues, even built with Xlibre!

The fact that it is failing during the building of the ISO, would indicated that it is running out of space, are you 100% sure there is enough space for the building process?

Now I am slightly confused

 $ pacman -Qo /usr/lib/initcpio/udev/11-dm-initramfs.rules
error: No package owns /usr/lib/initcpio/udev/11-dm-initramfs.rules

Speculating if the branch used on build host vs the branch used for the target ISO interferes somehow.

The package containing the buildiso script was rebuilt ~10 weeks ago - so what has changed in the interim - that is what directly related has changed ?

 $ pacman -Qi manjaro-tools-iso-git
Name            : manjaro-tools-iso-git
Version         : r3054.14521ab-1
Description     : Development tools for Manjaro Linux (ISO tools)
Architecture    : any
URL             : https://gitlab.manjaro.org/tools/development-tools/manjaro-tools
Licenses        : GPL-3.0-or-later
Groups          : manjaro-tools
Provides        : manjaro-tools-iso=0.15.15dev
Depends On      : dosfstools  git  grub  libisoburn  manjaro-tools-yaml-git  mkinitcpio  mktorrent  snapd  squashfs-tools
Optional Deps   : None
Required By     : None
Optional For    : manjaro-tools-base-git
Conflicts With  : manjaro-tools-iso
Replaces        : None
Installed Size  : 108,79 KiB
Packager        : Philip Mueller <philm@manjaro.org>
Build Date      : tir 26 aug 2025 10:36:23 CEST
Install Date    : tir 07 okt 2025 08:59:52 CEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

I see that stable branch has mkinitcpio 39-2

 $ mbn info mkinitcpio -q
Branch         : archlinux
Name           : mkinitcpio
Version        : 40-2
Repository     : core
Build Date     : Mon 10 Nov 2025 10:23:56 
Packager       : Christian Hesse <eworm@archlinux.org>
Branch         : unstable
Name           : mkinitcpio
Version        : 40-3
Repository     : core
Build Date     : Mon 10 Nov 2025 15:21:00 
Packager       : Mark Wagie <mark@manjaro.org>
Branch         : testing
Name           : mkinitcpio
Version        : 40-3
Repository     : core
Build Date     : Mon 10 Nov 2025 15:21:00 
Packager       : Mark Wagie <mark@manjaro.org>
Branch         : stable
Name           : mkinitcpio
Version        : 39.2-4
Repository     : core
Build Date     : Wed 18 Dec 2024 23:07:39 
Packager       : Mark Wagie <mark@manjaro.org>

And that Manjaro has a custom version of mkinitcpio - one step ahead of upstream Arch (possibly related to the issue with changes to linux 618)

I have zero experience with building init et.al. so I can only search and I have no idea what the results of the search imply or does not imply ?

I tried all of the above and nothing worked. This was building an unstable ROM, today i managed to build a stable ROM no error appeared. So this was on unstable and I have no idea what the difference is between building an unstable rom and building a stable one is?

1 Like

Most likely this:

/usr/lib/initcpio/udev/11-dm-initramfs.rules has been removed as of lvm2 2.03.36-2. You may need to downgrade device-mapper and lvm2, if you encounter an error during mkinitcpio.

I believe it has been included in 10-dm.rules as per this merge request. So if you have a hook that requires it but cannot find it, mkinitcpio will throw an error.

1 Like

I had to downgrade mkinitcpio before I could downgrade device-mapper and lvm2.

The error message still appears but the rom builds. I have updated mkinitcpio and the rom still builds.

Now the error message has gone!

manjaro-tools-iso-git has been updated accordingly with r3058.c2d9e66-1.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.