@Tom-Elliott said in Capture UEFI image on hyper-v VM:

6.1.89

Thanks, this worked for me.

When tasking a host, I’d get the same as @Baessens (Hyper-V).

I went to kernel update and installed 6.1.89 as per Tom’s suggestion and I was able to get past and into image deployment!

@george1421 It worked. Thanks !

@sebastian-roth Ah, my bad. I did not see that previous post. I tried snponly.efi, deploying works fine now. Thanks a lot!

Works fine now. Thanks @Sebastian-Roth !

@Baessens We there is nothing wrong with what there. What I see is a different version of undionly.kpxe for FOG 1.5.5 and 1.5.7. So the recommendation as a test take undionly.kpxe from the working FOG server and copy it over (renaming the original first) to the not working fog server then pxe boot.

If the problem goes away on the not working fog server then the problem is with undionly.kpxe if the problem stays then its with the different version of hyper-v

@Baessens In this special case I’d suggest you use basic Linux commands to export/import image definitions and sync the image files to your other node.

Optional: Create a sync user account on your main master node - otherwise you’d use the root account to do that but don’t use the fogproject account! Setup SSH keys to be able to login using the sync (or root) account from node B to node A Setup a cron job on your node B to do the DB and file sync Make sure rsync is installed on both nodes.

Here is just a quick outline of how you might do this (untested!):

#!/bin/bash ssh syncuser@nodeA mysqldump -u root -pPassw0rd fog images >/tmp/images.sql mysql -u root -pPassw0rd </tmp/images.sql rsync -ave ssh syncuser@nodeA:/images /images >>/var/log/fog/myimagesync.log 2>&1

This will wipe the images table on your node B and import all the definitions you have on node A.

@george1421 Ah, i see. I was doing it with rsync in a cron job at the moment. I’ll try out your suggestion. Thanks for the info. 🙂

@Baessens Maybe i need to change the UID of my FOG installation? ?
Edit: changed the UDPCAST INTERFACE to eth0, still same problem.

Also, Is this wrong?

ict@fogserver:/images$ ls dev postdownloadscripts Priminfowin10pro lost+found postinitscripts priminfowin10pronewofficekey ict@fogserver:/images$ cd dev ict@fogserver:/images/dev$ ls dev postdownloadscripts

EDIT: re-running the installer seemed to fix the issue.

@george1421 I didn’t know that storage nodes were deploy only. Thank for the info.

@Baessens Ahhh, I just had one more idea. Please run fdisk -l /dev/sda and post a picture as well. Possibly this is a sector size issue.