@Pingu Ok, i find out that my /images was a little bit bugged and got my snapshots in dev folder with the mac address as name folders, i moved them into /images and renamed them with the image name i configured on the Web Interface and it runs !!
Hope this will not happen for the next snapshots.

@george1421 Hello !
Thanks you so mush ! It worked ! 🤗 🤗

Have a good day,
Pinki

@sebastian-roth Thanks for your reply, we will try the alpha version.

My teammate ask me to say a big thank you because since 2008 we use fog and we see you’r answer are very quick and we are very happy to use fog.

did i need to do something to indicate the post as resolved ?

@sebastian-roth I would be happy to give you a feedback if I have the opportunity to test your new init (I am an intern so opportunities do not arise all the time :))

@dirtysoc Good news, this is a known issue with VirtualBox. Switch to ipxe.pxe boot file and the issue will be gone.

@brakcounty To get some more information, can you please schedule a debug deploy task (same as you would do a normal deploy task but just before you hit the last button in the web UI there is a check box for debug). Boot up the client as usual and let it boot up. Then you need to hit ENTER twice to get to the shell. Now type fog and ENTER again to start and step through all the process till you hit the error. It will throw you back to the shell. Now type:

sgdisk -gl /images/Win10Standard_GPT_EFI/d1.mbr /dev/sda

It surely will fail. Take a picture of the screen and post that here.

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

@JackWallington Please answer George’s questions first. As well let me add this one. Do you have a D-Link DGS-3620 switch between your HP desktop and the FOG server? If not you still might check to see if some kind of DOS attack prevention is enabled on a switch connecting those two - more information see here.

OK. Will do. Thanks!

Found the issue and was able to fix. Fix will be available for RC-6.

Thank you for reporting.

@Ph3noM Fog doesn’t set a DB password - if fog sets up the DB on a new server, it’s left blank. The installer (at least in FOG 1.3.0 beta) asks you for a DB password just in case you set one in the back end. And of course if that’s the case (and 99% of the time it is) then the field in /opt/fog/.fogsettings would be blank as well.

@Wolfbane8653 thanks for the help. I thought there might be issues running both svn and git but it went smoothly. Thanks again.