apfsclone.c: bitmap error when trying to capture mac OS drive
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: 126.96.36.199 on Ubuntu 21.10
I looked for /var/log/partclone.log on the FOG box but it was not there.
Pics linked below
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
@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 That is great news. Thanks for all your help.
@fog_newb I ran into some compile issues with partclone 0.3.20 tonight. Its giving me an error about a missing library that I can’t work around at the moment. I’ll have to pick this up tomorrow but I think I’m pretty close.
@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.
@fog_newb I think its possible to do it, with 3.20. I’ll have to rebuild the FOS operating system to make it happen. But I have a dev environment that I can get it done. Let me see what I can do over night. The output will be a new init.xz file for testing.
@fog_newb The short answer is maybe, depending on where the clonezilla guys got 3.20. I looked on the author’s web site and his is only 3.15. So someone must have forked his version and fixed stuff.
@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?
@fog_newb The raw or dd version should capture everything, its going to be a bigger captured image and slower to capture it, but it should work. You will at least have a clone / backup of the system that way.
@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
@fog_newb Well it appears that parclone has “immature support” for apfs volumes. It looks like clonezilla has a similar issue: https://github.com/rescuezilla/rescuezilla/issues/65
@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.
@fog_newb If you want to capture all disks leave the primary disk field blank. If you just want the boot disk then enter /dev/sda in the primary disk field. (I have a suspicion that you should do that if you are cloning all disks, but I have not personally tried to capture a computer with 2 disks.
OK the next command is
fdisk -l /dev/sda
The next step is if you did setup a debug capture (ticked the debug checkbox before you hit the submit capture job). Issue the following command
fogat the FOS Linux command prompt. You will single step through the capture script. I want you to pay attention to the blue partclone screens for any error messages scrawled across the screen. If you see it at the next break point, press ctrl-c to exit out of the imaging script. Record that error on the partclone screen. Also note on the partclone screen it should say something about apfs. The log file will be on the FOS Linux engine so you can inspect it for other error messages at
If none of the above help to find the root of the error then lets manually mount /dev/sda2 using the FOS Linux engine to see if it can see the actual files.
@george1421 Thanks, okay got it.
@fog_newb At the debug command prompt (as in the pict) key in
lsblkand post the results here.
(don’t do this until I can see the output of lsblk) Hopefully you scheduled a debug capture because to start the capture process just key in
foghere and it should single step through the imaging process.