@TaTa Seems like the EPEL repos you use are causing the problem because the force a different mysql/mariadb version. Is there a good reason you are using these repos? I am just asking because to me it looks a bit like you are trying to install FOG on a server that is not dedicated for FOG only. While this can be done we usually don’t recommend people to do that as the FOG installer adjusts quite a few configs and might cause problems with other services you have running on the same system.

@ziomario Thanks to Tom’s work the installer now works with Ubuntu 19.10 as well. Just finished a test install with dev-branch. Though you need to choose one of the development versions. Either go with working-1.6 (upcoming version 1.6 with new GUI) or dev-branch (latest development version of FOG 1.5.x).

sudo -i
cd /home/ziomario/Scaricati/Linux/
git clone https://github.com/FOGProject/fogproject
cd fogproject
git checkout working-1.6
cd bin
./installfog.sh

Choose the version at the above command where it says “git checkout …”

@ziomario said:

ubuntu 19.10 workstation.

Seems like the FOG installer is not capable of running on that version yet. We’ll look into that soon.

@rankinc While it’s not great the FOG services aren’t running I’d say this has nothing to do with the error you posted in the other picture.

Please try the following:

• Schedule a new deploy for a host with 256 GB SSD but before you click “Create Task” tick the checkbox for debug.
• Boot up the client and hit ENTER twice to get to the shell - run command fog and step through till you hit the error.
• Now back in the shell manually run sgdisk -gl /images/UEFI-CafeteriaPOS/d1.mbr /dev/sda, take a picture and post that here.

As well, can you please post the contents of the text file /images/UEFI-CafeteriaPOS/d1.partitions you have on your FOG server.

Read through this topic: https://forums.fogproject.org/topic/13906/ssd-fails-at-restoring-partition-tables-gpt-with-error-code-4

@crustyjeff

Please try the following:

• Schedule a new deploy for a host with 256 GB SSD but before you click “Create Task” tick the checkbox for debug.
• Boot up the client and hit ENTER twice to get to the shell - run command fog and step through till you hit the error.
• Now back in the shell manually run sgdisk -gl /images/Accessing2019/d1.mbr /dev/nvme0n1, take a picture and post that here.

As well, can you please post the contents of the text file /images/Accessing2019/d1.partitions you have on your FOG server.

You might find this helpful: https://forums.fogproject.org/topic/13906/ssd-fails-at-restoring-partition-tables-gpt-with-error-code-4

Fixed now in latest version of FOG: https://github.com/FOGProject/fos/commit/5600a5adf952d6cef50f60c4fde1a1551c2ba7ee

@sgoodman I just finished some testing and I can’t replicate the fog-client crash yet. So far I guess it’s either related to particular updates (I had some .NET updates as well as system updates) or caused by some particular GPO WSUS settings (just a wild guess). Here is a picture of the update test with the fog-client running all the way through without a single crash - watching the log file (powershell get-contents -wait and the services view):

@lebrun78 Please take a look at the apache and PHP-FPM error logs (see my signature) and post here. With 5xx server error we should get a proper message in the logs as well.

@ismith-hpu There are numerous posts on this topic in the forums!

https://forums.fogproject.org/topic/12714/option-to-delete-files-when-deleting-multiple-images-snapins
https://forums.fogproject.org/topic/13292/images-won-t-be-deleted-in-filesystem-when-using-the-webui-delete-option
https://forums.fogproject.org/topic/13472/pb-free-space-fog-1-5-5
https://forums.fogproject.org/topic/13731/image-deletion-issue-if-mass-mode-used

@ismith-hpu I am fairly sure this is not related to Mac OS X. You probably see some error on the host’s screen when it’s finished. Take a picture of that error and post here!