Post #1721877
2026-04-09 18:48 UTC
Why This Happens:
"HFS+ was designed in 1998 and uses 32-bit block addressing internally.
On very large volumes, the extended attributes B-tree node placement calculations produce an invalid node at a specific location — node #61432 on 24TB volumes — that fsck cannot read. This is a fundamental arithmetic limitation of HFS+ with modern large drives, not a hardware or cable issue."
Replies (1)
-
@morst@toad.social 2026-04-14 05:43
Oh shit Turns out this is only a problem on the M1 Mac mini! Sorry to alarm everybody. https://medium.com/@kivancgunalp/macos-fsck-hfs-fails-on-24tb-hfs-volumes-but-only-on-mac-mini-m1-11ef778484dc