From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Problem with building cdrom step
Date: Tue, 3 Mar 2026 11:09:41 +0000 [thread overview]
Message-ID: <0482A60D-B785-47AC-AE30-09CFAA9CAB67@ipfire.org> (raw)
In-Reply-To: <00fa6d59-93f4-49d8-8c0a-1ae0bf695840@ipfire.org>
Hello Adolf,
Oh, my favourite hobby, loop devices in containers. They are such fun.
I would most likely expect the kernel to have added any restrictions, but in a release cycle, this would be a very surprising.
Could you do the following for me:
* Enter the shell with ./make.sh shell
* Create a temporary file: dd if=/dev/zero of=/tmp/test.img bs=1k count=2880
* Put a FAT32 filesystem on it: mkdosfs -F 12 -n "IPFIRE_EFI” test.img
* Mount the image: mount -o loop test.img /mnt, this should fail
* And so that we have some debugging information, could you run the mount comment with strace in front of it, so that we see which syscall it is that is failing.
-Michael
> On 3 Mar 2026, at 11:04, Adolf Belka <adolf.belka@ipfire.org> wrote:
>
> Hi All,
>
> I mentioned this issue in yesterday's conf call. I was still waiting for the results of a complete standard set of packages based on a git pull from morning of 2nd March.
> That also failed in cdrom.
>
> I had a working build on 27th Feb and the only IPFire package updates since then are the ones I built on the 27th Feb.
>
> However my Arch Linux system has had an update on 2nd March just before I did my build so the issue may be coming from those updates.
>
> The error message I get is the following:
>
> # Build a GRUB EFI image
> mkdir -pv /tmp/cdrom/EFI/BOOT
> mkdir: created directory '/tmp/cdrom/EFI'
> mkdir: created directory '/tmp/cdrom/EFI/BOOT'
> grub-mkimage \
> --format=x86_64-efi \
> --output=/tmp/cdrom/EFI/BOOT/bootx64.efi \
> --config=/tmp/grub-efi.cfg \
> --compression=xz \
> --prefix=/EFI/BOOT \
> $(for mod in all_video at_keyboard boot bitmap_scale cat chain configfile disk echo efi_gop efi_uga ext2 extcmd fat file font fxterm_menu gfxterm gfxmenu gfxterm_background gzio halt help iso9660 jpeg loadbios loadenv loopback linux ls memdisk minicmd nativedisk normal ntfs part_gpt part_msdos png probe reboot regexp search search_fs_file search_fs_uuid search_label tar test tga true usb_keyboard; do [ -f "/usr/lib/grub/x86_64-efi/${mod}.mod" ] && echo "${mod}"; done)
> # Install GRUB configuration
> mkdir -pv /tmp/cdrom/EFI/BOOT
> sed -e "s/NAME/IPFire/g" -e "s/VERSION/2.29/g" -e "s/ARCH/x86_64/g" \
> < /usr/src/config/cdrom/grub.cfg > /tmp/cdrom/EFI/BOOT/grub.cfg
> # Create the EFI Eltorito image
> dd if=/dev/zero of=/tmp/cdrom/boot/isolinux/efiboot.img bs=1k count=2880
> 2880+0 records in
> 2880+0 records out
> 2949120 bytes (2.9 MB, 2.8 MiB) copied, 0.0038391 s, 768 MB/s
> mkdosfs -F 12 -n "IPFIRE_EFI" /tmp/cdrom/boot/isolinux/efiboot.img
> mkfs.fat 4.2 (2021-01-31)
> # Mount the EFI image
> mkdir -pv /tmp/efiboot.img
> mkdir: created directory '/tmp/efiboot.img'
> mount -o loop /tmp/cdrom/boot/isolinux/efiboot.img /tmp/efiboot.img
> mount: /tmp/efiboot.img: failed to setup loop device for /tmp/cdrom/boot/isolinux/efiboot.img.
> make: *** [cdrom:188: /usr/src/log/cdrom] Error 32
> make: Leaving directory '/usr/src/lfs'
>
> The Arch Linux update had a lot of changes. The update prior to that one was 5 days ago.
> Here is a list of the update changes in the various packages. Not sure if any of those could be causing the problem of not being able to setup the loop device.
>
> upgraded iana-etc (20260203-1 -> 20260225-2)
> upgraded systemd-libs (259.1-1 -> 259.2-1)
> upgraded libngtcp2 (1.20.0-1 -> 1.21.0-1)
> upgraded ca-certificates-mozilla (3.120.1-1 -> 3.121-1)
> upgraded file (5.46-5 -> 5.47-1)
> upgraded systemd (259.1-1 -> 259.2-1)
> upgraded accountsservice (23.13.9-3 -> 25.34.76-2)
> upgraded adwaita-fonts (49.0-2 -> 50.0-1)
> upgraded libksba (1.6.7-2 -> 1.6.8-1)
> upgraded archlinux-keyring (20260206-1 -> 20260301-1)
> upgraded libmaxminddb (1.12.2-2 -> 1.13.2-1)
> upgraded bind (9.20.19-1 -> 9.20.20-1)
> upgraded bluez (5.86-2 -> 5.86-4)
> upgraded bluez-libs (5.86-2 -> 5.86-4)
> upgraded bluez-utils (5.86-2 -> 5.86-4)
> upgraded bubblewrap (0.11.0-1 -> 0.11.0-2)
> upgraded compiler-rt (21.1.8-1 -> 21.1.8-2)
> upgraded deno (2.6.10-1 -> 2.7.1-1)
> upgraded dtkcommon (5.7.30-1 -> 6.7.31-1)
> upgraded nss (3.120.1-1 -> 3.121-1)
> upgraded v4l-utils (1.32.0-1 -> 1.32.0-2)
> upgraded mesa (1:25.3.5-1 -> 1:26.0.1-1)
> upgraded xkeyboard-config (2.46-1 -> 2.47-1)
> upgraded firefox (147.0.4-1 -> 148.0-1)
> upgraded firefox-i18n-en-gb (147.0.4-1 -> 148.0-1)
> upgraded fmt (12.1.0-1 -> 12.1.0-2)
> upgraded gstreamer (1.28.0-2 -> 1.28.1-1)
> upgraded gst-plugins-base-libs (1.28.0-2 -> 1.28.1-1)
> upgraded gst-libav (1.28.0-2 -> 1.28.1-1)
> upgraded gst-plugins-bad-libs (1.28.0-2 -> 1.28.1-1)
> upgraded gst-plugins-base (1.28.0-2 -> 1.28.1-1)
> upgraded gst-plugins-good (1.28.0-2 -> 1.28.1-1)
> upgraded mdadm (4.4-2 -> 4.5-2)
> upgraded gvfs (1.58.1-1 -> 1.58.2-1)
> upgraded gvfs-mtp (1.58.1-1 -> 1.58.2-1)
> upgraded intel-media-driver (25.3.4-2 -> 25.4.6-1)
> upgraded ldb (2:4.23.5-1 -> 2:4.23.6-1)
> upgraded libfyaml (0.9.4-1 -> 0.9.5-1)
> upgraded libldac (2.0.2.3-2 -> 2.0.2.3-3)
> upgraded libwbclient (2:4.23.5-1 -> 2:4.23.6-1)
> upgraded linux (6.18.9.arch1-2 -> 6.18.13.arch1-1)
> upgraded linux-headers (6.18.9.arch1-2 -> 6.18.13.arch1-1)
> upgraded lzip (1.25-2 -> 1.25-3)
> upgraded nodejs (25.6.1-2 -> 25.7.0-1)
> installed openjph (0.26.3-3)
> upgraded openexr (3.4.5-1 -> 3.4.6-1)
> upgraded openmpi (5.0.9-4 -> 5.0.10-1)
> upgraded python-chardet (5.2.0-7 -> 6.0.0.post1-1)
> upgraded python-requests (2.32.5-3 -> 2.32.5-4)
> upgraded smbclient (2:4.23.5-1 -> 2:4.23.6-1)
> upgraded samba (2:4.23.5-1 -> 2:4.23.6-1)
> upgraded systemd-sysvcompat (259.1-1 -> 259.2-1)
> upgraded thunderbird (147.0.2-1 -> 148.0-4)
> upgraded thunderbird-i18n-en-gb (147.0.2-1 -> 148.0-4)
> upgraded vim-runtime (9.2.0038-1 -> 9.2.0081-1)
> upgraded vim (9.2.0038-1 -> 9.2.0081-1)
> upgraded virtualbox-host-modules-arch (7.2.6-4 -> 7.2.6-5)
> upgraded vulkan-mesa-implicit-layers (1:25.3.5-1 -> 1:26.0.1-1)
> upgraded vulkan-radeon (1:25.3.5-1 -> 1:26.0.1-1)
> upgraded wxwidgets-common (3.2.9-4 -> 3.2.10-1)
> upgraded wxwidgets-gtk3 (3.2.9-4 -> 3.2.10-1)
> upgraded zed (0.224.11-1 -> 0.225.10-1)
>
> Any suggestions for how to fix this gladly accepted.
>
> Regards,
>
> Adolf.
>
next prev parent reply other threads:[~2026-03-03 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 11:04 Adolf Belka
2026-03-03 11:09 ` Michael Tremer [this message]
2026-03-03 11:56 ` Adolf Belka
2026-03-03 12:24 ` Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0482A60D-B785-47AC-AE30-09CFAA9CAB67@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox