@george1421 Hi George,

The issue was fixed, need to test it on more machines to make sure it’s a global a fix, but after isolating the boot drive using debug mode it appears to be deploying to the correct drive. I used /dev/sda2 as my host primary disk.

I’ve attached a photo of the drives available to the fog.

I’ll! keep you updated on this and thanks !

Bill.


@tombagley ignoring a mac in fogs webif just ignores it for the specific host not the whole system!

@waynejitehead i simply remove the usb nics mac after deployment because it does not belong to the system, this way new hosts with same usb nics mac will propperl recognized.

Regards X23

@bmacadre Try to put the FOG Server on one of the 100Mbps ports. This would obviously severely hinder unicast imaging, but if you’re mostly doing multicast then this might work better.

@george1421 Fog has been working, but I haven’t had any machines to test a multicast on since we last spoke. I am going to attempt to image a classroom today and will report back.

@george1421 I replicated my images using rsync and verified that all images are in both locations. I also have a backup of my images off of both of the nodes. I went in and I created a new Storage Group. I associated the Storage Node that is not the Master Server with the new Storage Group. I then associated a number of my images with that Storage Group. My goal is to have some images only reside on the node in the new Storage Group and some only reside on the other Storage Group. I set both servers to be the Master Node for their Storage Group. Based on the warning I read about setting a server to the Master Node I half-way expected for any images that were not associated with that Storage Group to be purged from the Master Node but that didn’t seem to happen, which is fine. Is it now safe to go back and purge images from servers via cli if they reside in an image store on a node that is not in the Storage Group that is associated with that image? Thank you!

We have ended up rebuilding our image and it is now working OK. It mustn’t have liked something in our old image.

Thanks for your help and suggestions!

@george1421 Ok, sorry about not getting back to this sooner, but work has been a bit busy. So anyway, I made the changes to the config file. (basically I created the ltsp.conf because it did not exist in the dnsmasq.d directory) there was only a README file. I was able to do a TCP dump and cap the information. But I have a feeling it will not be much help,

0_1532033995049_pcap.fog.JPG

I did see that I am running 2.75 version of dnsmasq, but I can reload the VM to just before I installed DNSMASQ and make sure the 2.76 version is installed. *will update if there are any changes from that versioning.

Thanks for the help!

Can you confirm

The FOG webgui is reachable On the switch where the target computer is: Ensure that spanning tree is configured for fast-STP or RSTP or place an unmanged switch between the target computer and the building switch.

@tom-elliott
It turns out that the crappy HP procurve 1900 switch that my xenserver was connected to has a feature called “auto DOS” that was blocking the NFS packets. I installed a couple of physical Linux systems to test with and found that I could mount the NFS shares when I was plugged into a different switch.

All works as it should after turning off “auto Dos” under security settings on the switch. The crazy thing is that I had a working fog server for years on this same switch/xenserver. Time to upgrade that switch. Anyway, thanks for all your help. Much appreciated!

@tom-elliott Wow, you’re awesome! We’re actually getting a new network because of E-Rate within the next month. I am logging your explanation/suggestions and will run this by the guys installing the switches. Thanks.

@wayne-workman Thanks. I changed it to 15 minutes. I’ll see how that does.

@Mike-Fahey As George said, the ACPI messages should be ok to ignore for now. About the CPU stall, find some posts from other users in the forums:
https://forums.fogproject.org/topic/8918/fog-boot-to-fos-rcu_sched-self-detected-stall-on-cpu

Not sure if this is the same issue. Please read through the whole post start to end and see if it helps.

@hvaransky This error has nothing to do with debug mode I reckon. Did you set a kernel name in that client’s host settings?? Or maybe you changed the general FOG configuration in the web UI?!

@alex84 reading the post I see no issues with what @Wayne-Workman has asked.

If indeed capture takes forever but deploy is fast as your post suggests, what is the compression set too? What is the RAM (size/speed)? What is the disk?(ssd/spinner) is the disk good?

@wayne-workman
Thank you workman, I will read the Wiki page.
Thanks again.

@george1421 I might just try that, just for troubleshooting purposes.

Re: firmware - There is a BIOS update for the machines, and a firmware update for the NVM Samsung drive. Sadly, trying these was my first troubleshooting step (not listed here, because it was before I suspected components of FOG). I sure was holding my breath that it was the drive firmware though!

So that gave me the answer I needed. It’s not a problem with fog. These aren’t the machines they were supposed to be they sent us the 64gb emmc version instead of the 128gb m.2 thanks for your help.

@cs_pccs Please start a new thread since your conditions are likely different than the OP, unless you just upgraded from 0.32 version of FOG.

Please include any images you feel are relevant in your post. HINT: A clear picture of the error provides us with an idea of the context of the error as well as the exact error message.

You need to use the kernel and inits shipped with FOG 1.5.4 (almost) or you will have an unsuccessful deployment. FOG kernel 4.17.0 is shipped with FOG 1.5.4. There is something wrong with that kernel version, it takes minutes to create partition tables on target computers. This is not a FOG issue per se, but a linux kernel issue. But to the point roll your FOG kernel back to 4.15.2 via the FOG Settings -> FOG Kernel menu. Also note that the inits are tied to the kernel version, so you need to put the FOG 1.5.4 inits back in place or you will get an error message. Once you provide the info in your own thread, we can start to dive into your issue.

@quazz @george1421 well, disabling secure boot seemed to do it. Thank you sooo much for the help. I will continue on with the process and hopefully all goes well.