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).

@f-15s-mtd You will need to change every switch/port that has a device that you want to pxe boot on. This is an access layer issue not something related to the FOG server or switch to switch communication. The problem is in the “last mile” so to speak.

ref: https://community.cisco.com/t5/other-network-architecture/enable-portfast-on-all-ports/td-p/324511 read down the post because there are switch global commands that you can use.

@smoooo If you are going to use two network adapters (recommended) before you install fog, know the linux name of the nic that will be your imaging network interface. Make sure you have static IP address mapping done on the imaging network interface. When you install FOG it will ask you which interface do you want to use. Make sure you name it correctly. Also FOG gets angry if you change the IP address of the imaging network interface after FOG is installed. So have your network configuration complete before you install FOG.

set the IP adress of the fog serveur
instead of the name “fogserver” at the install of the smartinstaller and enjoy 😄

I may have read your post too quickly, so if after you confirm the settings according to the wiki page, you still have issues we can debug using a packet capture. If the fog server and the pxe booting computer is on the same subnet, please use this tutorial to capture the best quality pcap. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

The pcap will show us what the target computer is being told to do.

If your pxe booting compute is on a different subnet then install wireshark on a witness computer (second computer not part of the pxe booting process). Use the wireshark capture filter of port 67 or port 68 to only capture the pxe boot.

Post the pcap to a file share site (like google drive) and either post the link in the thread or IM me the link and I will take a look at what the client is being told.

Thank you!

I clicked the update button but didnt wait long enough it seems.

Sorry for bothering you with this trivial stuff, thanks for the help.

Sébastien

@Richard-Wise Ah ok, then set this value in the web ui FOG Configuration->FOG Settings->(Expand all)->FOG Boot Settings->PXE MENU TIMEOUT change the value to 0

More info - from old fog I exported only hosts via web browser - old hosts when reinstalling have correct hash and snapins works smoothly. Issue is only with machines which I register.
No errors in fogsnapinhash.log

@tesparza If unicasts are fine, but multicasts are not then I would start with the igmp snooping. There may be another command that needs to be enabled for the catalyst line. I seem to remember there is but can’t remember the details at the moment.

@george1421 So actually we testet the ipxe.efi boot file and it Resolved the Error that we had. So thanks for the Help and Support, i hope it will stay so 🙂

@mmoore5553 Not a clue since I don’t have one to test with, sorry.