It appears like my important APFS Container acquired damaged by some MBR document after putting in OpenCore Legacy Patcher and rebooting few instances. Mac is now not booting and never recognising APFS Container. I see Invalid partition tableError loading working systemMissing working system
within the first 512 bytes of APFS partition, which appears like MBR.
After updating my MacBook Professional Mid 2015 to macOS Ventura utilizing OpenCore Legacy Patcher all the things labored nice and Mac was booting and dealing simply nice.
Nevertheless, subsequent morning it did not boot after I tried to wake it from sleep, it reveals the next three choices on boot:
Bootkicker.efi
, OpenShell.efi
and Reset NVRAM
This is output from gpt:
Booting from exterior drive nonetheless labored and diskutil reveals that inside drive can’t be mounted as file system is unrecognised:
I’ve created a picture from the disk to experiment and attempt to get better it.
Checking with apfs instruments confirmed that APFS construction is damaged and it appears prefer it was overwritten with some MBR, see dump
Subsequent I discovered this query on StackExchange and adopted analysis Unable in addition on my APFS partition
I could not discover NXSB superblock that regarded much like anticipated one, just a few random NXSB strings on the disk. However I do see a number of APSB’s initially of APFS partition that look reliable. So I attempted to do comparable trick with NXSB by taking first 512 bytes from my working exterior APFS drive that I am booting from, however that did not work, disk connected as following:
And this is output of diskutil repairVolume disk7s2
:
Began file system restore on disk7s2 Checking storage system and repairing if essential and if doable Performing fsck_apfs -y -x /dev/disk7s2 error: object (oid 0x1): o_cksum (0xc271d5ca22a06a4f) is invalid for object
UFS Explorer discovered the next “partition”, it has references to “Macintosh HD”, “Restoration” in addition to some set up log which appears to correspond to the Ventura set up. Nevertheless this partition is simply 2.86 GB in measurement: