June 3, 2026
Bad Apple or bad vibes?
I Found a Bug in Apple's Fsck_hfs
Apple’s disk checker cried disaster, and the comments turned into a tech family feud
TLDR: A user says Apple’s disk repair tool falsely claimed a huge drive was damaged, when the real bug was in Apple’s own software on lower-memory Macs. Commenters turned it into a debate over bad hardware, ancient Apple code, and whether anyone should still trust this old file system at all.
An Apple user went full internet detective after their giant 24TB external drive kept getting flagged as “corrupted” by Apple’s built-in disk repair tool. Plot twist: according to the write-up, the drive wasn’t dying at all. The real problem was Apple’s own checker getting overwhelmed on some Macs with just 8GB of memory, throwing a scary false alarm while the actual files stayed safe. For anyone who has ever seen a terrifying warning box and immediately pictured their life flashing before their eyes, this was deeply relatable nightmare fuel.
But the real show was in the comments, where the community instantly split into camps. One side went straight into skeptic mode: was this really Apple’s fault, or just a bad hard drive pretending to be a software bug? Another commenter delivered the most delicious twist of all by casually saying they may have written that code back in 2006, which is the kind of unexpected cameo that makes nerdy internet threads feel like reality TV. Then came the veteran hot takes: people calling Apple’s old HFS+ format basically a museum exhibit, warning that this is ancient tech still shambling around in modern machines. And, because this is the internet, one person refused to even engage with the story because it was on Medium, which is such a comments-section move it almost deserves its own award.
So yes, the article is about a bug. But the comments are about trust, tech debt, and whether old Apple code is haunted.
Key Points
- •The article reports that Apple’s `fsck_hfs` on macOS Sequoia can falsely report corruption on large HFS+ volumes.
- •The reported issue is described as a cache exhaustion bug in the hfs-683.x version line of `fsck_hfs`.
- •According to the article, the bug appears on machines with 8 GB of RAM when checking HFS+ volumes of 24 TB or larger.
- •The failure occurs during the extended attributes file check and can produce `Couldn't read node` errors.
- •The article states that systems with 16 GB or more of RAM and older macOS versions are not affected.