I figured it had to have been me (but a good chunk of the 20 downloads was actually me), but of course it is the simplest solution. I just unzipped the archive. Haven’t written it to disk yet, but I am sure it is fine. Thank you for the quick reply. I do have another issue when trying to build the image:
I attempted to build the Volumio image in WSL2 Debian Bookworm using the following command:
sudo ./build.sh -b arm -d pi -v 4.010
However, I ran into the following error:
[ .... ] Stage [2]: Creating Image
[ .. ] Image file: .//Volumio-4.010-2025-06-03-pi.img
[ .. ] Using DEBUG_IMAGE: no
4683+0 records in
4683+0 records out
4910481408 bytes (4.9 GB, 4.6 GiB) copied, 3.97863 s, 1.2 GB/s
Error: Partition(s) 1, 2, 3, 4, ... 64 on /dev/loop2 have been written, but we have been unable to inform the kernel of the change, probably because they are in use.
As a result, the old partitions will remain in use. You should reboot now before making further changes.
[ error ] Imagebuilder script failed!!
[ error ] Error stack [source] <= [main] <= [ 65 /home/sean/build/scripts/makeimage.sh ]
[ .. ] Unmounting chroot temporary devices at
umount: /sys: umount failed: No such file or directory.
[ warn ] umount sys failed
[ .. ] Cleaning loop device /dev/loop2
/proc/devices: fopen failed: No such file or directory
Failed to set up list of device-mapper major numbers
Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown version).
Command failed.
Steps Taken:
- Tried running the build multiple times.
- Ensured there were no other processes locking
/dev/loop2
. - Verified my WSL2 setup and checked for missing dependencies.
Questions:
- Has anyone successfully built the Volumio image in WSL2 Debian Bookworm?
- Could the partition error be related to WSL2’s virtualized kernel limitations?
- Are there recommended workarounds for handling loop device errors in WSL2?
Would love any insights from the community! Thanks for your help.