Repeated Error: Found File Extent Overlap

Yesterday my iMac 2017 running Monterey informed me that all of the drives attached (1 internal fusion drive and 3 external drives) were full and couldn't be written to. All four drives were reporting to have plenty of space when opening them up in the Finder. I went into recovery mode and ran first aid. The regular Macintosh HD was fine, but Macintosh HD - Data reported a number of "Error: Found file extent overlap id" alerts. The program itself would then hang and I would need to reboot. I eventually decided to erase the HD, reinstall Monterey, and then restore from a Time Machine backup, going back a couple days for the restore, just in case. This seemed to work, as once it came back up, I could save to all the drives again.


Except this morning I logged back in and started experiencing the exact same issue of the computer reporting all drives as full. I ran first aid again on the Mac HD - Data drive, it again gave me a bunch of the same errors, but this time it completed the scan, said it couldn't fix it. I'm once again doing an erase/reinstall/restore to get me access, but any other tips? I'm starting to think the hardware itself is faulty.

iMac 27″ 5K, macOS 12.5

Posted on Jul 25, 2022 10:03 AM

Reply
Question marked as Top-ranking reply

Posted on Jul 26, 2022 9:31 AM

When you erased the drive did you erase the whole hidden Container or base of the Fusion Drive?


It sounds like one of the drives in your Fusion Drive setup may be failing. Run DriveDx and post the complete text reports for both the internal SSD and hard drive here using the "Additional Text" icon which looks like a piece of paper.



Similar questions

4 replies
Question marked as Top-ranking reply

Jul 26, 2022 9:31 AM in response to Kaj Trapp

When you erased the drive did you erase the whole hidden Container or base of the Fusion Drive?


It sounds like one of the drives in your Fusion Drive setup may be failing. Run DriveDx and post the complete text reports for both the internal SSD and hard drive here using the "Additional Text" icon which looks like a piece of paper.



Jul 27, 2022 10:43 AM in response to Kaj Trapp

Well it's been about 48 hours since the last format/reinstall, and the internal drive appears to be okay now. It's passed another scan with flying colors, and there isn't any indication that it thinks any drives are full. I have no idea why the second reformatting apparently worked, but if anyone else experiences the same issue and it doesn't resolve after the first reformatting, I guess my advice is to try it one more time.

Jul 26, 2022 9:54 AM in response to HWTech

I erased the whole drive.


Oddly enough, the second erase/reinstall/restore seemed to work. It's been nearly 24 hours since I did that, and everything remains normal. After the first reinstall, it started spitting out full HD errors within 12 hours.


I've attached the report log showing that everything appears to be normal. The only thing showing up as under 75% are the temperature sensors. Guess I need to clean out the vents and remove a few things from behind the computer. But they're still showing as "okay", and I doubt that was the cause.


Very odd, but it appears that the second reinstall worked.


Jul 26, 2022 10:31 AM in response to Kaj Trapp

The drives look Ok. The low percentages for the temperature related attributes is due to DriveDx not interpreting them properly. Most drives only list a single (or perhaps two) temperature attributes so DriveDx was not expecting this. Temperature attributes are display & interpreted differently. Just ignore the low percentages for the temps as the maximum temp for the SSD was well within the normal operating range.


The only oddity I can see is the transfer test rate of the hard drive was much faster (significantly) than for the SSD which makes no sense to me. I don't normally worry about those values because they are not accurate as they are usually reported as much slower than if a standard speed test had been performed.


Will be interested in how the latest erase works.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Repeated Error: Found File Extent Overlap

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.