FOG Hangouts

@kevinnew22 said in Error trying to restore GPT partition tables (restorePartition TablesAndBootLoaders):

understood, the release of the new version will be when more or less? I can help with something?

Can’t give you a date as we don’t have a fixed plan for new releases. Not great but that’s the way it is right now. Hardly anyone has time to work much on FOG and so things are going very slowly. You are more than welcome to join in an help us push this forward. See my post in the forums. Please send me a private message if you are keen to get involved and I am sure we have something for you! Looking forward to hear from you.

@lucycle Take a look at the first couple of lines of this script: https://github.com/FOGProject/fogproject/blob/master/utils/FOGiPXE/buildipxe.sh

@pamadmax Which version of the fog-client do you use?

Try using this installer to hopefully fix the issue: https://github.com/FOGProject/fog-client/releases/download/0.12.0/FOGService_fixed-tls.msi

This has been discussed in the forums before…

@kevinnew22 said in Error trying to restore GPT partition tables (restorePartition TablesAndBootLoaders):

Is this dev-branch version inferior to the one I have? to solve this problem I have in the images which do you recommend? t

Yes it is! As George said, updating to dev-branch will fix the issue you see most certainly. What George was saying about going back to an official release (a.k.a the master branch) can be done easily using git - see the commands he posted. But I wanted to add that you shouldn’t do this while 1.5.9 is still the latest official release because that would be a downgrade and could cause problems. As soon as 1.5.10 will be released you can switch to master because that’s going to be a step forward then.

Just for the records, downgrading (e.g. dev-branch to 1.5.9) is not supported. I am not saying this will cause problems per se but the more changes we have between latest official version (1.5.9 as of today) and dev-branch, the more chance there is downgrading will break something. Do whatever you like but I won’t support fixing a downgraded install.

@mrp When we struggled with this I didn’t think as far as only using identifiers for deployment. I will see what I can do when I get back from my holiday in a couple of days.

@koni said in The client won't install:

the first error disepeared by installing the package sysv-rc-conf but chkconfig can’t be install because he is obselete.

Sure, the fog-client does an “either or” check and should not complain if one is found.

I think we had someone a similar issue in the forums some time ago. Please search the forums for sysv-rc-conf…

Is fog unusable on certains Linux distro / version ?

We don’t know as the feedback from testers on many distros is missing. Much so with newer versions.

@yeet said in When and Image is captured multiple times, does it overwrite the previous capture? Or is there a way to access captures from different dates?:

Would I just need to back up the /images folder, or are there other components that would need backing up as well?

Backing up /images is enough for what you want to achieve. BUT keep in mind that you keep track of image setting changes as well. So if you need to go back to an older image you can switch back to an older image setting as well. Those settings are not changed often and so backing those up alongside is probably too much (useless) effort.

@yeet said in When and Image is captured multiple times, does it overwrite the previous capture? Or is there a way to access captures from different dates?:

When I capture an image, then capture again, is there a way to go back to a previous capture?

No, unless you use another software to grab daily backups of your FOG image store.

@mrp said in Identical NVMe drives:

I’m thinking of the possibility to specify the order of drives in the Host Primary Disk field by listing all disk identifiers in the right order.

Which disk identifiers would you think are apropriate? Disk UUIDs?