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
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 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.
@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?
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.
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.
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.
Hello,
Any luck with incorporating the 0.3.20 into FOG? Also, is there something I can check or turn on the debug/partclone logs? Nothing ever shows up in /var/logs
Thanks
@george1421 I mean, it is not great news that you ran into trouble with the libraries but great news you are working on it and far enough a long to ‘do things’ with the library. But I digress, I was half asleep when I made the first reply. I looked at it now and was like… I should explain
I am super excited to get the Hackintosh all backed up with FOG.
@george1421 said in Fog stops at init.xz...ok:
FWIW: Those HP dc7800 and dc7900 are a pita to get to pxe boot well. The kernel for the dc7800s is 4.15.2 that works. Someone else in the forum just got it working what that old kernel.
That was me. The only reason I was able to figure it out - the dc7800’s worked fine until I upgraded the FOG server. I just kept going back through the older kernels which were out around the time the FOG server was initially installed. 4.15.2 was the first one I came to that worked. Older ones would probably work too.
@george1421 That is great news. Thanks for all your help.
@george1421 Cool, I can’t wait!
Both of my drives in that laptop are the same size and model
I noticed something weird about CloneZilla live. When I first booted from it, the Windows drive became /dev/sdb. I only noticed because I chose to back up from /sdb to the external and saw NTFS. No big deal, I rebooted again and chose to back up /sda to external, well guess what, it was the Windows drive again. I am not sure why it would change like that. It gave me flashback to having 2 NVMe drives where one may or may not initialize before the other.
3.13 that comes on the latest dev-branch as of today has issues with APFS on my laptop.
3.20 x64 does not
@george1421 .The problem is with partclone 3.13
Version 3.20 appears to work.
I am using CloneZilla Live to get the mac drive copied to an external. Can you guys add partclone 3.20 for FOG?
@george1421 I guess it may be a while until partclone gets sorted. It looks like
Should I capture as a raw image? Clonezilla live 3.0 claims to support apfs and at one time I was able to capture both drives on the laptop sort of recently. IDK
@george1421 Hello George,
I was running a debug prior to posting this thread.
This is the error (from OP) when trying to capture the APFS partition on the mac OS SSD, which is /dev/sdb.
The Microsoft EFI boot files as well as the mac OS bootloader are located within the EFI partition on /dev/sdb, the mac OS drive.
Here are the results of the fdisk on both sda and sdb
Green blocks - blocking my face in the reflection.
Task - debug - host primary disk set to capture /dev/sdb. Image type is the following
I also tried “Apple Mac Os” as the operating system instead of “Other” but got the same results.
It captures the EFI on /dev/sdb fine
But same error when it tries to capture the APFS partition
For whatever reason there isn’t a partclone.log in /var/log/ this time either.
