[GH-ISSUE #1664] Incomplete asset downloads #562

New issue

Open

opened 2026-02-27 14:52:14 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 14:52:14 +03:00

Owner

Originally created by @CompPhy on GitHub (Aug 20, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1664

[X]: This bug persists when memory is increased beyond 8GB.

Describe the bug
I'm attempting to use the new Proxmox 9 ISO and I keep getting I/O errors when the boot loader tries to mount the ISO. I started looking at the asset files and notice that the file was smaller (1.2GB) than the size listed on their download page (1.6GB).

I don't think this is an issue with the target device, it's got plenty of physical memory (32GB) and seems to be getting the asset from netboot just fine. It shows 100% download of the ISO asset at boot time.

I was able to download the file through another machine and then manually copy into my Netboot XYZ assets. After which point I was able to boot the installer properly without errors.

To Reproduce
Steps to reproduce the behavior:

Pull the assets for Proxmox 9.
- This is especially slow on my internet provider for some reason, maybe netboot is timing out the download?
- Examine netboots asset files and see that file size is too small.
- I did not get any error in the UI, and it shows the iso as a tracked asset file.
Boot through netboot.xyz and select Proxmox 9 from menus.
Bootloader starts, but then fails to mount the ISO properly.

Expected behavior

The download should tell you if it didn't complete properly, instead of keeping a bad asset in the inventory.
There should be a way to verify things like md5sum, size, etc. through the UI.
Even looking at logs on my container, (I am running netboot xyz through docker/truenas), I don't see any indication that it thought the download failed. It's happily serving up a file that's not complete.

Screenshots
I don't have a good way to get screen shots, as this is a bare metal desktop machine. However, here are the errors I'm getting, which I think are both related to a corrupt ISO file.

mounting /dev/loop2 on /mnt/.installer failed: Input/output error

[ERROR] mount '/mnt/pve-installer.squashfs' failed

Additional context

Originally created by @CompPhy on GitHub (Aug 20, 2025). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1664 [X]: This bug persists when memory is increased beyond 8GB. **Describe the bug** I'm attempting to use the new Proxmox 9 ISO and I keep getting I/O errors when the boot loader tries to mount the ISO. I started looking at the asset files and notice that the file was smaller (1.2GB) than the size listed on their download page (1.6GB). I don't think this is an issue with the target device, it's got plenty of physical memory (32GB) and seems to be getting the asset from netboot just fine. It shows 100% download of the ISO asset at boot time. I was able to download the file through another machine and then manually copy into my Netboot XYZ assets. After which point I was able to boot the installer properly without errors. **To Reproduce** Steps to reproduce the behavior: 1. Pull the assets for Proxmox 9. - **This is especially slow on my internet provider for some reason, maybe netboot is timing out the download?** - Examine netboots asset files and see that file size is too small. - I did not get any error in the UI, and it shows the iso as a tracked asset file. 2. Boot through netboot.xyz and select Proxmox 9 from menus. 3. Bootloader starts, but then fails to mount the ISO properly. **Expected behavior** 1. The download should tell you if it didn't complete properly, instead of keeping a bad asset in the inventory. 2. There should be a way to verify things like md5sum, size, etc. through the UI. 3. Even looking at logs on my container, (I am running netboot xyz through docker/truenas), I don't see any indication that it thought the download failed. It's happily serving up a file that's not complete. **Screenshots** I don't have a good way to get screen shots, as this is a bare metal desktop machine. However, here are the errors I'm getting, which I think are both related to a corrupt ISO file. **mounting /dev/loop2 on /mnt/.installer failed: Input/output error** **[ERROR] mount '/mnt/pve-installer.squashfs' failed** **Additional context**