FOG doesn’t copy NVRAM from cloned machine to the new machine

[Sebastian Roth]

@marted I would say use the .efi file should do. If you are keen you can copy the .conf over as well but using a different name and diff the two files.

[marted]

@Sebastian I tried your other suggestion for executing a postscript and I came with this command I executed in debug session on a client and it works
For me, it will be a better solution instead to mess up with rEFInd boot.
Now I need just to figure out how to add the script and where

efibootmgr --create --disk /dev/sda --part 1 --loader ‘\EFI\grub2win\g2bootmgr\gnugrub.kernel64.efi’ --label “Grub2Win”

[marted]

@Sebastian to run this command with efibootmgr, do I need just to create a bash script, make it executable and put it in /images/postdownloadscripts. ?

[george1421]

@marted The proper way is to create a bash script and place it in /images/postdownload directory and then link (call) it into the fog.postdownload script. If you have different hardware or images, you can also create a conditional if statement so that it only calls this command if the image name matches a certain image name.

I have examples of post download scripts in the tutorial forum. Some are windows focused but the concepts are the same.

https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

https://forums.fogproject.org/topic/8889/fog-post-install-script-for-win-driver-injection

[marted]

@george1421 Thank you so much!

[Sebastian Roth]

@marted said in FOG doesn’t copy NVRAM from cloned machine to the new machine:

I tried your other suggestion for executing a postscript and I came with this command I executed in debug session on a client and it works

Nice. Well you might go with that for now and come back to other solutions when you feel like it.

[marted]

@george1421 @Sebastian-Roth I did the changes, just please confirm that everything I did is correct :

1. I created a file with permission 775 on the server FOG in /images/postdownloadscripts called fog.grub2win

#!/bin/bash
/bin/efibootmgr --create --disk /dev/sda --part 1 --loader ‘\EFI\grub2win\g2bootmgr\gnugrub.kernel64.efi’ --label “Grub2Win”

2. I added the script in fog.postdownload

#!/bin/bash
## This file serves as a starting point to call your custom postimaging scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post download scripts are
. ${postdownpath}fog.grub2win

is everything OK?

[george1421]

@marted Yes, I would make a comment and add a debugPause in your script so you can see it run something like this.

#!/bin/bash
echo Updating the Grub boot manager
debugPause

/bin/efibootmgr --create --disk /dev/sda --part 1 --loader ‘\EFI\grub2win\g2bootmgr\gnugrub.kernel64.efi’ --label “Grub2Win”

echo Grub configuration has been updated
debugPause

The echo statement will allow you to see while the post install script is running that your efibootmgr code is running. The debugPause will pause the code while running in debug mode.

[marted]

@george1421 thank you !

[Sebastian Roth]

@marted Looking good.