Thank you so much for your replies. I reinstalled and it fixed it. I didn’t realize a reinstall wouldn’t affect the existing install. It installed “php-gettext” and did all the checks. Database is perfect.

Thanks for the assist. I appreciate it.

Hello @george1421

I had already done a mount and it worked

I had also activated no mapping on the squash option

probleme2.PNG

Thank you!

@wayne-workman This call has to be made using the DELETE method.

@renard Usually those ACPI BIOS errors can be ignored as mostly being warnings. Though it’s strange you machine just reboots after that.

Which version of FOG do you use and more importantly, which kernel version (FOG web UI -> FOG Configuration -> pane “Kernel Versions” -> expand by clicking the “DefaultMember FOG Version…” bar).

Today w’ve tested FOG with one new switch (a Cisco) and every problems leaves away. So i didn’t test udp-sender modifications. Our 2 switches are 1GoMps. Sebastian, i wil look to improve the french translation and i’ll send you back the language pack

@george1421 So are you saying we should not alter the kernel config because of this? While you are right about it should be working when using the latest 5.10.19 kernel I still wonder if the CDC_ETHER will cause us trouble as we did not have that enabled in the 4.x series kernels.

@alan-lim

This is really just a starting point. You should adjust the instructions based on the mount point for your NetApp storage.

@fimlore I understand that,

What I meant by the ipxe is different from pxe and fog is:

PXE has it’s own DHCP mechanism. This then hands off to iPXE which handles DHCP on its own. This then hands off to FOS (FOG Operating System) which handles DHCP on its own.

@belac said in Problem with new FOG 1.5.9 installation:

manually update
on all your storage nodes

This is not for your FOG master node. Hope you have a copy of the old fogsettings file or we might be able to get the last fogmaster DB credentials from a backup of the config.class.php file in /home/fog_web_1.5.9.BACKUP/…

@choppaholic26 Oh well, I should have had look at the topic line again to know it’s about TFTP timeout.

I think the only way to maybe find out is to capture the network traffic exactly where this is happening. Either you have a managed switch and can enable a monitoring port or one of these really old network hubs to pick up that traffic from/to the PXE booting client machine.

@sebastian-roth said in Uninstall FOG-Client (Service) after deploying with Snapin?:

The fog-client runs as SYSTEM

@jcrod73

OK here is what I’m thinking. I’m not saying its the exact case here but I’ve experienced this in the past.

If the application that is running is 32 bits (regardless as who it runs as), windows knows this. Windows will map the 32bit application to this path (akin to chroot) to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node So if you have a 32 bit application creating the runonce key, the value should be found here: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\RunOnce Whereas a 64 bit application would create the key here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce

Note the: HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce would only “run once” the current user who created the key logs in again (i.e. SYSTEM). You will probably not get the response you expected from that reg key location.

I’m speculating the fog client is a 32 bit app because I don’t see an install for 32bit vs 64bit its just one install. I don’t know if the installer is smart enough to install the 32 bit stuff for a 32 bit machine and the 64 bit stuff for a 64 bit machine. So some of this is just an educated guess.

@george1421
Hello george,
I did not succeed in restoring the database, I do a complete reinstallation of the server.
Thank you for everything

@kamil .fogsettings file is hidden. In linux when a file name begins with dot ( . ) then file is hidden.

Question on bitlocker. Yes and no will this be a problem. No it will not be a problem in that FOG will backup the protected images in RAW disk mode.

Yes it will be a problem because fog will not be able to resize the disk because the partitions are protected with bitlocker. Also if you move the image to a different computer, that bitlocker protected disk will not boot because the values stored in the TPM chip will be different on a different computer.

So while you can copy a bitlocker protected disk you can not move the image to a second computer and think that it will work.

@mikmatcr So does it mean you were able to properly capture the image from the 500 GB disk and deploy to the 256 GB disk?

From the new d1.minimum.partitions it looks like it but just want to make sure I don’t misunderstand.

@florent
Sorry i found the problem, i think it’s bad value on the mysql table.
I go to the powerManagement table and see line like this with “-” :
0 8 - * wol 0
I have deleted this line and restart FOGScheduler, after it’s ok

[03-04-21 5:08:23 pm] * Found a wake on lan task that should run. [03-04-21 5:08:23 pm] | Task sent to XXX

It’s resolved for me

@george1421

Dell change the motherboard with lan integrated and it works now.

Finally got centos-root expanded. that fixed everything!

@george1421 I will certainly never try to upgrade CentOS forklift style again. You were correct I upgraded Centos from version 7 to 8. After the mess it created I took your advice and ran the FOG installer using “GIT” and it cleaned up a bunch of the issues. A BOAT LOAD of things were missing after the upgrade but now they are functional. Thank you for all the assistance, FOG’s community and dev team is top notch.