mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 23:25:54 +03:00
[GH-ISSUE #1157] arch iso fails to boot due to wrong dns (0.0.0.0) #318
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#318
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @berinaniesh on GitHub (Sep 16, 2022).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1157
Using netboot.xyz.efi with manual network configuration and dns 8.8.8.8, it downloads the initrd and kernel (I guess) and boots, then proceeds to download the root file system, but download fails due to wrong dns. It sets the dns to 0.0.0.0 itself.
@berinaniesh commented on GitHub (Sep 16, 2022):
Ubuntu ISO works fine, please don't mind if the issue is with archlinux's ISO.
@oe3gwu commented on GitHub (Mar 12, 2023):
I cant relate tho that. As you see in the 2nd picture, my DNS is correct (192.168.1.10). I am running Netboot on a Docker (no Host Network). As DNS I user a Pi Hole with a DHCP Helper.
Boot works fine for me of all components. I didnt test Arch further, because I really hate it.
@cicku commented on GitHub (Mar 13, 2023):
The workaround is to
echo "nameserver 1.1.1.1" > /etc/resolv.confAppears to be a busybox bug with static IP.
@berinaniesh commented on GitHub (Mar 31, 2023):
It just drops me to the emergency shell, can it be done with emergency shell?
@berinaniesh commented on GitHub (Mar 31, 2023):
Tried it yesterday, with manual ip address (non dhcp) and it failed.
Used netboot.xyz.efi
hit m to failsafe mode, entered network ip, gateway and dns manually,
initramfs downloads fine, when the rootfs downloads, it fails and drops to emergency shell.
@bartenbach commented on GitHub (Apr 15, 2023):
Same issue. DNS doesn't resolve a hostname and I end up in an emergency shell.
Ironically it downloads the kernel and initramfs img just fine from the same host and then seconds later claims it can't resolve that hostname.
@bartenbach commented on GitHub (Apr 16, 2023):
Agree. I can set the DNS server and grab the file but then what?
@bartenbach commented on GitHub (Apr 17, 2023):
Tried to just log out after adding DNS server to resolv.conf as the text suggests, but no luck there. Found a file in /tmp that clearly doesn't have the DNS servers that you can verify are present in the netboot network settings menu initially.
After this, it appears to continually try and execute the next line of some script and turns into an error message generator.
@ryester19 commented on GitHub (Sep 9, 2023):
Is there a related bugreport on the Busybox's Bigzilla page that we can monitor?
@antonym commented on GitHub (Sep 9, 2023):
I can adjust the kernel command line to put DNS entries if there's a place in the loader that can pull them out, I haven't managed to find it yet tho. I tried a few iterations of ip= but that didn't seem to work.
@bartenbach commented on GitHub (May 16, 2024):
I was looking at this too but found no solution.
I'm back at this same problem over a year later. The devs might as well just remove Arch from the list and admit that it doesn't work. It's essentially just marketing at this point. They just have a big list of items that probably don't work to make the app sound more useful/important than it actually is.
If you can avoid netboot, you can install Arch just fine.
@berinaniesh commented on GitHub (May 16, 2024):
Only manual network configuration is a problem. Automatic configuration works just fine @bartenbach. BTW, the problem still persists. Tried a week before.
@antonym commented on GitHub (May 17, 2024):
I'm open to suggestions for fixing manual config, automatic works just fine however as I installed Arch with it this week.
@zwogorg commented on GitHub (Apr 4, 2025):
Error still persists; here's a workaround, though:
Wait for the download of
airootfs.sfsto fail. Set nameserver manually:echo "nameserver 9.9.9.9" > /etc/resolv.conf(this is Quad9, change to whatever DNS you like. It's only used until Archiso is booted, though)Restart the download of
airootfs.sfsinto working dir/run/archiso/httpspace/arch/x86_64:wget -P /run/archiso/httpspace/arch/x86_64/ http://mirrors.edge.kernel.org/archlinux/iso/2025.04.01/arch/x86_64/airootfs.sfsNow run
exitto leave the emergency shell and the process should continue. Install Arch as always.