This problem occurred round a month in the past. Randomly, my macbook would freeze:
- Software stops responding (spinning wheel).
- After a number of sec, pointer stops shifting / disappears and time stops operating. Caps lock doesn’t reply. Trackpad pressure click on stops working.
- Music nonetheless performs.
- Doesn’t reply to unplugging monitor.
- 50% probability it is going to get better after 10-30 sec, however then 99% probability it will seem a second time and will not get better.
- After 1-2 min display screen turns black.
- 1-2 min after that it reboots.
The one log associated is panic file:
{"bug_type":"210","timestamp":"2026-04-15 18:47:14.00 -0400","os_version":"macOS 12.6.7 (21G651)","incident_id":"56909DAD-A0EF-4928-9DF0-56913333A6B0"}
{
"construct" : "macOS 12.6.7 (21G651)",
"product" : "MacBookPro18,2",
"socId" : "0x00006001",
"kernel" : "Darwin Kernel Model 21.6.0: Thu Jun 8 23:56:13 PDT 2023; root:xnu-8020.240.18.701.6~1/RELEASE_ARM64_T6000",
"incident" : "56909DAD-A0EF-4928-9DF0-56913333A6B0",
"crashReporterKey" : "99D13F6C-BA88-AE1B-AD5F-0D5CC7540C88",
"date" : "2026-04-15 18:47:16.20 -0400",
"panicString" : "SOCD report detected: (iBoot panic)",
"panicFlags" : "0x0",
"SOCDContainer" : "U09DRAAgAAAAAQMAAAAAAAAAAAAIAD0AAAAAAAAAAAAAAgAAYQUAALrX1yVmCDRZouOAG+XMPwiQ1/8NpvevRwAAAABBAAAAfgBIAAAAaUJvb3QgUGFuaWM6IDogNDk2MjIxMWIwM2Q3MDZkOjE1MwpCb2FyZDogajMxNmNhcDoweDUgCkNoaXA6IDYwMDE6MHgxMSAKQnVpbGQ6IFJFTEVBU0U6aUJvb3QtODQyMi4xMjEuMSBAMHgwMDAwMDAwMWZjMGE5M2M0AAAAEJkK/AEAAADEkwr8AQAAAKCTCvwBAAAA7O8T/AEAAABU8BP8AQAAAODoE/wBAAAAgKQF/AEAAAA0owX8AQAAAKCaCvwBAAAAAAAAAG8XAABOxRxi0TO/6SycMtS5lTBJ+djn9AAAAABpQm9vdCBQYW5pYzogOiBoaWJlcm5hdGVfaXNfcmVzdW1lIGlzIHRydWUgYnV0IGhpYmVybmF0ZV9sb2FkX2ltYWdlX3ByZWZsaWdodCBmYWlsZWQgd2l0aCBhbiBpbnZhbGlkIGhlYWRlciBzaWduYXR1cmUsIG1vc3QgbGlrZWx5IGR1ZSB0byBhbiB4bnUgcGFuaWMgd2hpbGUgaGliZXJuYXRpbmcgdGhlIHN5c3RlbS4KQm9hcmQ6IGozMTZjYXA6MHg1IApDaGlwOiA2MDAxOjB4MTEgCkJ1aWxkOiBSRUxFQVNFOmlCb290LTc0NTkuMTQxLjEgQDB4MDAwMDAxMDIwMDBkNmNjNAAAAJMMdb0MAyY+sUZWJ0wzLhdM9pCrpJ61yJlNYv1Auh//2JWoYe9CstEEoDiMtCbojpLdzLOFaK1470T1I7ogdKfathc5oGZI9kqG4O9g+KHoCGS/cTDKeKqBzkbscfWr9Kkx1j4B1uqMaPVqscCMb49EAJsoYMUBcHLEj+GCyZT67yqmMyiDU5Uxyn+FcfAIo0uwRaqBQJPUgfHaUypR2AXVxYzbSOiobmT4JvmXQUoauGnrj+APqvucbTRbKLmtLzo6FdKL4gJFyhipVKFBT6SWy82kLINPcVM8kEleWiQ7kWYn50AFb5aWr3fTFWzsXJlGc0qHGcpDyEfn0ECNsFcmOv+60qretq/8N31OBsULr0CtEyGtWoFgGL53xDnDKNkCuqNnJZpaCjzR9pmkhtwmRrr+8GSlS2JXr3IKut6+zqh+nojf++WDhEnVogE5qun0BF5wj5UHsIjwzggUJqQ4J+XrPe45I+kB/eaQcxNuHc0jpbVgk+lGHCxFaL9ZtGiIaUy6m2yV+KL9cZhfboakeh922yGxSWScVAaqcFOqXmRPrYtxSuLWK5rtPQrwB1Ujj8oxxnJtU2Wm1w==",
"SOCDPanicString" : "SOCD report detected: (iBoot panic)",
"binaryImages" : []
}
The SOCDContainer area is similar throughout panic recordsdata.
iBoot Panic: : 4962211b03d706d:153
Board: j316cap:0x5
Chip: 6001:0x11
Construct: RELEASE:iBoot-8422.121.1 @0x00000001fc0a93c4
iBoot Panic: : hibernate_is_resume is true however hibernate_load_image_preflight failed with an invalid header signature, more than likely as a result of an xnu panic whereas hibernating the system.
Board: j316cap:0x5
Chip: 6001:0x11
Construct: RELEASE:iBoot-7459.141.1 @0x00000102000d6cc4
The precise errors appears to be panic when waking from hibernate file. Nevertheless, hibernation is disabled:
jin@Pleasure-MBP ~> pmset -g
System-wide energy settings:
SleepDisabled 0
At present in use:
standby 0
Sleep On Energy Button 1
hibernatefile /var/vm/sleepimage
powernap 1
networkoversleep 0
disksleep 10
sleep 0 (sleep prevented by runningboardd, sharingd, powerd, bluetoothd)
hibernatemode 0
ttyskeepawake 1
displaysleep 180
tcpkeepalive 1
powermode 2
womp 1
In my understanding, when mode set to 0, hibernate file will not be written except there’s a low batt occasion (which there is not as a result of the macbook is plugged in on a regular basis).
I requested Codex to discover numerous logs and work out the trigger, however sadly it can’t discover something aside from this panic file and would fixate on this restore from hibernate failure.
One suspicion I’ve is a few form of disk failure, as a result of this problem typically correlate with heavy disk learn or write. For instance, one time I used to be importing some recordsdata to Google Drive to liberate some disk house and do not have loads different stuff open. A supporting issue is the truth that there are apfs corruptions on my quantity:
(Disk Utility in Restoration, at present)
正在“容器disk3”上运行“急救”
正在检查储存系统并在需要和可能时修复
正在执行fsck_apfs -y -x /dev/disk0s2
正在检查容器超级块。
warning: container has been mounted by APFS model 2142.120.7, which is newer than 1934.141.2
warning: disabling overallocation repairs by default; use -o to override
正在检查空间管理器。
正在检查空间管理器空闲队列树。
正在检查对象映射。
正在检查加密密钥结构。
正在检查宗卷/dev/rdisk3s1。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查文稿编号树。
正在检查fsroot树。
error: discovered file extent (id 21137506) at logical deal with 339968 past the tip of the dstream 339968
error: discovered file extent (id 90706609) at logical deal with 0 past the tip of the dstream 0
error: discovered file extent (id 139693596) at logical deal with 0 past the tip of the dstream 0
error: discovered file extent (id 153330545) at logical deal with 4096 past the tip of the dstream 4096
正在检查范围引用树。
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (12878298 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (12878301 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (12878307 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (338461987 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (338462027 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (338468371 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (338468378 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (338468469 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (338468613 + 1)
正在检查文件密钥滚动树。
正在验证宗卷对象映射空间。
warning: apfs_fs_alloc_count isn't legitimate (anticipated 479821549, precise 479821558)
发现宗卷“/dev/rdisk3s1”已损坏，需要修复。
正在检查宗卷/dev/rdisk3s2。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s2”似乎是好的。
正在检查宗卷/dev/rdisk3s3。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查快照1/1（com.apple.os.update-6BCC1101DA4D5A9FDF54AE1ED26525D3B2B685E3E543C4A2CBA5FC555EB33FB9）
正在检查fsroot树。
正在检查文件范围树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s3”似乎是好的。
正在检查宗卷/dev/rdisk3s4。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s4”似乎是好的。
正在检查宗卷/dev/rdisk3s5。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s5”似乎是好的。
正在检查宗卷/dev/rdisk3s6。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s6”似乎是好的。
正在验证已分配的空间。
warning: overallocation detected on Major machine: (0xc481da+1) bitmap deal with (0x6f47)
warning: overallocation detected on Major machine: (0xc481dd+1) bitmap deal with (0x6f47)
warning: overallocation detected on Major machine: (0xc481e3+1) bitmap deal with (0x6f47)
warning: overallocation detected on Major machine: (0x12009b7+1) bitmap deal with (0x6fce)
warning: overallocation detected on Major machine: (0x12009b9+2) bitmap deal with (0x6fce)
warning: overallocation detected on Major machine: (0x15e5314+2) bitmap deal with (0xad64)
warning: overallocation detected on Major machine: (0x15e58a9+1) bitmap deal with (0xad64)
warning: overallocation detected on Major machine: (0x9c6731e+2) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0x9c67348+1) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0x9c6736f+1) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0x9c673c9+1) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0xc7ad0d0+1) bitmap deal with (0x80e3)
warning: overallocation detected on Major machine: (0xd96b850+1) bitmap deal with (0x84dd)
warning: overallocation detected on Major machine: (0x142c8523+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c854b+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9e13+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9e1a+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9e75+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9f05+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x1ab10063+2) bitmap deal with (0x9411)
warning: overallocation detected on Major machine: (0x1ab11950+1) bitmap deal with (0x9411)
warning: overallocation detected on Major machine: (0x1ab11958+1) bitmap deal with (0x9411)
正在执行推迟修复。
error: discovered invalid file extent object (id 21137506) at logical deal with 339968
error: discovered invalid file extent object (id 90706609) at logical deal with 0
error: discovered invalid file extent object (id 139693596) at logical deal with 0
error: discovered invalid file extent object (id 153330545) at logical deal with 4096
Utilized 4/4 repairs of this sort in complete.
error: orphan/invalid bodily extent (12878298)
error: orphan/invalid bodily extent (12878301)
error: orphan/invalid bodily extent (12878307)
error: orphan/invalid bodily extent (338461987)
error: orphan/invalid bodily extent (338462027)
error: orphan/invalid bodily extent (338468371)
error: orphan/invalid bodily extent (338468378)
error: orphan/invalid bodily extent (338468469)
error: orphan/invalid bodily extent (338468613)
Utilized 9/9 repairs of this sort in complete.
Restarting after deferred repairs...
正在检查空间管理器。
正在检查空间管理器空闲队列树。
正在检查对象映射。
正在检查加密密钥结构。
正在检查宗卷/dev/rdisk3s1。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查文稿编号树。
正在检查fsroot树。
正在检查范围引用树。
正在检查文件密钥滚动树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s1”似乎是好的。
正在检查宗卷/dev/rdisk3s2。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s2”似乎是好的。
正在检查宗卷/dev/rdisk3s3。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查快照1/1（com.apple.os.update-6BCC1101DA4D5A9FDF54AE1ED26525D3B2B685E3E543C4A2CBA5FC555EB33FB9）
正在检查fsroot树。
正在检查文件范围树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s3”似乎是好的。
正在检查宗卷/dev/rdisk3s4。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s4”似乎是好的。
正在检查宗卷/dev/rdisk3s5。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s5”似乎是好的。
正在检查宗卷/dev/rdisk3s6。
正在检查APFS宗卷超级块。
正在检查对象映射。
正在检查快照元数据树。
正在检查快照元数据。
正在检查fsroot树。
正在检查范围引用树。
正在验证宗卷对象映射空间。
宗卷“/dev/rdisk3s6”似乎是好的。
正在验证已分配的空间。
warning: overallocation detected on Major machine: (0xc481da+1) bitmap deal with (0x6f47)
warning: overallocation detected on Major machine: (0xc481dd+1) bitmap deal with (0x6f47)
warning: overallocation detected on Major machine: (0xc481e3+1) bitmap deal with (0x6f47)
warning: overallocation detected on Major machine: (0x12009b7+1) bitmap deal with (0x6fce)
warning: overallocation detected on Major machine: (0x12009b9+2) bitmap deal with (0x6fce)
warning: overallocation detected on Major machine: (0x15e5314+2) bitmap deal with (0xad64)
warning: overallocation detected on Major machine: (0x15e58a9+1) bitmap deal with (0xad64)
warning: overallocation detected on Major machine: (0x9c6731e+2) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0x9c67348+1) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0x9c6736f+1) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0x9c673c9+1) bitmap deal with (0xb5cd)
warning: overallocation detected on Major machine: (0xc7ad0d0+1) bitmap deal with (0x80e3)
warning: overallocation detected on Major machine: (0xd96b850+1) bitmap deal with (0x84dd)
warning: overallocation detected on Major machine: (0x142c8523+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c854b+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9e13+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9e1a+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9e75+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x142c9f05+1) bitmap deal with (0x11061)
warning: overallocation detected on Major machine: (0x1ab10063+2) bitmap deal with (0x9411)
warning: overallocation detected on Major machine: (0x1ab11950+1) bitmap deal with (0x9411)
warning: overallocation detected on Major machine: (0x1ab11958+1) bitmap deal with (0x9411)
容器“/dev/disk0s2”似乎是好的。
储存系统检查退出代码为0。
操作成功。
Nevertheless, that is regardless of I fixing all of the corruptions final time the freeze occurs some weeks in the past
(Forgot to avoid wasting log of precise restore, that is log earlier than repairing)
-bash-3.2# diskutil checklist
/dev/disk0 (inner):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 2.0 TB disk0
1: Apple_APFS_ISC 524.3 MB disk0s1
2: Apple_APFS Container disk3 2.0 TB disk0s2
3: Apple_APFS_Recovery 5.4 GB disk0s3
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk3
Bodily Retailer disk0s2
1: APFS Quantity Backup - Knowledge 2.0 TB disk3s1
2: APFS Quantity Macintosh HD 15.4 GB disk3s3
3: APFS Quantity Preboot 452.7 MB disk3s4
4: APFS Quantity Restoration 827.4 MB disk3s5
5: APFS Quantity VM 24.6 KB disk3s6
/dev/disk4 (disk picture):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +1.9 GB disk4
1: Apple_APFS Container disk5 1.9 GB disk4s1
/dev/disk5 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1.9 GB disk5
Bodily Retailer disk4s1
1: APFS Quantity macOS Base System 1.8 GB disk5s1
-bash-3.2# fsck_apfs -n -s -d /dev/disk3
Requested cache measurement: 4096MB (64k blocks * 64kB)
** Checking the container superblock.
Checking the checkpoint with transaction ID 59407644.
warning: container has been mounted by APFS model 2142.120.7, which is newer than 1934.141.2
warning: disabling overallocation repairs by default; use -o to override
** Checking the house supervisor.
** Checking the house supervisor free queue bushes.
** Checking the thing map.
** Checking the encryption key constructions.
** Checking quantity /dev/rdisk3s1.
** Checking the APFS quantity superblock.
The amount Backup - Knowledge was formatted by asr (1933.41.2) and final modified by apfs_kext (1934.141.2).
** Checking the thing map.
Requested cache measurement: 4096MB (64k blocks * 64kB)
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the doc ID tree.
** Checking the fsroot tree.
dstream (id 107232424) has greater than 1024 clones, disabling alloced_size repairs
error: dstream (id 2338620) doesn't have an related dstream id object
error: alloced_size (6938624) of dstream (id 2338620) doesn't match calculated measurement (0)
error: discovered file extent (id 90706658) at logical deal with 0 past the tip of the dstream 0
error: discovered file extent (id 130884071) at logical deal with 12288 past the tip of the dstream 12288
error: discovered file extent (id 146365201) at logical deal with 4096 past the tip of the dstream 4096
error: discovered file extent (id 150422653) at logical deal with 7000064 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7012352 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7024640 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7036928 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7049216 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7061504 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7073792 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7086080 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7098368 past the tip of the dstream 7000064
error: discovered file extent (id 150422653) at logical deal with 7110656 past the tip of the dstream 7000064
** Checking the extent ref tree.
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (18876855 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (18876857 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (18876858 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (22958868 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (22958869 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (22960297 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (97265794 + 2)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116939816 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116939989 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116940145 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116940184 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116940401 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116940578 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116940686 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116940757 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (116940991 + 3)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (164000542 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (164000543 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (164000584 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (164000623 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (164000713 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (209375440 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (227981392 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (447807587 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (447807588 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (447813968 + 1)
warning: mismatch between extentref entry reference depend (1) and calculated fsroot entry reference depend (0) for extent (447813976 + 1)
** Checking the file key rolling tree.
** Verifying quantity object map house.
warning: apfs_fs_alloc_count isn't legitimate (anticipated 480013964, precise 480014010)
Repair apfs_fs_alloc_count(oid 0x41eb, xid 0x38a7d19)? NO
** The amount /dev/rdisk3s1 was discovered to be corrupt and must be repaired.
** Checking quantity /dev/rdisk3s2.
** Checking the APFS quantity superblock.
The amount Replace was formatted by com.apple.MobileSof (1933.41.2) and final modified by apfs_kext (1934.141.2).
** Checking the thing map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying quantity object map house.
** The amount /dev/rdisk3s2 seems to be OK.
** Checking quantity /dev/rdisk3s3.
** Checking the APFS quantity superblock.
The amount Macintosh HD was formatted by com.apple.MobileSof (1933.41.2) and final modified by apfs_kext (1934.141.2).
** Checking the thing map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking snapshot 1 of 1 (com.apple.os.update-6BCC1101DA4D5A9FDF54AE1ED26525D3B2B685E3E543C4A2CBA5FC555EB33FB9)
** Checking the fsroot tree.
** Checking the file extent tree.
** Checking the extent ref tree.
** Verifying quantity object map house.
** The amount /dev/rdisk3s3 seems to be OK.
** Checking quantity /dev/rdisk3s4.
** Checking the APFS quantity superblock.
The amount Preboot was formatted by com.apple.MobileSof (1933.41.2) and final modified by apfs_kext (1934.141.2).
** Checking the thing map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying quantity object map house.
** The amount /dev/rdisk3s4 seems to be OK.
** Checking quantity /dev/rdisk3s5.
** Checking the APFS quantity superblock.
The amount Restoration was formatted by com.apple.MobileSof (1933.41.2) and final modified by apfs_kext (1934.141.2).
** Checking the thing map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying quantity object map house.
** The amount /dev/rdisk3s5 seems to be OK.
** Checking quantity /dev/rdisk3s6.
** Checking the APFS quantity superblock.
The amount VM was formatted by com.apple.MobileSof (1933.41.2) and final modified by apfs_kext (1934.141.2).
** Checking the thing map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying quantity object map house.
** The amount /dev/rdisk3s6 seems to be OK.
** Verifying allotted house.
warning: overallocation detected on Major machine: (0x12009b7+1) bitmap deal with (0xe7c0)
warning: overallocation detected on Major machine: (0x12009b9+2) bitmap deal with (0xe7c0)
warning: overallocation detected on Major machine: (0x15e5314+2) bitmap deal with (0xe82f)
warning: overallocation detected on Major machine: (0x15e58a9+1) bitmap deal with (0xe82f)
warning: overallocation detected on Major machine: (0x5cc2882+2) bitmap deal with (0xedd9)
warning: overallocation detected on Major machine: (0x6f85c28+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f85cd5+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f85d71+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f85d98+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f85e71+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f85f22+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f85f8e+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f85fd5+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x6f860bf+3) bitmap deal with (0xef8e)
warning: overallocation detected on Major machine: (0x9c6731e+2) bitmap deal with (0xf0aa)
warning: overallocation detected on Major machine: (0x9c67348+1) bitmap deal with (0xf0aa)
warning: overallocation detected on Major machine: (0x9c6736f+1) bitmap deal with (0xf0aa)
warning: overallocation detected on Major machine: (0x9c673c9+1) bitmap deal with (0xf0aa)
warning: overallocation detected on Major machine: (0xc7ad0d0+1) bitmap deal with (0xf366)
warning: overallocation detected on Major machine: (0xd96b850+1) bitmap deal with (0xf48c)
warning: overallocation detected on Major machine: (0x1ab10063+2) bitmap deal with (0xff94)
warning: overallocation detected on Major machine: (0x1ab11950+1) bitmap deal with (0xff94)
warning: overallocation detected on Major machine: (0x1ab11958+1) bitmap deal with (0xff94)
House allocation abstract:
class block depend
-------- -----------
container 28103
spaceman 44997
omap 14565
fs root tree 1169736
extent ref tree 156788
quantity metadata 15
file knowledge 482766154
Whole blocks marked by fsck: 484180358
Whole blocks allotted by spaceman: 484180404
** Performing deferred repairs.
Requested cache measurement: 4096MB (64k blocks * 64kB)
error: discovered invalid file extent object (id 90706658) at logical deal with 0
Take away orphan/invalid file extent objects? NO
Skipped 13/13 repairs of this sort in complete.
error: dstream (id 2338620) doesn't have an related dstream id object
Insert lacking dstream id objects? NO
Skipped 2/2 repairs of this sort in complete.
error: orphan/invalid bodily extent (18876855)
Take away orphan/invalid bodily extent objects? NO
Skipped 27/27 repairs of this sort in complete.
Deferred repairs skipped.
** The container /dev/disk3 couldn't be verified fully.
Undecided if these present disk failure, or is it only a results of kernel panics and unclean fs “unmount”. However apfs makes use of checkpoint/cow and energy failure should not trigger fs errors?
Operating Apple Diagnostics (some weeks in the past after a freeze and reboot) yields regular end result (nothing discovered).
Any concepts what I can strive subsequent?
