Topics created by Pikmin

@george1421

Sorry for the late reply,1) and 2) are both correct recompiled ipxe.efi works fine

@Pikmin Understand it only needs to be in ahci mode for imaging, once the image is laid down just switch it back to raid-on mode before the first boot of windows. Or if you are not using any raid function, just leave it in ahci mode. There isn’t much of a performance penalty for leaving it in ahci mode.

@astrugatch

It was an upgrade from 16.04, both universe and multiverse are enabled in sources. Good to know
Thanks

SOLVED
Thanks guys, once the certificates were copied to the fog2 server, AD join started working

Yay 🙂

@Sebastian-Roth
Lets say I deploy an image to host1 and join it to the domain. I want to image host2 next, so I thought maybe delete or just rename the host1 to host2 and start the deployment?

Looks like that worked, so I am just renaming the host since I’m using the same mac address

@lucycle
I used to have an issue with some Realtek cards behaving weird and throwing errors in IPXE and later in the boot process, but it’s been a while. With these two HP models and an integrated Realtek card I had to use a different boot firmware, long shot but maybe you can try that?

HP210 Legacy Test

pxe-service=tag:HP210,X86PC, “HP-210 Working”, realtek.kpxe

HP430 UEFI Test

pxe-service=tag:HP430,X86-64_EFI, “HP 430”, realtek.efi

@lucycle said in NFS over TCP not available from x.x.x.x:

In my case the driver in question was dm9601.ko and I also compiled it into my initrd.img which did not fix the issue and behavior persists.

I’ve added another USB dongle, this time a Lenovo 2.0 Ethernet Adapter based on the asix driver, however it didn’t work, then I checked with modinfo and noticed I was missing a dependency (usbnet.ko)

modinfo asix .... depends: mii,usbnet modinfo usbnet filename: /lib/modules/4.15.0-34-generic/kernel/drivers/net/usb/usbnet.ko

Just to be sure, you said initrd.img, I added it to initrd.lz

That’s about all I’ve got to suggest at this point

@sebastian-roth said in FOG server with dhcp client registration:

@Pikmin I don’t like guessing much so we should just take a look at the facts - the packets on the network that is. So get your client ready but don’t start it yet. Go to your FOG server and install tcpdump (sudo apt-get install tcpdump or sudo yum install tcpdump). Then run the following command and substitute x.x.x.x with the client’s IP address: tcpdump -w /tmp/boot_issue.pcap host x.x.x.x

Leave that command sitting there, boot up the client till it shows the error “Either DHCP failed or …”. Now stop tcpdump (Ctrl+c). Upload the generated file /tmp/boot_issue.pcap to your dropbox/google drive and post a link here or send me a private message if you don’t want to share this with the rest of the world.

I just went through the process of doing this when I discovered that after issuing spanning-tree portfast on all the interfaces it appears to be working now, so that’s the solution like in the other thread.
Thanks again for all your help george1421 and Sebastian Roth, I won’t forget the porfast setting ever again

@george1421

Thanks for clearing stuff up with me. Appreciate it

Hey george1421,
Thanks for clearing that up mate

@Wayne-Workman Sure

The content of /etc/subversion/servers on my servers are like this:

[global] http-proxy-host = 192.168.1.56 http-proxy-port = 3128

for git you can issue the following commands (from stackoverflow.com😞
git config --global http.proxy http://192.168.1.56:3128
git config --global https.proxy https://192.168.1.56:3128

If you really wanted to not use env variables, then wget has proxy settings in /etc/wgetrc just uncomment the proxy lines and add the appropriate values and save.

@Tom-Elliott said:

@Pikmin Do you have separate storage nodes?

No, I don’t just the master which is on the fog server

@ch3i said:

FOG_STORAGENODE_MYSQLPASS is not a unix password, it’s stored in MySQL database (in nfsGroupMembers table), has said Tom, it’s only to communicate between FOG node storage.
Ensure that in you FOG settings (in web UI) the FOG_TFTP_FTP_PASSWORD has the password 68c364.
The password in there is already set to that

fog.PNG

Thanks so much, I kinda did check the tables in sql but was looking for one called users

+---------+---------+ | ngmUser | ngmPass | +---------+---------+ | fog | 68c364 | +---------+---------+

In the FOG_STORAGENODE_MYSQLUSER I had fogstorage, but shouldn’t that be just fog? I have tried with fog, same thing.

This is what the other place looks like
storage node.PNG
Thank you both for helping out, much appreciated