@Quazz said in Snapin replication no working:

systemctl start FOGSnapinReplicator

10x dude …that did the trick 🙂 now its all working again

After some extended research I figured out this was caused by the build script not re-generating the trusted root part of the code compiled into the iPXE binaries. It’s really easy to fix and I pushed a fix to both dev-branch and working-1.6 so we hopefully never run into this again.

cd path/to/fogproject/bin/ touch ../../ipxe/src/crypto/rootcert.c rm /tftpboot/undionly.kkpxe ./installfog.sh

On that way I learned a couple of things about iPXE booting over HTTPS and so I hope we can find most upcoming issues more quickly from now on.

@AlexPDX So if you look on the storage node(s), are those image files there?

@astrugatch Good to know this was caused by browser caching. I can imagine more people running into this. Thanks!

@cbittencourt So just for clarity you had secure boot enabled and you turned it off to resolve the issue?

@Sebastian-Roth Thank you for all you and everyone does. I agree with you this was a good choice to make a second topic out of. This is working well now and I greatly appreciate all the assistance!

@george1421 said in PXE Boot not working properly from Storage Node:

So the root cause of this:

The fog install script does not honor https for storage node installs?
The fog installer did not provide the necessary command line switches when installing the storage node to enable https?

As far as I can tell right now the only issue was that the storage node was not installed with HTTPS enabled in the first place and the buildipxe script in 1.5.7 has a bug that would not compile the cert into the binaries correctly (fixed for 1.5.8 already).

@anwoke8204 said:

it attempts to pass off to the hard drive, but it doesn’t, just goes back to the fog menu

I am wondering on what happens if you switch from PXE boot back to just plain boot from disk? Does it boot Windows 10 properly then?

I have tried both bios and uefi. and I get the same issue.

What exactly to you mean by that? Did you play with the exit type settings for both in the web UI or did you switch the BIOS/UEFI firmware settings on the host? If you played with the firmware settings on the host I am really wondering if your image is UEFI or legacy BIOS? You can’t have a pure UEFI image and boot that on a legacy BIOS only machine or vice versa.

Which exit type is set in the web UI? Have you tried all the different ones like SANBOOT and so on?

Be aware there is a global setting for exit type as well as a per host setting.

@mp12 Looks good! I will update the official binaries tomorrow. Thanks for all the testing! Marking as solved.

Hi,

DB cleanup did the the trick.

Thanks

@Sebastian-Roth I removed the last two partitions and worked like a charm. Thanks!

I implemented the fix in my setup. It works HOWEVER just copying refind.conf and renaming it WILL NOT WORK!
rEFInd seems to hardcoded look for refind.conf and WILL NOT ACCEPT a file named differently. I worked around this by naming both files refind.conf and putting them in different folders.

Thanks again for your help!

Thanks to @Tywyn who provided the initial password I was able to figure out why this happened. The installer uses the password to update the storage node setting in a way that is prone to a URL encoding issue. I have to admit I didn’t know base64 encoding can actually produce strings that can cause such a problem:

$ echo -n 'as~ja$j2niau83j2' | base64 YXN+amEkajJuaWF1ODNqMg==

The + character is then miss-interpreted by the PHP code as space character and therefore breaking the base64 decoding of that string.

I just pushed a fix to dev-branch in hope if this fixing all cases that special characters could cause in that part of the code.

@george1421

Thank you, perfect followup…
worked well as well L13 Yoga success.

Thanks to all.

@joanmarzo Only a real FOG Server can run the fog replicator service. Marking the nas as a master node allows it to capture and deploy images. If you want image replications to other servers you will need to setup something outside FOG to move the images. Remember I said this configuration is NOT supported by FOG but can kind of work.

@phm2000 said in Error trying to restore GPT partition tables:

I have same problem with fog 1.5.7, is there a solution ?

Sorry but with this kind of problem there is no general solution that works for everyone. Please open your own topic in the forums and post all your own details: full contents of the file d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions.

@JYost said in Remotely imaging a laptop using FOG:

Now that I’m looking at it I see exactly what you mean about going in and pre-creating the HOST.

This is referred to as manually registering the host. The only bit of information that may be problematic is the target computer’s MAC address. If you have the mac address then you an just go into the web ui and add a new host and enter its name, image, mac address via the web ui. You won’t get the full inventory right away, but there will be enough information to pxe boot the target computer. If the fog client is already running on the target computer, when you create a deploy task the target computer will reboot, or power on if WOL is enabled on the target computer. But to do this, the target computer needs to be configured to boot through PXE to the FOG menu every time. If there is nothing to do the target computer will continue on booting from the local hard drive.

ALSO, if the fog client is installed on the target computer BUT the target computer is not registered in FOG the target computer will be added to the FOG server in the pending state. You will need to approve the target computer to have it added to the inventory. You will still need to set the image name but you should have a near hands off registration.

@Sebastian-Roth

fogadmin@fogimaging:~$ ls -al /var/www && ls -al /var/www/html total 16 drwxr-xr-x 4 root root 4096 Feb 13 10:53 . drwxr-xr-x 14 root root 4096 Sep 11 2017 .. drwxr-xr-x 10 www-data www-data 4096 Feb 13 11:04 fog drwxr-xr-x 2 root root 4096 Sep 11 2017 html total 20 drwxr-xr-x 2 root root 4096 Sep 11 2017 . drwxr-xr-x 4 root root 4096 Feb 13 10:53 .. lrwxrwxrwx 1 root root 13 Sep 11 2017 fog -> /var/www/fog/ -rw-r--r-- 1 root root 10701 Sep 11 2017 index.html

Yes text alternatif

@george1421 , obrigado! Agora entendo como o fog funciona!