From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robin Roevens To: development@lists.ipfire.org Subject: Re: Unable to build cdrom: failed to setup loop device Date: Wed, 04 Sep 2024 22:58:30 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3537028708316336878==" List-Id: --===============3537028708316336878== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael Michael Tremer schreef op wo 04-09-2024 om 21:38 [+0200]: > Hello Robin, >=20 > > On 4 Sep 2024, at 20:53, Robin Roevens > > wrote: > >=20 > > Hi all > >=20 > > While trying to build ipfire, which always has worked quite > > effortless, > > it now fails while building cdrom: > >=20 > > --- > > =C2=A0=C2=A0 # Create the EFI Eltorito image > > =C2=A0=C2=A0 dd if=3D/dev/zero of=3D/tmp/cdrom/boot/isolinux/efiboot.img = bs=3D1k > > count=3D2880 > > =C2=A0=C2=A0 2880+0 records in > > =C2=A0=C2=A0 2880+0 records out > > =C2=A0=C2=A0 2949120 bytes (2.9 MB, 2.8 MiB) copied, 0.00453183 s, 651 MB= /s > > =C2=A0=C2=A0 mkdosfs -F 12 -n "IPFIRE_EFI" > > /tmp/cdrom/boot/isolinux/efiboot.img > > =C2=A0=C2=A0 mkfs.fat 4.2 (2021-01-31) > > =C2=A0=C2=A0 # Mount the EFI image > > =C2=A0=C2=A0 mkdir -pv /tmp/efiboot.img > > =C2=A0=C2=A0 mkdir: created directory '/tmp/efiboot.img' > > =C2=A0=C2=A0 mount -o loop /tmp/cdrom/boot/isolinux/efiboot.img > > /tmp/efiboot.img > > =C2=A0=C2=A0 mount: /tmp/efiboot.img: failed to setup loop device for > > /tmp/cdrom/boot/isolinux/efiboot.img. > > =C2=A0=C2=A0 make: *** [cdrom:184: /usr/src/log/cdrom] Error 32 > > =C2=A0=C2=A0 make: Leaving directory '/usr/src/lfs' > >=20 > > ERROR: Building > > cdrom=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=20 > > [ FAIL ] > > =C2=A0=C2=A0 Check /home/robin/src/ipfire-sandbox/ipfire- > > 2.x/log_x86_64/_build.ipfire.log for errors if > > applicable=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=20 > > [ FAIL ] > > --- >=20 > What is the output of =E2=80=9Closetup=E2=80=9D after this fails? Just a list snap files mounted by snapd. Nothing from ipfire. >=20 > > The logfile has no extra or new information. > >=20 > > When I manually try those steps, as root (as make.sh is also ran as > > root (using sudo)), they work correctly, and I'm able to > > successfully > > mount the image. >=20 > Does this also work in shell? Yes, it works also in a root shell. >=20 > >=20 > > --- > > $ sudo dd if=3D/dev/zero of=3D./efiboot.img bs=3D1k count=3D2880=20 > > 2880+0 records gelezen > > 2880+0 records geschreven > > 2949120 bytes (2,9 MB, 2,8 MiB) gekopieerd, 0,0130511 s, 226 MB/s > > $ sudo ./build/sbin/mkdosfs -F 12 -n "IPFIRE_EFI" ./efiboot.img > > mkfs.fat 4.2 (2021-01-31) > > $ sudo mkdir ./efi > > $ sudo mount -o loop ./efiboot.img ./efi > > $ df -h > > ./efi=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=20 > > Bestandssysteem Grootte Gebruikt Besch Geb% Aangekoppeld op > > /dev/loop15=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2,8M=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0 2,8M=C2=A0=C2=A0 0% /home/robin/src/ipfir= e- > > sandbox/ipfire-2.x/efi > > --- > >=20 > > So I'm unsure as of why the build fails setting up the loop device. > > I did a ./make.sh clean, but that didn't solve it. > >=20 > > If I try to mount the loop device as unprivileged user, I get the > > exact > > same error. But the build process is ran as root, so that should > > also > > not be the problem? >=20 > It creates new namespaces in which root is less privileged than in > the first namespace. Can it be that there is some leftover somewhere from older builds when it had more privileges? Not that I can imagine what could still be there that it now prevents mounting a freshly created file on loopback. >=20 > > Has anyone an idea what could be wrong here? or give me some > > guidelines > > on how to debug this ?=20 > > I've read there where changes to the inner workings of the build > > system, could those be the cause ? I assume not as then I would > > have > > seen others complain about it here? >=20 > Apart from that, as Adolf requested, please provide us with some more > information about your kernel and distribution. I'm running openSUSE Tumbleweed on kernel 6.10.5. >=20 > -Michael >=20 > > Robin >=20 --===============3537028708316336878==--