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

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

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.

@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

Hell yeah dude, that cleared it right up.

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

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

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.

@junkhacker

Thank you

It would be cool if when viewing your images in the Web UI it displayed the amount of space it took up on the server.

Thank you

@tom-elliott

Are there any plans to make a windows/mac/linux app that would allow FOG images to be mounted and read allowing the user to copy files from an image?

Thanks

@tom-elliott

Thank you

@tom-elliott

The 1.5.9.86 install completed.

• Skipping package: php7.4-gettext…(Does not exist)

fog_error_1.5.9.86.log

@tom-elliott

I tried the latest dev branch 1.5.9.85 and the same problem occurredfog_error_1.5.9.85.log .

Run the install with the -X switch. I ran into this the other night.

https://forums.fogproject.org/topic/15370/dev-branch-1-5-9-79-installing-package-php-gettext-failed-has-to-use-x-switch-to-get-it-to-work/2?_=1620026956491

@sebastian-roth

Okay. I will try it later. I was going to post this under Bug Reports initially but I wasn’t sure if something was up with my Ubuntu install. This is the first time I installed Desktop Ubuntu. I am a wicked newb and could not figure out how to properly make the EFI\ESP partition to EFI boot Ubuntu with the server install.