I'm getting "loopX is not a mountable filesystem" message before failing to build the package when using yay. This is the output I'm getting from prepare():
- Examininging locally available fonts
- Fonts are missing
- Mount filesystems as a non-privileged user: allowed
- Checking for old loop devices created by by this package
- deleting '/dev/loop0'... done.
- Downloading fonts directly
- Mounting HTTP file
file name: 19042.631.201119-0144.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us.iso
host name: software-static.download.prss.microsoft.com
port number: 80
protocol: http
request path: /pr/download/19042.631.201119-0144.20h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x86FRE_en-us.iso
auth data: (null)
file size: 4079597568
- Creating loop device
- Mounting loop device: /dev/loop0
Object /org/freedesktop/UDisks2/block_devices/loop0 is not a mountable filesystem.
- Loop device mounted as ISO at:
- Extracting files from online Windows installation image
7-Zip 26.01 (x64) : Copyright (c) 1999-2026 Igor Pavlov : 2026-04-27
64-bit locale=en_CA.UTF-8 Threads:20 OPEN_MAX:4096, ASM
Scanning the drive for archives:
ERROR: errno=2 : No such file or directory
/sources/install.wim
I noticed that particular message because I get the same message when I run "udisksctl unmount -b /dev/loop0" after the build failure.
Seeing that you mentioned building in a clean chroot in other replies, I tried that too, and it worked probably because loop device was not used:
- Examininging locally available fonts
- Fonts are missing
- Mount filesystems as a non-privileged user: not allowed
- Preparing download of full ISO
...
Do you happen to know what could be causing the error? Not that I care too much because I probably won't have to update this package for a while, but I am curious why this is happening.
Pinned Comments
Zepman commented on 2021-02-24 16:49 (UTC) (edited on 2021-03-24 22:08 (UTC) by Zepman)
This package is based on ttf-ms-win10. It differs in that it automatically downloads the fonts from Microsoft, if possible without downloading an entire ISO file.
If Polkit allows the user to create loop devices and mount files using udisks, around 200 MB of (mostly compressed) data will be downloaded. This can be a slow download method even over the fastest connections, since the fonts are taken from a large ISO file without downloading the entire file.
If Polkit is not available or it does not allow the user to use udisks, the entire ISO file will be downloaded and install.wim will be extracted. A check ensures that enough temporary disk space is available, which can be up to twice the size of the ISO file. This can happen if either Polkit or an authentication agent is not running, or when a user is logged in remotely (e.g. through SSH).