This issue occurred around a month ago. Randomly, my macbook would freeze:
- Application stops responding (spinning wheel)
- After a few sec, pointer stops moving / disappears and time stops running. Caps lock does not respond. Trackpad force click stops working
- Music still plays
- Does not respond to unplugging monitor
- 50% chance it will recover after 10-30 sec, but then 99% chance it would appear a second time and won’t recover
- After 1-2 min screen turns black
- 1-2 min after that mac reboots
The only log related 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"}
{
"build" : "macOS 12.6.7 (21G651)",
"product" : "MacBookPro18,2",
"socId" : "0x00006001",
"kernel" : "Darwin Kernel Version 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 field is the same across panic files.
iBoot Panic: : 4962211b03d706d:153
Board: j316cap:0x5
Chip: 6001:0x11
Build: RELEASE:iBoot-8422.121.1 @0x00000001fc0a93c4
iBoot Panic: : hibernate_is_resume is true but hibernate_load_image_preflight failed with an invalid header signature, most likely due to an xnu panic while hibernating the system.
Board: j316cap:0x5
Chip: 6001:0x11
Build: RELEASE:iBoot-7459.141.1 @0x00000102000d6cc4
The specific errors seems to be panic when waking from hibernate file. However, hibernation is disabled:
jin@Joy-MBP ~> pmset -g
System-wide power settings:
SleepDisabled 0
Currently in use:
standby 0
Sleep On Power 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 won’t be written unless there is a low batt event (which there isn’t because the macbook is plugged in all the time).
I asked Codex to explore various logs and figure out the cause, but unfortunately it cannot find anything other than this panic file and would fixate on this restore from hibernate failure.
One suspicion I have is some kind of disk failure, because this issue sometimes correlate with heavy disk read or write. For example, one time I was uploading some files to Google Drive to free up some disk space and don’t have a lot other stuff open. A supporting factor is the fact that there are apfs corruptions on my volume:
(Disk Utility in Recovery, today)
正在“容器disk3”上运行“急救”
正在检查储存系统并在需要和可能时修复
正在执行fsck_apfs -y -x /dev/disk0s2
正在检查容器超级块。
warning: container has been mounted by APFS version 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: found file extent (id 21137506) at logical address 339968 beyond the end of the dstream 339968
error: found file extent (id 90706609) at logical address 0 beyond the end of the dstream 0
error: found file extent (id 139693596) at logical address 0 beyond the end of the dstream 0
error: found file extent (id 153330545) at logical address 4096 beyond the end of the dstream 4096
正在检查范围引用树。
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (12878298 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (12878301 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (12878307 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (338461987 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (338462027 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (338468371 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (338468378 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (338468469 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (338468613 + 1)
正在检查文件密钥滚动树。
正在验证宗卷对象映射空间。
warning: apfs_fs_alloc_count is not valid (expected 479821549, actual 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 Main device: (0xc481da+1) bitmap address (0x6f47)
warning: overallocation detected on Main device: (0xc481dd+1) bitmap address (0x6f47)
warning: overallocation detected on Main device: (0xc481e3+1) bitmap address (0x6f47)
warning: overallocation detected on Main device: (0x12009b7+1) bitmap address (0x6fce)
warning: overallocation detected on Main device: (0x12009b9+2) bitmap address (0x6fce)
warning: overallocation detected on Main device: (0x15e5314+2) bitmap address (0xad64)
warning: overallocation detected on Main device: (0x15e58a9+1) bitmap address (0xad64)
warning: overallocation detected on Main device: (0x9c6731e+2) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0x9c67348+1) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0x9c6736f+1) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0x9c673c9+1) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0xc7ad0d0+1) bitmap address (0x80e3)
warning: overallocation detected on Main device: (0xd96b850+1) bitmap address (0x84dd)
warning: overallocation detected on Main device: (0x142c8523+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c854b+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9e13+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9e1a+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9e75+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9f05+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x1ab10063+2) bitmap address (0x9411)
warning: overallocation detected on Main device: (0x1ab11950+1) bitmap address (0x9411)
warning: overallocation detected on Main device: (0x1ab11958+1) bitmap address (0x9411)
正在执行推迟修复。
error: found invalid file extent object (id 21137506) at logical address 339968
error: found invalid file extent object (id 90706609) at logical address 0
error: found invalid file extent object (id 139693596) at logical address 0
error: found invalid file extent object (id 153330545) at logical address 4096
Applied 4/4 repairs of this type in total.
error: orphan/invalid physical extent (12878298)
error: orphan/invalid physical extent (12878301)
error: orphan/invalid physical extent (12878307)
error: orphan/invalid physical extent (338461987)
error: orphan/invalid physical extent (338462027)
error: orphan/invalid physical extent (338468371)
error: orphan/invalid physical extent (338468378)
error: orphan/invalid physical extent (338468469)
error: orphan/invalid physical extent (338468613)
Applied 9/9 repairs of this type in total.
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 Main device: (0xc481da+1) bitmap address (0x6f47)
warning: overallocation detected on Main device: (0xc481dd+1) bitmap address (0x6f47)
warning: overallocation detected on Main device: (0xc481e3+1) bitmap address (0x6f47)
warning: overallocation detected on Main device: (0x12009b7+1) bitmap address (0x6fce)
warning: overallocation detected on Main device: (0x12009b9+2) bitmap address (0x6fce)
warning: overallocation detected on Main device: (0x15e5314+2) bitmap address (0xad64)
warning: overallocation detected on Main device: (0x15e58a9+1) bitmap address (0xad64)
warning: overallocation detected on Main device: (0x9c6731e+2) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0x9c67348+1) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0x9c6736f+1) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0x9c673c9+1) bitmap address (0xb5cd)
warning: overallocation detected on Main device: (0xc7ad0d0+1) bitmap address (0x80e3)
warning: overallocation detected on Main device: (0xd96b850+1) bitmap address (0x84dd)
warning: overallocation detected on Main device: (0x142c8523+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c854b+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9e13+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9e1a+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9e75+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x142c9f05+1) bitmap address (0x11061)
warning: overallocation detected on Main device: (0x1ab10063+2) bitmap address (0x9411)
warning: overallocation detected on Main device: (0x1ab11950+1) bitmap address (0x9411)
warning: overallocation detected on Main device: (0x1ab11958+1) bitmap address (0x9411)
容器“/dev/disk0s2”似乎是好的。
储存系统检查退出代码为0。
操作成功。
However, this is despite I fixing all the corruptions last time the freeze happens some weeks ago
(Forgot to save log of actual repair, this is log before repairing)
-bash-3.2# diskutil list
/dev/disk0 (internal):
#: 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
Physical Store disk0s2
1: APFS Volume Backup - Data 2.0 TB disk3s1
2: APFS Volume Macintosh HD 15.4 GB disk3s3
3: APFS Volume Preboot 452.7 MB disk3s4
4: APFS Volume Recovery 827.4 MB disk3s5
5: APFS Volume VM 24.6 KB disk3s6
/dev/disk4 (disk image):
#: 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
Physical Store disk4s1
1: APFS Volume macOS Base System 1.8 GB disk5s1
-bash-3.2# fsck_apfs -n -s -d /dev/disk3
Requested cache size: 4096MB (64k blocks * 64kB)
** Checking the container superblock.
Checking the checkpoint with transaction ID 59407644.
warning: container has been mounted by APFS version 2142.120.7, which is newer than 1934.141.2
warning: disabling overallocation repairs by default; use -o to override
** Checking the space manager.
** Checking the space manager free queue trees.
** Checking the object map.
** Checking the encryption key structures.
** Checking volume /dev/rdisk3s1.
** Checking the APFS volume superblock.
The volume Backup - Data was formatted by asr (1933.41.2) and last modified by apfs_kext (1934.141.2).
** Checking the object map.
Requested cache size: 4096MB (64k blocks * 64kB)
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the document ID tree.
** Checking the fsroot tree.
dstream (id 107232424) has more than 1024 clones, disabling alloced_size repairs
error: dstream (id 2338620) does not have an associated dstream id object
error: alloced_size (6938624) of dstream (id 2338620) does not match calculated size (0)
error: found file extent (id 90706658) at logical address 0 beyond the end of the dstream 0
error: found file extent (id 130884071) at logical address 12288 beyond the end of the dstream 12288
error: found file extent (id 146365201) at logical address 4096 beyond the end of the dstream 4096
error: found file extent (id 150422653) at logical address 7000064 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7012352 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7024640 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7036928 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7049216 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7061504 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7073792 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7086080 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7098368 beyond the end of the dstream 7000064
error: found file extent (id 150422653) at logical address 7110656 beyond the end of the dstream 7000064
** Checking the extent ref tree.
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (18876855 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (18876857 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (18876858 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (22958868 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (22958869 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (22960297 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (97265794 + 2)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116939816 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116939989 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116940145 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116940184 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116940401 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116940578 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116940686 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116940757 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (116940991 + 3)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (164000542 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (164000543 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (164000584 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (164000623 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (164000713 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (209375440 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (227981392 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (447807587 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (447807588 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (447813968 + 1)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (447813976 + 1)
** Checking the file key rolling tree.
** Verifying volume object map space.
warning: apfs_fs_alloc_count is not valid (expected 480013964, actual 480014010)
Fix apfs_fs_alloc_count(oid 0x41eb, xid 0x38a7d19)? NO
** The volume /dev/rdisk3s1 was found to be corrupt and needs to be repaired.
** Checking volume /dev/rdisk3s2.
** Checking the APFS volume superblock.
The volume Update was formatted by com.apple.MobileSof (1933.41.2) and last modified by apfs_kext (1934.141.2).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying volume object map space.
** The volume /dev/rdisk3s2 appears to be OK.
** Checking volume /dev/rdisk3s3.
** Checking the APFS volume superblock.
The volume Macintosh HD was formatted by com.apple.MobileSof (1933.41.2) and last modified by apfs_kext (1934.141.2).
** Checking the object 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 volume object map space.
** The volume /dev/rdisk3s3 appears to be OK.
** Checking volume /dev/rdisk3s4.
** Checking the APFS volume superblock.
The volume Preboot was formatted by com.apple.MobileSof (1933.41.2) and last modified by apfs_kext (1934.141.2).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying volume object map space.
** The volume /dev/rdisk3s4 appears to be OK.
** Checking volume /dev/rdisk3s5.
** Checking the APFS volume superblock.
The volume Recovery was formatted by com.apple.MobileSof (1933.41.2) and last modified by apfs_kext (1934.141.2).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying volume object map space.
** The volume /dev/rdisk3s5 appears to be OK.
** Checking volume /dev/rdisk3s6.
** Checking the APFS volume superblock.
The volume VM was formatted by com.apple.MobileSof (1933.41.2) and last modified by apfs_kext (1934.141.2).
** Checking the object map.
** Checking the snapshot metadata tree.
** Checking the snapshot metadata.
** Checking the fsroot tree.
** Checking the extent ref tree.
** Verifying volume object map space.
** The volume /dev/rdisk3s6 appears to be OK.
** Verifying allocated space.
warning: overallocation detected on Main device: (0x12009b7+1) bitmap address (0xe7c0)
warning: overallocation detected on Main device: (0x12009b9+2) bitmap address (0xe7c0)
warning: overallocation detected on Main device: (0x15e5314+2) bitmap address (0xe82f)
warning: overallocation detected on Main device: (0x15e58a9+1) bitmap address (0xe82f)
warning: overallocation detected on Main device: (0x5cc2882+2) bitmap address (0xedd9)
warning: overallocation detected on Main device: (0x6f85c28+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f85cd5+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f85d71+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f85d98+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f85e71+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f85f22+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f85f8e+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f85fd5+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x6f860bf+3) bitmap address (0xef8e)
warning: overallocation detected on Main device: (0x9c6731e+2) bitmap address (0xf0aa)
warning: overallocation detected on Main device: (0x9c67348+1) bitmap address (0xf0aa)
warning: overallocation detected on Main device: (0x9c6736f+1) bitmap address (0xf0aa)
warning: overallocation detected on Main device: (0x9c673c9+1) bitmap address (0xf0aa)
warning: overallocation detected on Main device: (0xc7ad0d0+1) bitmap address (0xf366)
warning: overallocation detected on Main device: (0xd96b850+1) bitmap address (0xf48c)
warning: overallocation detected on Main device: (0x1ab10063+2) bitmap address (0xff94)
warning: overallocation detected on Main device: (0x1ab11950+1) bitmap address (0xff94)
warning: overallocation detected on Main device: (0x1ab11958+1) bitmap address (0xff94)
Space allocation summary:
category block count
-------- -----------
container 28103
spaceman 44997
omap 14565
fs root tree 1169736
extent ref tree 156788
volume metadata 15
file data 482766154
Total blocks marked by fsck: 484180358
Total blocks allocated by spaceman: 484180404
** Performing deferred repairs.
Requested cache size: 4096MB (64k blocks * 64kB)
error: found invalid file extent object (id 90706658) at logical address 0
Remove orphan/invalid file extent objects? NO
Skipped 13/13 repairs of this type in total.
error: dstream (id 2338620) does not have an associated dstream id object
Insert missing dstream id objects? NO
Skipped 2/2 repairs of this type in total.
error: orphan/invalid physical extent (18876855)
Remove orphan/invalid physical extent objects? NO
Skipped 27/27 repairs of this type in total.
Deferred repairs skipped.
** The container /dev/disk3 could not be verified completely.
Not sure if these show disk failure, or is it just a result of kernel panics and unclean fs “unmount”. But apfs uses checkpoint/cow and power failure shouldn’t cause fs errors?
Running Apple Diagnostics (some weeks ago after a freeze and reboot) yields normal result (nothing found). Any ideas what I can try next?
