[GH-ISSUE #1603] Local Assets on docker latest image missing filesystem.squashfs.part2 for downloads nor will they fully boot #2069

New issue

Closed

opened 2026-03-01 18:38:17 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 18:38:17 +03:00

Owner

Originally created by @rickgitdone on GitHub (Mar 30, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1603

Describe the bug

Using the latest docker image from ghcr.io/netbootxyz/netbootxyz, with Remote Assets at 2.0.86 Menus
the listings for any assets with a filesystem.squashfs.part2 is not listed for downloads
To Reproduce
Steps to reproduce the behavior:

Go to "Local Assets" Item on for http://[local-IP or localhost]:3000/

Expected behavior
A listing item to download the .part2 of any required squashfs.part2 needed to fully boot the kernel and filesystem is required to match the release assets of the Live OS to be net booted

Screenshots

Additional context

none of the Live OS versions where the assets have a part2 listed in the assets sections boot fully since part2 is not being downloaded again as reported previously here issue #1068

as a test I made a concatenated squashfs that is now /root mounted and shown in the screen shot ... the kernel is reporting no valid interfaces found?

I have downloaded both
https://github.com/netbootxyz/ubuntu-squash/releases/download/20250323-0744-9b372e2a/filesystem.squashfs
https://github.com/netbootxyz/ubuntu-squash/releases/download/20250323-0744-9b372e2a/filesystem.squashfs.part2

both must be concatenated together 1st to even make a valid squashfs then the resultant file can be used as a /root filesystem for the kernel on boot. So why were these assets implemented this way since there is no path on the netboot process to perform this action during pxe process?

Originally created by @rickgitdone on GitHub (Mar 30, 2025). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1603 **Describe the bug**  Using the latest docker image from ghcr.io/netbootxyz/netbootxyz, with Remote Assets at [2.0.86](https://github.com/netbootxyz/netboot.xyz/releases/2.0.86) Menus the listings for any assets with a filesystem.squashfs.part2 is not listed for downloads **To Reproduce** Steps to reproduce the behavior: 1. Go to "Local Assets" Item on for http://[local-IP or localhost]:3000/ **Expected behavior** A listing item to download the .part2 of any required squashfs.part2 needed to fully boot the kernel and filesystem is required to match the release assets of the Live OS to be net booted **Screenshots**  ![Image](https://github.com/user-attachments/assets/33c8df12-1ceb-41a0-be3b-d9ad07e9e7b6) **Additional context**  none of the Live OS versions where the assets have a part2 listed in the assets sections boot fully since part2 is not being downloaded again as reported previously here [issue #1068](https://github.com/netbootxyz/netboot.xyz/issues/1068) as a test I made a concatenated squashfs that is now /root mounted and shown in the screen shot ... the kernel is reporting no valid interfaces found? I have downloaded both https://github.com/netbootxyz/ubuntu-squash/releases/download/20250323-0744-9b372e2a/filesystem.squashfs https://github.com/netbootxyz/ubuntu-squash/releases/download/20250323-0744-9b372e2a/filesystem.squashfs.part2 both must be concatenated together 1st to even make a valid squashfs then the resultant file can be used as a /root filesystem for the kernel on boot. So why were these assets implemented this way since there is no path on the netboot process to perform this action during pxe process?

kerem

2026-03-01 18:38:17 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-01 18:38:17 +03:00

Author

Owner

@rickgitdone commented on GitHub (Mar 30, 2025):

disregard... the issue is not the squashfs which appears to be no valid interfaces found ... If I load an ISO into VBOX the install to VM also fails to boot on my hardware.

@rickgitdone commented on GitHub (Mar 30, 2025): disregard... the issue is not the squashfs which appears to be no valid interfaces found ... If I load an ISO into VBOX the install to VM also fails to boot on my hardware.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#2069

No description provided.

Rows
Columns