@humoss233 Great to see George has come up with the correct set of kernel options for your crypto setup.
At this point I think we are hitting kind of a wall. We might find a hole through but I am not sure yet.
FOG is made to capture whole disks, so one of the first things it does is get a list of partitions from the device. This surely fails on
/dev/mapper/crypto. There is an option in FOG that you can use to make it capture only one single partition (in the host’s settings you have Partition - defaults to Everything) but the script code as it exists right now would still try to enumerate the partitions and bail out.
So looking at your
lsblk output my first idea was to set Host Primary Disk to
/dev/md126 and create a symbolic link pointing from
mapper/crypt. But that doesn’t work because
/dev/md126p3 device file already exists. Hmmmm, well maybe you can delete it. It’s not an issue in the live FOS Linux because on reboot it will be restored. Try this:
mdadm -D /dev/md126
cryptsetup luksOpen /dev/md126p3 crypt
ln -s /dev/mapper/crypt /dev/md126p3