@Mark-Shelton As seen in the picture the version of partclone is 0.2.89 which is the version we used in FOG 1.5.7. Sadly it’s not able to deploy images that were created with the newer version of partclone (0.3.13) which is now used in FOG 1.5.8.

Partclone 0.3.13 can deploy older images created by version 0.2.89 but not the other way round. Please upgrade your Raspberry Pi FOG install to FOG 1.5.8 (manually fixing the udpcast compile issue) or FOG development version (dev-branch has the udpcast compile fixed already).

@dmathews If you are going to start over, once the linux server is built. Create the /images directory by hand and then create the mappping of /dev/sdb1 to /images THEN install FOG. It will create everything correctly then and no changes will need to be made to FOG because the disk was added at the OS layer.

@AlexPDX Please open a new topic as your request has nothing to do with the initial post as far as I can see. Just copy and paste your text from this.

@Mark-Shelton Great, thanks for the feedback. I just added a fix to the code.

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