0 Members and 2 Guests are viewing this topic.
Why This HappensHFS+ 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.
As long as they aren’t over 24 TB, you don’t need to worry about it. And if they were over 24 TB you wouldn’t have been able to do it. But yes, going forward new drive should have the new file system.