FOG Registration for Dell Optiplex 3630 Errors
-
Hello everyone,
As a follow-up from my previous thread, I am having trouble registering a new model of computer in FOG. Other computers register and images upload and deploy just fine, it’s just this new model. I’m working with the Dell Precision 3630 on this.
I can boot to PXE, obtain an IP Address, and get to the basic FOG menu no problem. From here, we typically do a Full Host Registration and Inventory before attempting to deploy any images, so that we have the host registered and trackable. We also use this for automating items like Hostname Changer and Active Directory domain joining.
Once I get to the basic FOG menu, I select the option for Full Host Registration and Inventory, and I am greeted with the error in the screenshot at the bottom of this post.
At first, I believed this to be related to a kernel, so I did update the kernel as noted in my previous post. This did not correct the error at all.
My kernel is now on version 4.19.36 TomElliott (May 1, 2019) and I’m using FOG version 1.4.4, SVN version 6077.
In the previous thread that I’m migrating this issue from, @george1421 suggested that I cancel any tasks I have assigned to the host and push the “Debug” task to it. I have been unable to do this, as I have not even been able to register the host in order to assign any tasks thus far. I’m just trying to get through host registration first.
EDIT: Typos corrected.
-
@kenneth-sisco said in FOG Registration for Dell Optiplex 3630 Errors:
In the previous thread that I’m migrating this issue from, @george1421 suggested that I cancel any tasks I have assigned to the host and push the “Debug” task to it. I have been unable to do this, as I have not even been able to register the host in order to assign any tasks thus far. I’m just trying to get through host registration first.
Crud I missed a step. Manually register that new computer with the fog server by making a host record for it. Make sure you have the mac address of the NIC handy then schedule a debug capture or deploy (doesn’t matter for this test).
And in the fwiw bucket, my work computer is a Precision 3630 so I have something I can test against if absolutely necessary.
-
Thanks @george1421 . I manually registered the client via Mac Address in FOG and pushed the Debug task to it. When booting into the task, I get the same error message. See the screenshot below. This is what makes me think I need an updated kernel.
EDIT: I’m a dumb-dumb. If I press Enter a few times, I get to the debug prompt as expected.
-
So I realized if I simply press Enter a few times at that error, I still get the debug prompt. So I tested the commands, as recommended:
ip addr show
lspci -nn|grep -i netBelow are the results of these commands!
-
@kenneth-sisco ok from the commands we can see a few things.
- The network driver is not loading since there is no eth0
- The network adapter is a 8086:155b or an Intel e1000 based network controller. I checked and that network adapter has been in the linux kernel since 4.12
uname -awill display the current kernel version. But I’m sure the FOS Linux kernel is after that version.FWIW: the 5i5 nuk I have on my desk that is running centos 3.10 linux kernel has a network hardware id of 8086:15a3 which is listed as a I218-V adapter.Comment redacted: I’m getting my posted mixed up. There is another thread where an Intel NUC has an issue with the network interface.
I wonder if you were to run this command
grep e1000 /var/syslogif that would show any errors related to the e1000 network adapter. -
Thanks @george1421 ! I ran those commands, and I think the /var/syslog might be for RHEL where I’m on Ubuntu 16.04 LTS.
But your point on the kernel version is interesting, as I’m only on version 4.11. I thought I had updated to 4.19 yesterday in the Kernel Update thread.
So to test this a bit further, I ran the FOG kernel update again and rebooted this machine into Debug mode. The kernel update that the FOG management page says I’m installing is 4.19. The update succeeded without error. Rebooted the client into its debug task, and ran uname -a again, and still only see version 4.11.
-
I don’t know if this is helpful or not, but I found some e1000 references in the /var/log/messages file. Did not see a syslog file anywhere.
-
@kenneth-sisco Ok that is good (being on 4.11), well not really but explains why the network adapter isn’t working. Remember that the kernel is booting from the USB flash stick. So its the bzImage and bzImage32 on the flash stick that counts here. So you need to update the usb flash stick from here: https://fogproject.org/kernels/
Grab Kernel.TomElliott.4.19.36.64 and save it as /boot/bzImage on the flash drive.
Also grab Kernel.TomElliott.4.19.36.32 and save it as /boot/bzImage32 on the flash drive, replacing the files that are there.Remember that case IS important.
As far as files and paths, I’m a RHEL guy so I have a certain slant on things and file paths. The debian variants (where FOS Linux is) confuse me a bit, i can get you into the ballpark but you will have to find the bases. Its good you were able to fine what you needed in /var/log/messages.
-
@george1421 Thanks for the heads-up. I’m not using any USB flash sticks – I’m using a PXE boot setup. So would these need to go in /tftpboot on the server instead? Or another location?
-
@kenneth-sisco Ugh, I’m mixing up my thread again. Sorry. The files go in /var/www/html/fog/service/ipxe directory. You should be able to update the kernels using the FOG Settings menu.
-
Yup that did it! I was in the middle of copying files up to the server when you replied. Put them in that directory and rebooted and the errors went away. We’re good to go.
Thanks for the help @george1421 . Feel free to mark this one as solved.
-
@kenneth-sisco I know it took you a long way to get here, but its great when you can pinpoint the root of the error and fix it knowing that its not just some random crud that may reappear when it will hurt the most.
