Open fenggy09 opened 5 years ago
It looks like the APFS format might differ from the one that afro can handle. It might be a newer or older version of APFS.
May I know what model of mac did you tested Afro on? Thank you!
I tested afro with APFS version 748.31.8. The current APFS version on my Mac is 945.250.134.
Any updates on this? I'm having the same issue... @cugu : How to get the APFS version?
You can try strings /sbin/fsck_apfs | grep "fsck_apfs ("
Thank you. My APFS version is 945.260.7.
Newbie here, but from what I found was that so far: Some nodes that are being instantiated as PointerValT objects, which do not have the .ov_paddr
They are being created because their parent node looks like:
NodeEntry _on 256
NodeEntry _parent <afro.libapfs.apfs.Apfs.BtreeNodePhysT object at 0x113e8dba8>
NodeEntry btn_level 2
I tried to add .ov_paddr = None
in PointerValT._read()
(and skip them in parse_apsb()) but that doesn't recover anything. Sorry if this is meaningless, but otherwise, I'm happy to try some ideas you might have.
I can confirm this bug: with an image of a working Catalina (macOS 10.15) system, only files from VM, Preboot, and Recovery are recovered, as previously described.
However, I am able to create APFS disk images in Disk Utility on both macOS 10.14 (system APFS version: 945.275.9) and 11 (system APFS: 1677.50.1) which are successfully read and recovered using afro
. I suspect that the on-disk format (for the actual macOS system) is not the same as what Disk Utility creates in the two disk images.
When I have some time, I may be able to look through the paper and compare the previously described APFS format to my system image. I would be happy to provide any further information.
Hi, I've tried afro for recovering deleted files on a raw APFS image (500GB) but the result is always that only "Preboot", "Recovery" and "VM" volumes got recovered but not the volume where the OS is:
The log for carving kept showing errors like:
And I tried the "-m parse" option to see if same errors appear:
Would you mind explain what could be the reason for these "no attribute" errors? (parsing the OS volume leads to null objects?) Thanks very much!