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

[marted]

@Sebastian-Roth sorry for my late response but I wanted to test everything before asking you again for help.
Now the problem is that I see the rEfind menu in some model UEFI (HP 800 G2 UEFI) and on other HP 800 G4 UEFI), the boot stays on the message rEFInd initializing and does nothing.
Furthermore, on the first one model where I see the menu, I still don’t understand something - I added the menuentry for grub2win you suggested and I cannot see it. After I deactivated ALL entries and still see the same menu on boot! Do I have to run some command to apply the changes in refind.conf file or it applies the changes every time it boots?
Just to mention we compare the BIOS of both two computers G2 and G4 and they are equal, secure boot disable and legacy disable.

[Sebastian Roth]

@marted Try the latest rEFInd version you find here: http://sourceforge.net/projects/refind/files/0.11.4/refind-bin-0.11.4.zip/download

See if those work better than the ones we have as default.

After I deactivated ALL entries and still see the same menu on boot! Do I have to run some command to apply the changes in refind.conf file or it applies the changes every time it boots?

Changes should be active on the next boot as soon as you save the file. Though I haven’t played much with the config lately. Maybe there is some option that I have forgotten about that you need to enable/add/change/remove to make those boot entries work. @george1421 would you have an idea?

[marted]

@Sebastian, from the downloaded zip file, do I need just to find the .efi file x64 and replace the old one on the server with it? what about the .conf example in the zip? Do I have to copy it also to the server replacing the old one?

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