FOG Project

Fog_Newb

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

Fog_Newb

@Sebastian-Roth

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.

Fog_Newb

@Sebastian-Roth

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.

Fog_Newb

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.

Fog_Newb

@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?

Fog_Newb

@Sebastian-Roth

Hell yeah dude, that cleared it right up.

Fog_Newb

@Sebastian-Roth

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.

Fog_Newb

@sebastian-roth

I used the latest inits and I was able to capture the mac OS drive. I forgot about needing the debug option to get the partclone log.

I didn’t know the dev inits were using the disk size option. I try to keep up on that by going here.
https://github.com/FOGProject/fogproject/compare/dev-branch

Thanks for your time.

Fog_Newb

Hello,

I backed up my hackintosh no problem on the 28th, just 3 days ago and was using whichever the latest dev branch was and the NVMe inits found here. https://fogproject.org/inits/init-disk-size.xz

There are 2 NVMe drives each with their own OS and EFI.

It captures the Win 10 drive sda and all the partitions no problem.

When it starts to capture the mac OS drive I get a bitmap error and am told to check var/logs/partclone.log but it is not there.

Ubuntu 21.04 Desktop

I can’t seem to find the FOG error logs that show anything. Any help would be greatly appreciated.

Thank you.

Fog_Newb

@sebastian-roth

Are the new version going to have inits that use the device size? I am still copying over those custom ones after every update.

Fog_Newb

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.