- FOG Version: 1.4.4
- OS: Ubuntu 16.04.3 desktop
- Service Version:
- OS: Windows 8.1 Pro
Just setup a new FOG server, and setup an Alienware X51 as a new host. I entered in the product key and created a new Host Image using the web server. I setup the image as Windows 8.1, and all the defaults; Image Enabled, and Replicate boxes checked, Compression at 6 and using Partclone Gzip. I did change the Image Type to Multiple Partition Image - Single Disk as I wanted, in this case, to also clone the recovery partitions. I scheduled a basic task to upload the image from the PC. The PC had secure boot disabled, UEFI disabled Legacy Boot enabled and PXE OpRom Policy Enabled to boot to the FOG server. After scheduling the image upload and rebooting, Partclone Gzip started, mentioned a disk size of only 500 MB then finished. The task showed up as finished on the FOG server and the image size showed up as 500 MB. I attempted to deploy the image to an identical Alienware X51 and it showed a message “The target partition size (368 MB) is smaller than the source (525 MB) Use option -C to disable size checking(Dangerous)” but then it said it would continue in a minute and it did a reboot and said the job was finished on the FOG server. I switched the PC host back to UEFI and secure boot and it failed to load Windows (no change as this HDD is wiped which is why I’m surprised it said the target partition was only 368 when there were no partitions on it).
This is where my biggest problem begins, I change my boot options in the bios back to normal and Windows 8.1 boots to a recovery screen and I attempt the “troubleshoot startup problems”. Reboot and the bios does not even see a Windows Boot Manager. I am worried I have lost my data and reinstalling Windows without the Alienware recovery partition results in Windows never being able to activate again unless you buy new licenses.
I am very new to FOG and desperately need some help as I’m trying everything I can but If I lost those recovery partitions I’m screwed.
I have confirmed the partitions are still alive on the source PC but what could FOG have done to corrupt it’s boot manager if it was just supposed to be an upload…
Picture of Partitions