@sebastian-roth Ok thanks, I will try it out and report back. These inits, they just go on the FOG server right? Or do I also need to add something to the mac OS Grub/FOS boot stick?
Posts
-
RE: Include partclone 3.20?posted in General
-
RE: MAC address captured during registration is different than actual MAC address.posted in Mac Problems
No. I do not have any USB / Ethernet or Wifi devices. Just the built in Ethernet and WiFi. I am going to remove this registration and re-register when testing out the updated partclone inits. I’ll be sure to post what happens AFA MAC address
-
MAC address captured during registration is different than actual MAC address.posted in Mac Problems
Not sure what happened or if this is something to do with the latest mac OS (Monterey 12.5.1) security
I created a FOS USB stick and registered my mac Mini. The MAC shown in the FOG web UI after registration is different than the MAC address of the Ethernet port.
Actual mac address


MAC address seen by FOG when registering

Also, any word on when the latest partclone will be integrated into FOG so we can capture APFS images?
-
RE: Can't get to FOG booting from USB Boot UEFI clientposted in Mac Problems
@george1421 Awesome - this worked. It booted from the stick fine and I was able to perform a quick registration. I started to capture the drive and it worked up until it came to the APFS portion. I ran into the apfsclone.c: bitmap error, like with the hackintosh.
-
RE: Can't get to FOG booting from USB Boot UEFI clientposted in Mac Problems
@george1421 said in Can't get to FOG booting from USB Boot UEFI client:
FOS linux
Is there a tutorial for creating a FOS Linux usb client to work with the pre existing FOG server?
-
RE: Can't get to FOG booting from USB Boot UEFI clientposted in Mac Problems
@brakcounty
Not sure. I don’t think it gets that far but it is hard to tell. It boots from bootx64.efi (the renamed ipxe.efi) on the USB something, maybe the banner appears or whatever text when ipxe.efi loads, then the screen goes black really quick - as it reboots. I can try to take a video of what happens.
I thought about making a USB stick with an EFI partition and putting the bootx64.efi on there but not sure if it would make any difference.
-
Can't get to FOG booting from USB Boot UEFI clientposted in Mac Problems
Hi,
I followed the instructions here and created a USB Boot UEFI client.
https://forums.fogproject.org/topic/6350/usb-boot-uefi-client-into-fog-menu-easy-way/12
I disabled secure boot and enabled booting from anything. And I can boot from the USB drive, it starts to ipxe boot but then my display goes out, then a mac OS error screen really quick then it boots from the mac OS SSD.
I have a 2018 Mac Mini, I manually added the host to FOG, blah blah and added the t2kernel and specified in the settings for it to use that kernel but I don’t think it is getting that far. I am using the built in Ethernet on the mini.
Is there an updated guide for pxe booting t2 intel based macs?
-
RE: apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
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
-
RE: apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
@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.
-
RE: Fog stops at init.xz...okposted in FOG Problems
@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.
-
RE: apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
@george1421 That is great news. Thanks for all your help.
-
RE: apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
@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. -
Include partclone 3.20?posted in General
3.13 that comes on the latest dev-branch as of today has issues with APFS on my laptop.

3.20 x64 does not

-
RE: apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
@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?
-
RE: apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
@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
-
RE: apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
@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.
-
apfsclone.c: bitmap error when trying to capture mac OS driveposted in FOG Problems
I’m running into trouble capturing the mac OS SSD on my laptop. Hackintosh.
diskutility doesn’t see any problems with the mac OS SSD, no problems with the drive on the FOG server. If I set FOG to capture All drives, all partitions, not resizable it will capture the Windows SSD fine and the EFI partition on the mac OS SSD, but fails when backing up the APFS partition(s) So to save time, I just tried backing up the mac SSD. Same problem. EFI fine, APFS fails.
Here are some pics if it helps.
Latest dev-branch version: 1.5.9.154 on Ubuntu 21.10
I looked for /var/log/partclone.log on the FOG box but it was not there.
Pics linked below
Thanks
edit:typo
