Search the Community

Hi, Since the Beta threads are closed now, i thought i'd ask here too. I've tried my best to get a proper log file but everything is NUL (or <0x00> after the OpenCore debug output). I've been using Jake Lo's e7470 OC Package with a few of my own touches and have/had a very stable Big Sur environment. But twice, i have went through an APFS Container corruption, but i cant for my own sake of sanity find out what has been causing it. It just randomly happened. First time it happened, i could only isolate the randomness to two things, i logged in on the iCloud welcome screen between the Beta updates, and used Hackintool although only to read some values. None of the cases make sense to create such an issue. However, i've also isolated that i've signed to my Apple AirPort Extreme, which i strictly use as a NAS (SMB), to copy something, in both cases. In both cases, it randomly started happening after a few restarts, mostly of OS switches. It started with the initial first boot showing me this (i've ommited the values after DWORD, this line showed up at least in 5 straight rows): disk1s1: device error. void IONVMeController::HandleCompletionError(AppleNVMeRequest *, uint32_t)::5566:DWORD "SOME VALUES HERE in for a few ROWS" NVMeStatus=0x2004 Followed by the next boot (after a restart obviously): 1. This comes first nx_corruption_detected_int:55: disk1 Container corruption detected by obj_init:2775! alloc_space_for_write_with_hint:15409: spaceman_alloc() FAILED, err: 92 xid: 22501 paddr: 0 blocks requested: 1 blocks allocated: 0 2. Than an immense output of these apfs_vnop_blockmap:13735: disk1s1:0 ### obj-id 738787/738787 err 92 offset 0 size 524208 mapflags 2 destream apfs_fsync_internal:10740: disk1s1:0 cluster_push() failed with err 92 on ino apfs_vfsop_sync:4178: disk1 Container corruption detected by obj_init:2775! obj_write_prepare:4779: disk1s4:0 oid 1199 flags 0x21a1 0x0 type xid 22501 (cur xid 22501) error allocating 3. Until it stops for a bit with this: tx_flush_thread:1496: disk1 tx_flush(22501) failed, 92 # 146 (<- this number keeps increasing) And it keeps repeating this. ITLWM verbose output can be seen scanning networks and finding MAC addresses, so i assume the system itself is working but something has messed up the file system. EDIT: just some extra clarity. Big Sur resides on a 2242 SSD in the WWAN Port, running at 1x speed lanes, but it's a Western Digital PC SN520 (which happens to be SanDisk rebranded from what i could tell). First SSD is disabled via SSDT as OpenCore and MacOS really don't like it.