Unable to build an ISO using instructions from website

Support
,
1

I am trying to build a custom ISO using the instructions at the manjaro site but am unable to produce a usable ISO image. Currently, I am following the below steps after a fresh install of Manjaro Minimal:

sudo pacman -Sy archlinux-keyring manjaro-keyring
sudo pacman -Syu
sudo reboot
pamac install manjaro-tools-iso-git git
git clone https://gitlab.manjaro.org/profiles-and-settings/iso-profiles.git ~/iso-profiles
buildiso -p xfce

Once I am done, I see the following errors output as the process runs:

`==> WARNING: Possibly missing firmware for module: 'lantiq_gswip'`
`==> WARNING: Possibly missing firmware for module: 'softing_cs'`
`==> WARNING: Possibly missing firmware for module: 'liquidio'`
`==> WARNING: Possibly missing firmware for module: 'mlxsw_spectrum'`
`==> WARNING: Possibly missing firmware for module: 'bna'`
`==> WARNING: Possibly missing firmware for module: 'nfp'`
`==> WARNING: Possibly missing firmware for module: 'qed'`
`==> WARNING: Possibly missing firmware for module: 'bnx2x'`
`==> ERROR: invalid symlink: '/usr/lib/libnss_files.so.2'`
`==> ERROR: invalid symlink: '/usr/lib/libnss_dns.so.2'`
`  -> Running build hook: [miso_pxe_http]`
`  -> Running build hook: [miso_pxe_nbd]`
`  -> Running build hook: [miso_pxe_nfs]`
`  -> Running build hook: [miso_kms]`
`  -> Running build hook: [modconf]`
`  -> Running build hook: [block]`
`==> WARNING: Possibly missing firmware for module: 'qla2xxx'`
`==> WARNING: Possibly missing firmware for module: 'wd719x'`
`==> WARNING: Possibly missing firmware for module: 'aic94xx'`
`==> WARNING: Possibly missing firmware for module: 'bfa'`
`==> WARNING: Possibly missing firmware for module: 'qla1280'`
`  -> Running build hook: [filesystems]`
`  -> Running build hook: [keyboard]`
`  -> Running build hook: [keymap]`
`==> Generating module dependencies`
`==> Creating xz-compressed initcpio image: '/boot/initramfs.img'`
`==> WARNING: errors were encountered during the build. The image may not be complete.`

The resulting ISO is not usable and will not burn to a USB disk. The last time I ran this type of process was years ago and didn’t have this issue. I did search the forums and I saw a potential solution, but it’s over two years old and very unhelpful in that it doesn’t provide specifics regarding how to apply the solution. Any help which can be provided would be most appreciated. Thanks!

Mod edit:- Please always format code or command output as preformatted text. This has been corrected for you this time. In future you are expected to attend to this yourself.

2

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:

Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

Output of this command (formatted according to forum requirements) may be useful for those wishing to help:

inxi --filter --verbosity=8

or the short form:

inxi -zv8

Be prepared to provide more information and outputs from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Required reading
Resources

Regards.

3

That is strange - the tools are used every so often and is receiving ongoing maintenance.

I cannot say what your issue may be and the messages - disturbing as they look - have no consequence for the final ISO.

The most important output is the last lines of the console output - say about 20 lines or so.

I can do a proofreading of the wiki page - but that is about it - of course I can do a test run on my system.

Test run 
07:57:58 ○ [fh@tiger] ~
 $ buildiso -p xfce -n -k linux612 -b stable
 --> Profile: [xfce]
==> Start building [xfce]
==> Cleaning up ...
  -> Deleting chroot [rootfs] (x86_64) ...
  -> Deleting isoroot [iso] ...
 --> Loading Packages: [Packages-Root] ...
==> Prepare [Base installation] (rootfs)
 --> mirror: https://mirror.easyname.at/manjaro/stable/$repo/$arch
==> Creating install root at /a/projects/builddir/root/buildiso/xfce/x86_64/rootfs
  -> Installing packages to /a/projects/builddir/root/buildiso/xfce/x86_64/rootfs

[...]

==> Making bootable image
==> Creating ISO image...
xorriso 1.5.6 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev 'stdio:/miso/iso/manjaro/xfce/25/manjaro-xfce-25-minimal-250330-linux612.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data,  591g free
Added to ISO image: directory '/'='/a/projects/builddir/root/buildiso/xfce/iso'
xorriso : UPDATE :     820 files added in 1 seconds
xorriso : UPDATE :     820 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 512 bytes from file '/a/projects/builddir/root/buildiso/xfce/iso/boot/grub/i386-pc/boot_hybrid.img'
libisofs: NOTE : Automatically adjusted MBR geometry to 1021/145/32
xorriso : UPDATE :  14.10% done
ISO image produced: 1185887 sectors
Written to medium : 1185887 sectors at LBA 0
Writing to 'stdio:/miso/iso/manjaro/xfce/25/manjaro-xfce-25-minimal-250330-linux612.iso' completed successfully.

==> Done [Build ISO]
 --> Time compress_images: 2.17 minutes
==> Finished building [xfce]
 --> Time make_profile: 4.72 minutes

possible gotcha

The most obvious problem may be the writing to USB. The command may exit early but the file system buffer data is still being flushed to USB. If the USB is removed before all data is flushed - your write will be incomplete and you get error trying to boot.

USB helper package

We have a new package in the repo - intended to adjust when the system reports back on write complete.

The package is udev-usb-sync available from all up-to-date mirrors.

iso boot tool

Another valuable tool is ventoy - also in the repo - which provides another method of booting using a regular .iso file stored on the USB.

sudo pacman -Syu udev-usb-sync ventoy

Then prepare an USB stick using the Ventoy2Disk GUI from your application launcher.

When prepared - drag your iso and drop it on the Ventoy partition of the preprared USB.

Boot the system and select your ISO - when selected you have two choices

  • normal mode
  • grub2 mode

Normal mode usually work - but sometimes it doesn’t - making grub2 mode the best choice for an iso build with our tools.

4

Thank you for your response!

I tried waiting for a while after the close of the dd process and it looks like most of my images are bootable. The only issue I ran into was when including specific packages in my Packages-Desktop file in the iso-profile, specifically the following:

  • vagrant
  • docker
  • docker-machine
  • docker-compose
  • virtualbox
  • virt-manager
  • virt-viewer

Not sure why, but when I try to build with these in the build, I get the following error:

Warning: /lib/modules/5.4.291-1-MANJARO/modules.devname not found - ignoring
ERROR: '/dev/disk/by-label/MANJARO-XFCEM_2500' device did not show up after 30 seconds...
  Falling back to interactive prompt
  You can try to fix the problem manually, log out when you are finished
sh: can\'t access tty; job control turned off
[rootfs ~]#

I’ll keep performing runs to make sure this isn’t just a coincidence, but my ideal ISO build doesn’t even need these applications so I am considering this matter closed. Thanks for the help! One of my favourite things about Manjaro is that it has a tool to build custom ISOs that works really well.

5

When a Support topic you open has been solved, members are expected to mark the post that helped them the most accordingly.

There is a Solution button under each post designed for this purpose; Simply:

…doesn’t indicate to others that a topic has reached its conclusion. Without this, a topic might continue pointlessly while well-intentioned members continue to add their commentary.

I have marked the appropriate (and obvious) solution post in your absence.

Regards.

6

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