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

@george1421 Hi George,

thanks for that, yes that’s solved my issue.

I was thrown off by the the Fog version info, stating that it was up to date. didnt see the Kernel update to the side.

Many thanks! 😊

@bido Well where its failing we can rule out a lot of things. You have your PXE booting configured correctly because iPXE is running. That is undionly.kpxe. That file is getting transferred to the target kernel and is running. Its iPXE that is having a hard time.

The next test I want you to do is to install a cheap unmanaged switch between the target computer and the building switch. This test will give us an indication if spanning tree is enabled, but you are not using one of the fast spanning tree protocols (RSTP, MSTP, port-fast, FastSTP or whatever your switch mfg calls it). The dumb switch will keep the building switch from resetting the spanning tree counter while booting. Understand this is only a test to tell us if its spanning tree or not. My gut reaction is yes.

@mstabrin Yeah, sounds like we found a good working solution for you. Great to hear that it did the trick.

Edit: I did rename the topic so we and others might find it more easily when looking for WOL.

@george1421
this is the wrong configuration: option 66 was checked.
a big thank you for your patience and the time spent with me

@alexnoel2 said in Capturing from a LUKS encrypted drive.:

primary drive is encrypted with LUKS

Am I screwed?

Only on days of the week with the name ending with a y

It has been successfully solved before: https://forums.fogproject.org/topic/13845/error-decrypting-luks-partition-prior-to-capture-imaging

You have the same issue as a windows computer protected with bitlocker. Since FOS Linux can’t read the disk, it clones it as RAW (block by block).

@quazz said in Can't capture an Image on Fog (newbie):

@juntacadaveres Well, it’s pretty clear, boot in recovery mode and fsck -fy it.

The cause of this problem was that my client was a “clone” of another virtual machine… I have detected that using fog with clones of other virtual machines can cause troubles. Thank you, anyway.
By the way, I have used virtualbox.

@george1421 said in FOG image drive failed. What now?:

@cammykool This image error is related to the php code. Apache off load php (the language the web ui is written in) to php-fpm (dedicated php execution engine). The error you see is apache saying that php-fpm did not answer it was done with the task in time so apache timed out.

There may be some clues to what is at fault in /var/log/php-fpm/error.log tail that and see if it tells you what its not liking. If you set the permissions of 777 on /images nothing should stop it from moving files.

i had my coworker crack away at it. He got them all to delete and we are in good shape! Everything seems to be working and happy!

@cicero said in Can't image:

I don’t want to be a pest but would appreciate if I can reach out to you you have great instructions

You are not. The forum is here to ask questions and people try to help. I would just ask you to not repeat asking more and more questions in the same topic! There is no restriction to open new ones for each question you have and it’s a lot easier for everyone to keep track.

@blankzapper said in Client check-in and restart times:

I removed WinMGMT as dependency of FOG service, and removed random offset added by FOG server. These are dirty hacks, but they work for me.

You seem to digg right into it! 🙂 May I ask, what is your actual aim with this? You are more than welcome to help us working on the fog-client code as you seem to be pretty good with this stuff.

PS: Didn’t even know the MSI installer sets up so many service dependencies…

@sebastian-roth said in UEFI boot loop issue:

@jonhwood360 said in UEFI boot loop issue:

Updating the refind x64 binary

To which version did you update? This might be helpful for other users as well.

refind-bin-0.13.0.zip

@sebastian-roth Yes i am sure. also for now i am using 2 clonezilla live USBs which seems to work perfectly fine and does recognize the disks/raid card. cloning over the network with these 2 USB sticks seems to work.