Topics created by jahilton2002

I don’t think the permissions are changing on a reboot (possible, but I have doubts). I can see the permissions may be changing (not staying the way you set) when you capture an image and only for the captured image.

Can you provide a screen shot of what the permissions are being changed to?

@jahilton2002 Partclone is the default for FOG 1.2.0 and later. Partimage is left in the configuration for legacy images so they will deploy correctly with newer releases of FOG.

The next question you might ask is zstd or gzip compression. By default gzip is selected since it has been part of fog imaging for many years. The new compression technology is zstd. zstd is known for having a fast decompression speed as compared to gzip. zstd also creates smaller image files on the fog server. The only down side(s) to fog using zstd:

zstd is a newer compression format than traditional gzip compression. It takes longer to compress the image with zstd than with gzip, but decompression times more than make up for the slower compression times (consider you typically capture once and deploy many times).

So what should you pick? partclone with zstd with compression ratio 11.

Also there are 2 bugs in FOG 1.5.4 that have been patched in the 1.5.5 beta release that have not been back ported to 1.5.4.

Roll the FOS kernels back to 4.15.2 (done in fog setup->kernels). Download both the 64 bit (bzImage) and 32 bit (bzImage32) x86 images. This will fix the 3-5 delay (in some cases) creating the partition table (this issue is being actively worked on by the developers) If you run into an imaging issue with out of memory condition (under rare circumstances) there is another fix that I can tell you about if you run into it.

@jahilton2002 said in Issues importing /images since new fog server build:

But it hasn’t worked, same error

Which error do you mean? I can’t believe you are seeing the same “Attempting tp expand/fill partitions…awk:…” error.

After talking to my tech team here, we’ve decided to “take the hit”.

Probably a good idea!

The simple answer, because it’s Ubuntu, the “harder” answer, because it’s using upstart/systemd.

The answer to make it “automated” as you request, can be found on the forums. Specifically look for one of my posts today where I go almost fully in depth. I forget where.

Hi thanks for your help Purpleturtle99! after switch fog to do DHCP i can now boot from LAN thank you!

Add to that a little,

It just says next-server as you were describing, and only specifies you to edit the Options 66 & 67 on a windows DHCP. I didn’t add the “this is what you need where” until 0.33b and forward.

To add, actually it seems almost 100% stable with this modification, no crashes today…

Maybe the one crash after I made this change was a fluke and/or I had not rebooted yet, I cannot remember with all the different testing that I’ve been doing…