SOLVED
I was on 18.04 and ran “sudo do-release-upgrade -d”, It finished, I rebooted and was able to access the FOG web interface and deploy an image. I am running the latest stable version: 1.5.8
UPDATE: I had some issues when I upgraded to 20.04 on a different FOG box. It has been resolved.
Thanks
@sebastian-roth The error during the FOG install on 21.10 is related to installing php 8.0 mysql
If I try to manually install php8.0-mysql it appears to be installed already
The GUI works fine and capturing an image goes smoothly until the end where the database needs to be updated
Wow, so I ran the FOG installer again, this time there wasn’t an error when it came to the mysql install.
Going to try capturing an image now.
Hmm. It still fails to update the database.
Yes.
I just want to add real quick, the DC 7800’s can boot to the menu with any kernel and without and kernel parameters. They fail when deploying.
I installed the leaked dev version 21996/21996.1 on bare metal and in a VM. Secure Boot didn’t have to be enabled . UEFI and TPM (which requires CSM to be disabled) had to be. Secure Boot - the option only had to be present.
After more testing. I found I could install it in a VM as Legacy. I guess MS laxed on the VM requirements?
I also found on metal, I could disable TPM and enable CSM which should make secure boot completely unavailable. Then I deploy a sysprep-ed Win 11OOBE UEFI image on it without any problems.
I will try pure legacy on metal next…
This was with that leaked dev build so who knows if it was modified or what not and how close it is to the actual dev build release or the final release.
3.13 that comes on the latest dev-branch as of today has issues with APFS on my laptop.
3.20 x64 does not
Hell yeah dude, that cleared it right up.
Not sure if this has been resolved or if this helps -
I’ve created a Win 10 UEFI VM using the 2004 ISO. VMware
Workstation 15 Pro 15.5.6 build-16341506. All the settings were default except I went up tp 8GB of RAM. I installed it, ran all the updates, activated it while waiting for updates, rebooted twice then captured the image with FOG dev-branch version: 1.5.9-RC2.11 running on Ubuntu 20.04 LTS
It deployed fine to a similar VM.
@sebastian-roth Thanks. I just updated to the latest. So far it is capturing an APFS drive on a hackintosh no problem.
So yes, this is a perfect solution since Primary host disk can now be set by size. I have one image for the OS disk, and one for the “D” drive. I just switch the Primary Host disk setting depending on which image I want to capture or deploy.
@george1421 I boot from a FOS usb stick that pxe boots to the FOG server. So I am thinking put the T2 Kernel on the server and specify that kernel under the “host kernel” setting for the macs, then on the the FOS stick put the t2 kernel as well?
@will said in M.2 not recognised during deploying stage:
But when put these 2 modules together
What do you mean by put them together? Like in onboard RAID?
Is it possible like with NVMe drives, the M.2s are initializing at different times during the boot process and the drives switch places? Like changes from say /dev/nvme0n1 to /dev/nvme1n1?
@sebastian-roth Sure will do that now.
Also going to restore snapshot then upgrade to 22.04, use those commands listed above, then install the latest FOG dev (175)
@sebastian-roth I just noticed .177 was out and updated. No errors at all during the update process.
@george1421 Yes.
I just started backing up a Windows drive using 1.5.9.215. I saw Partclone 3.20 briefly appear on the screen. For some reason, while it is backing up a partition the version number of Part Clone isn’t listed. Only for a moment between capturing each partition is the version number displayed.
Thanks Tom, that fixed it right up. I guess I overlooked that file when copying everything from the original /images.
Yeah, that fdrive number… 
It is the serial number of the drive.
The NVME drives initialize differently each time during boot. I guess that is a thing, so nvme0 would sometimes be nvme1. It was a mess. Then I learned drive size could be used to differentiate between drives under Host Primary Disk. Now that both of my NVME drives are the same size, I have to use the drive serial number.