@Zaqen Looks good I reckon.

@george1421 said in Failed to start php-fpm.service:

Please upgrade your installer package to the dev-branch.

Thank you @george1421 It work ! 😄

@ToneZ82 Why the double post?

@sebastian-roth Installing the dev branch solved the issue.

Thank you, mate!

@tmikecurry said in After Network Issues and Reboot, New Image Attempts Are "0.00 iB" and "Invalid date":

…did this occur because we needed to re-inventory the hardware on the source laptop? (So it would stop associating it with the earlier image?)

In FOG the inventory has no association with imaging directly as far as I can tell. So I think setting the correct image in the host object was actually the solution.

@axou86ch Answer yes to set a proper MySQL root passwort and make sure you note it down.

@piotr86pl said in CentOS Partition Count Failed:

The script checks how many NTF

In order to use “Single Disk - Resizable” option during the installation CentOS for the /boot directory i use ext4 instead of xfs. As a result it can be capture without error but the image client size still remain the same size as the disk.

@omar_medhat said in No Configuration methods succeeded !:

The switch is cisco C3750G and as soon as I configured the port as port-fast … Problem solved !

Well done.

OS is Ubuntu live server 16.04

Please make sure you switch to a more up to date OS before you go productive with this.

@chunter2 Bump…

@londonium said in Image replication crashes when FTP connection fails:

Anyways thanks again for your help.

You are welcome!

We really enjoy using FOG and have big plans for it!

You might consider contributing to the project as you’ve done a great job digging into this issue. Feel free to send me a message if you consider helping out.

@kibade This is fixed in the latest dev-branch on Github.

@David-Scott See George’s post here: https://forums.fogproject.org/post/115780

Though I am not sure this is actually causing the issue you describe.

@carl-d said in Unable to see current FoG Version Info After Upgrading Debian from 8 to 9, then from 9 to 10:

I did have to install php-curl, and now everything is working properly.

Probably a good idea to manually edit the “packages” line in /opt/fog/.fogsettings and add the php-curl to that as well.

@flareimp There’s other options as well. You could do either of the below.

The below script is a one-use script that someone could run manually. After updating the IP via the OS configuration, you can run this script that will update all the FOG IP bits for you.
https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

This next script below will continuously update FOG’s IP settings to match the local interface IP address. You could package this with the fog server image you have so everything just works out-of-box.
https://github.com/FOGProject/fog-community-scripts/tree/master/MakeFogMobile

@tom-elliott
There’s not port/cable issue. I’ve changed it and still with same error. I’m thinking this can be something with hardware/bios of this notebook (DATEN-DCM2B-4).

Does someone have another ideia?

@obscure Good job getting it to boot! As for the function of the bootcd, I can’t say. If everything is contained in the boot.wim it should be in the box so to speak. Its possible that additional files are needed that are saved on the cd image. I don’t know the the software itself only how to boot the winpe image.

I was able to resolve this by removing my prepopulated /opt/fog/.fogsettings file and going through the prompts from the installer. I suspect the line causing my issues was caCreated='yes'. I had copied this over from another installation.

@robertkwild Yes, at least by default. I don’t know how frequently we’ve had things actually usable from a partition to partition image, but typically the flow is:

Erase the Existing drive
Configure the Existing with the image partitioning schema
Write the image to the disk
(If resizable - expand partitions)
Reboot

@sebastian-roth Thanks Sebastian! That solved all issues!

@ferras said in FOG PXE menu on black screen:

However, when trying with a third computer, the menu was displayed correctly, so I assume it could be some bios setting which I will review in detail.

As Tom said some firmware is not playing with the “standards” and so you end up with the ugly black and white menu screen. There is not much we can do. Feel free to report this to the iPXE project.

Additionally, I would like to ask about the preparation of an image to apply to some of my computers, when restoring the image I realize that the Windows UUID of the master device is cloned in the other computers as well, causing me to not be able to add them to my company’s domain controller. I just dont figure out how to correct this issue.

Please open a new topic on this. Posting different questions in one topic usually ends up in misunderstanding.