@sudburr Ok, I tested and updated my version of the script below (derived from yours).

Again, make sure you have backups of your /images and the certificate files before you run this script!! I won’t be responsible for any trouble caused by this script!

I found and believe I may have fixed the issue. It was actually pretty simple. The error was coming from the unpacking of information.

Hopefully it helps. Just repull the dev-branch and install and all should be back to normal.

@Sebastian-Roth Thank you for finding and fixing the issue.
@Greg-Plamondon Thanks for reporting. This fix is also set for 1.6 now too.

Awesome job everybody!

Thank you,

@masoudmahamid Please run this on the command line and post output here: ls -al /images/dev

@dario-vettore Did you get this solved?

@brakcounty Any news on this?

@andrewhancock91 Are you still keen to discuss this?

@f-an Is this still an issue or did you solve it?

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

@brakcounty said in customizations to ipxe menu not applying after updating to 1.5.7:

One question though, from the main FOG ipxe menu, when i hit Deploy Image, and get the prompt to authenticate with fog/pass, that text is blue, i want it to be white. Where can i change that setting?

In my test environment if I change the iPXE main colors (FOG Configuration -> FOG Settings -> FOG Boot Settings -> IPXE MAIN COLOURS) this is valid for all the text in the iPXE boot screens as well as for the password entry.

@george1421 That is because the separate storage group has a master. It’s a “work around” to the “Images are always captured to the master node” because you, quite literally, are making the storage node, now, a master node. It works of course for this reason.

@madeyem said in FOG and UEFI/M.2 SSD:

Is it really necessary for you to have the PC run in raid on mode? If not, leave it at AHCI

If you have only a single disk in the computer OR you have multiple disks but have no plans on setting up a raid configuration there is no performance penalty to leave the disk controller in ahci mode.

@Brad-Schumann The short answer is it depends on what the laptop is doing. The bit longer answer is the config file for refind is in /var/www/html/service/ipxe and its called refind.conf.

Also make sure the firmware is up to date on this laptop because it could be flaky firmware that is causing refind to fail.

The last option is we may need to look into updating refind to a later version because the hardware drivers in refind may need updating.

So in the end it depends…

@Quazz Thanks, done: https://github.com/FOGProject/fos/issues/31

@martial said in button "Reset encryption Data" does not appear:

I guess the virtual mac address made by forticlient is the big problem as it is created on multiple clients?

Yes, most probably. Take a look at the option QUICKREG PENDING MAC FILTER in FOG Configuration -> FOG Settings -> FOG Client - Host Register!

@Sebastian-Roth No, i have changed the permissions to fogproject:root and delete the directories in /images/dev/ that looks like a MAC address.

It works now.

@Wayne-Workman said in Installation stops during setting up fogproject password:

own projects, I opt for very long passwords made from upper & lower case letters and numbers randomly. I’m talking 32, or 64 characters long. Typically I look up the maximum length supported password, and generate one of that length, just letters and numbers.

I tried another installation on an other, identical notebook fujitsu lifebook with fedora server 30, but allowed special characters in the function.sh and it works also.

do [[ -z $password || $ret -ne 999 ]] && password=$(head /dev/urandom | '0-9a-zA-Z!#$%&()*+,-./:;<=>?@[]^_{|}~' | fold -w12 | shuf -n1) echo -e "$password\n$password" | passwd $username >>$workingdir/error_logs/fog_error_${version}.log 2>&1 ret=$? let cnt+=1 done

@george1421 Thank you once again for great support!!!

Since the apache crashes did not correlate with the no directory or file errors I double checked everything attached to our workbench and…

Found out one of my engineers had a test box attached to our workbench that was set for no reply to ICMP so I did not catch it had been static’d to 10.0.0.250 as well. Flipped it over to DHCP and now PXE boot works consistently.

Sorry and thank you for your time!

Some options.

1º Use a snapin pack including the executable.
2º Put it in a ftp server and use a cmd ftp client to download it. (You can use the fog server/node as ftp and the built-in ftp client)

This two solutions works!!!