PXE boot - Reopening Network Devices - Kernel Panic
-
Hi all, and thanks in advance for your help.
I have read the Wiki (though I admit I may have missed something or that some of that documentation may have been out of date).
Here is my environment:
Fog 1.0.1 on Ubuntu 14.04 in a KVM VM
DNS/DHCP on Ubuntu 14.04 in a KVM VM
I have also tried DHCP from a Win2012std Server in a VM.
I have used multiple kernels from the published and unpublished list, and compiled my own kernel (Using 3.14.4 and following the directions on the Wiki, but modifying to comply with the change from using the /tftpboot/fog/kernel/ folder to /var/www/fog/service/ipxe/) to include the drivers I need (Intel i810 and Intel network cards) for my Dell Optiplex 780s. I have tried using Tom’s kernels in both x64 and x86.Here’s what works so far:
I can PXE Boot and get the FOG menu.
That’s where things go wrong-
When I select the compatibility check option or schedule a task for the machine from the FOG WebUI, I get the following. For search purposes, I’ll add the text here as well as add a screenshot.[CODE]Decompressing Linux… Parsing ELF… done.
Booting the Kernel.
IP-config: Reopening network devices…
IP-Config: Auto-Configuration of network failed
Starting init: /sbin/init exists but couldn’t execute it (error -8)
Starting init: /bin/sh esists but couldn’t execute it (error -8)
Kernel Panic - not syncing: No working init found. Try passing init= option to kernel.[/CODE]Etc…
So, to my untrained eye it appears that while booting the kernel, the machine tries to initialize the network card and fails. During this time, the “Link light” on the front of the machine (a feature of the 780 desktop models) goes off and back on as if the card is cycled off and on to initialize. At this point, it either can’t initialize the network card or the DHCP server doesn’t respond. My initial setup had an Ubuntu 14.04 server running ISC-DHCP… I have tried it as straight DHCP and I have tried setting a static address in the dhcpd.conf file. Both of which worked to get the PXE boot to work, but not enough to actually boot the linux kernel to do any operations . I then tried a Win2012STD server in a KVM VM as a DHCP server which, again, hands out addresses just fine, but does not resolve my issue.
So given all this information, I think I’m probably missing a simple init= string or something that is fairly obvious, but i’m lost looking at the trees and can’t see the forest at this point. 3 days of Google, reading the forums here and trial and error hasn’t produced any results. Hopefully some of the gang here can give me a hand.
[ATTACH]858[/ATTACH]
Thanks again![url=“/_imported_xf_attachments/0/858_2014-05-29 12.13.11.jpg?:”]2014-05-29 12.13.11.jpg[/url]
-
I have continued trying different things and have made some changes worth noting.
I have changed to using the undionly.kpxe (f473) released by Tom, and it seems to have changed the behavior of “Reopening Network devices”. That’s the good news.
The bad news is that the kernel panic happens much more quickly now.
So I changed kernel to an older version, now the kernel panic gives me a message of
“Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0).”
I can ping the address assigned to the PXE now (not sure if I could before… never tried)… even with the kernel panic.Any help will be greatly appreciated.
-
[quote=“loudroar, post: 28563, member: 24384”]I have continued trying different things and have made some changes worth noting.
I have changed to using the undionly.kpxe (f473) released by Tom, and it seems to have changed the behavior of “Reopening Network devices”. That’s the good news.
The bad news is that the kernel panic happens much more quickly now.
So I changed kernel to an older version, now the kernel panic gives me a message of
“Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0).”
I can ping the address assigned to the PXE now (not sure if I could before… never tried)… even with the kernel panic.Any help will be greatly appreciated.[/quote]
It sounds like you’re using a 64bit kernel with a 32 bit init, or vice versa (32bit kernel with a 64 bit init)
FOG 1.X.X will not load if the archs don’t match.
bzImage is (default install) 64bit
init.xz is 64bit
bzImage32 is (default install) 32bit
init_32.xz is 32bit.If you’re changing kernels around you have to be cognizant of these two things.
-
Tom, you are a scholar and a gentleman…
Thank you!I made a backup copy of each of my init.xz and init_32.xz files (copied to init.xz.bak and init_32.xz.bak), then renamed my init_32.xz file to init.xz and selected your Kernel - 3.14.4 (x86) TomElliott as my bzImage file.
The computer successfully booted and ran the inventory job I scheduled.
