mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 15:15:56 +03:00
[GH-ISSUE #248] CentOS 7 fails to install on Supermicro HW #1647
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#1647
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 @xmovu on GitHub (Jul 6, 2018).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/248
Hi guys,
Getting the following error installing CentOS 7, I've no idea why.
It's not an isolated event. I've been unable to get netboot.xyz to install CentOS 7 on several E3, Supermicro servers.
Network is configured, not by DHCP but manually.
Any idea?
Cheers
@antonym commented on GitHub (Jul 6, 2018):
Made some changes to see if this can be handled better. Since you were able to load iPXE to bring up the menu and start the installer, this patch uses that same MAC that got on the network and attempts to reuse it with DHCP.
github.com/antonym/netboot.xyz@b5e0e0f71dIf you don't have DHCP we'd probably have to go another route which would be a bit more complex as we'd need to inject the static networking config into the kernel command line as dracut networking configuration.
@xmovu commented on GitHub (Jul 6, 2018):
Hi Anthony!
Thank you for such amazing tool. This is amazing!
To answer your question, there is no DHCP server. Its all manual configured in terms of network. Since I configure the network when it boots initially it should save the configuration, no? Doesnt make much sense in my perspective. I boot netboot, then it tries to configure with DHCP, it fails, I configure the network manually and it downloads some stuff. I then proceed to install CentOS 7 and this happens. IMHO the network config should be saved as it is normally. Weird thing.
@xmovu commented on GitHub (Jul 6, 2018):
Btw I did try to remove the interface from there or rename it like you have done but it wont work either.
@antonym commented on GitHub (Jul 6, 2018):
Yeah, if you set things up manually, it's set within iPXE. In order for it to pass it to the installer, those values then need to be put on the kernel command line or in most cases, can be set up once inside the installer. The CentOS installer is a bit tricky as it retrieves a rootfs image during the initrd process where it doesn't really prompted for the IP at that point. That's why we'd probably need to pass the settings obtained in PXE and funnel them to the kernel.
@xmovu commented on GitHub (Jul 6, 2018):
Anthony,
Interesting. Thats why it fails... Damn. Does make sense now. So basically without DHCP it fails on all sort of hardware.
@pgera commented on GitHub (Jul 13, 2018):
I'm seeing this too (or it looks similar in that it's some networking issue). Tried to boot fedora today. I know that this used to work about a year ago for the same server and same network. Attaching screenshot.
@pgera commented on GitHub (Jul 13, 2018):
I saw that the commit was for Centos only. I tested Centos, and I was able to get to the installer. So the fix works. Same would apply to Fedora, RHEL and any others in the family too. Thanks.
@antonym commented on GitHub (Jul 13, 2018):
Cool, good to know, will get that applied on the others too.
@antonym commented on GitHub (Jul 16, 2018):
Added this to Fedora and RHEL.
@xmovu commented on GitHub (Jul 31, 2019):
This is fixed as well with #343 .