@TBCS ok good to know thanks.

@fox134 Have you restarted your FOG server yet?

@george1421 Ubuntu 20.04

You didn’t mention any baseline numbers of what you are seeing today with imaging on a 10GB network.

In my office we have a 10G core network with 1GbE going to the communication closets. I get between 13 and 15 GB/min (single unicast) transfer rates to modern target computers. On a well managed pure 1GbE network you should be seeing about 6GB/min (single unicast) transfer rates. I have not tested transfer rates on a pure 10GbE network, but I suspect the bottleneck will be in the disk controller on the server or the VM itself and not the network.

@george1421 Thank you! I have already requested that this configuration be done in PfSense. They haven’t implemented it yet, but managed to boot legacy. It was an option in the setup that was missing to allow legacy boot.

The option ‘Sistema Operacional Selecionado’ must be changed to Windows 7 or other.

I leave it registered here in case anyone comes across this same type of configuration.

link text

@NuTech3 said in UEFI secure boot off not working with DDWRT:

Does the Fog Server need to operate as the DHCP Server?

No fog does not need to operate as a dhcp server. BUT if you did install the dhcp server as part of the FOG install, then there would be no need for dnsmasq since the isc-dhcp server that fog uses is preconfigured to support both bios and uefi systems.

DNSMASQ has several modes of operation, but if you use my config file from the tutorial exactly DNSMASQ will operate in a proxydhcp mode. In this mode it supplements the main dhcp server with pxe boot information only. We will typically use dnsmasq running on a fog server when the main dhcp server is either incapable of sending pxe boot information (as in some soho routers) or the dhcp server is unmodifiable for some reason not related to FOG.

The interesting aspect of using dnsmasq on the fog server is that if the fog server is powered off so is dnsmasq. With dnsmasq off there is no chance of being directed to a server that is not powered on.

@awellis i see that you’ve solved the problem, can you share the solution, because it seems to me that i have the same thing.

Yep, that was it 🙂 I searched and searched yesterday, but couldn’t find anything that specifically applied 🙂

Anyways, mental note, delete recovery partition after Windows 10 is installed 🙂

Great forum, glad I was able to find a solution.

Quintin

@Sebastian-Roth Removing the 4th partition did resolve the issue. Thank you for your help. Great work with FOG.

I have 1.5.0 right now. Other images work it’s just specifically this one. I have to use the sda command to point to the primary disk

Hello, I forgot to give you an update. Your solutions fixed the problem! Thank you 🙂

@icescout27 Sorry for the delayed answer. Somehow I lost track of this. OK, so now we see a different error, obviosly because the password of the fogproject account is different. As well the access rights of the folder seem strange.

Run sudo chmod -R 777 /media/fog/External and follow George’s advices and you should bei good to go: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

Those accounts are service accounts created and used by FOG. If you mess with those you will run in trouble sooner or later.

You should certainly be able to search in the GUI by MAC address, however sometimes even then the host won’t display due to other issues. Using SQL, you can always find items.

Please have a read through the topic Sebastion mentioned. You might also look at this Wiki article: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

There is an antivirus McAfee. I have en impression that the app blocks on ping or somewhere there, when I try to install it with https selected. It doesn’t install at all. When I don’t select https option I can install it but in the log I see it blocked on downloading the certificate. From the log I took the address to the certificate and I was able to download it in a browser

https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

Essentially that will do what you’re looking for.

You do not install the fog software directly. You just need to configure the node to have FTP and NFS.

You will miss a few little details such as disk size and what not.

@Hartman4820 said in fog capture stuck at starting cmain:

starting cmain

This message is only being displayed by GRUB chainloader as far as I know. What this means is that the host your are PXE booting is using GRUB to chainload the OS from your hard drive and therefore I am sure there is no task even scheduled for this host!

You are saying “I check the Tasks and it just stops the task.”. Can you please let us know how exactly you scheduled the task and if you get to see it in the tasks list at the very beginning?

Just started a new fog server.

Which version of FOG do you use?

@george1421

Great thankyou, will do as you’ve suggested and report back!

@george1421 I’m good now. Thanks

@T-thorel Ok you passed the dhcp issue and pxe boot issue. Now the issue is with the iPXE program that creates the FOG iPXE menu.

Typically when we see this error it is because your building network switch is using Spanning Tree protocol but not one of the fast spanning tree protocols. A test for this can be to find a dumb/cheap/unmanaged switch and place it between the pxe booting computer and then building network switch. If the computer pxe boots correctly into the FOG iPXE menu then you will need to get with your networking/infrastructure group and have them enable one of the fast spanning tree protocols like portfast, RSTP, MSTP, fastSTP, or what ever your switch manufacturer calls it. This setting will need to be enabled on every user facing port where you need to pxe boot.

The issue is that FOG boots too fast. It will give up trying before spanning tree starts forwarding data on the network interface (~27 seconds after the link light is turned on).