Does anyone know how to fix error -69845 in disk utility?

[darkpaw]

I know I am late to this thread but my 27" late 2012 iMac just kind of slammed it's head into the wall and all weekend I have been stuck in repair disk, Utilities, releasing NVRA cycle nightmares and I REALLY could use some assistance. I found this thread by googling the errors I am seeing on First Aid, and kind of did what you asked Rachel to do during this thread last year, I viewed my container and ran it on Container Disk2 and got "Storage System verify or repair failed (-69716)" and now have no clue what to do, I am good at taking direction, I have never unmounted anything but was wondering if you had any advice where to go from here? I am desperate

Have you tried running Disk Utility from the macOS Recovery system? This page has startup key combinations; you want Command (⌘)-R.

Try disk first aid on the containers, as I mentioned.

 

[Barkevious]

Have you tried running Disk Utility from the macOS Recovery system? This page has startup key combinations; you want Command (⌘)-R.

Try disk first aid on the containers, as I mentioned.

Sorry just saw this reply super late, I have run every single one of those. it gets stuck in boot loops where it gets all the way to the end and then just restarts and tries again and again. None of the utility options have fixed it. So I am making strides towards getting another mac, thunderbolting them together to put mine into target mode, see if I can at least pull the data off the HD and maybe buy a new HD for it and start over. Not sure what else I can do....

 

[vvg]

In case it helps anyone with this problem. I was running an external USB drive for my file storage, due to recent problems on my 2017 iMac, and after another system crash lost the 3Tb external drive with all its data, it was formatted ExFat. I got errors -69845 and -69874 from Disk Utility. Fortunately, when I started EaseUS Data Recovery it found the disk and, when scanning for lost files, the disk mounted on the desktop and the data all appears to be intact. Thankfully I didn't have to wait for the 33-hour scanning time to complete before being able to copy the essential data to another drive

 

[supernat10]

I keep getting fail errors when I run disk utility on "data" (see attached screenshot).

File System verify or repair failed. : (-69845)

I've tried in normal mode, safe mode and recovery mode. Any clue how to fix this without wiping my operating system? Apple doesn't seem to recognize this error and they're kind of giving me a hard time about passing this error code onto the developers so that they can tell me what this code relates to. I'm running disk utility because when I ran it a few days ago, it solved some permissions issues that werent allowing me to open Adobe After Effects. Now when I open Adobe Acrobat DC and try to embed a document with a password, the password box wont pop open (on my desktop computer) but it will on my laptop so it makes me think theres lingering permissions issue on the desktop computer. So I'm trying to repair the permissions with no luck when it comes to the "data" column in disk utility. Any help would be appreciated.

When I couldnt get into After Effects, Adobe remoted in and tried for hours to fix it, and couldnt figure it out themselves. So I'm not confident they are gonna be able to fix this one. I would like to leave them out of this if possible, because they started doing all this wild stuff to my computer to experiment with it to fix the issue, like they tried wiping all my fonts. I dont want to involve them because they always resort to the most wild things that end up being a big setback for me.


View attachment 1987456
View attachment 1987457

In case anyone else runs into this problem, you might have some luck with Windows if the file system is a Windows-supported file system. I happened to have my external drive formatted with EXT FAT, and Windows also noticed the error, but displayed the contents immediately. And checkdisk was able to fix the errors (so it says). After moving it back to Mac, it appeared again and seems operational. This is the 3rd time my drive failed when hard powering off the Mac, which unfortunately is required sometimes. I don't seem to have the same issue on other drives, just my Lacie d2 20TB drive.

 

[madrich]

I had the same problem and my Airport Utility was indicating that my Time Machine was failing. I found this link and followed the instructions. I think it is important to get into the Recovery Mode, indentify the APFS Container, but unmount the Volumes first. https://eclecticlight.co/2021/11/19...check-and-repair-apfs-volumes-and-containers/

…..so far my Time Machine is no longer reporting that it is failing!

 

[ryoching_teng]

Fantastic!

I had the same errors on TWO m1's. Appeared at the same time. Contacted Apple support they guided me through Disk Utils, shared my screen etc - all the stuff I had already done. I also formatted the disc and reinstalled, errors came back after a few days. Apple support said not to use time machine as it might be copying something over. So I formatted again and manually restored. Fine for a few days but the errors gradually came back.

Pulling my hair. out at this point. New mac studio with errors! Found this and ran disk utils on the container disk (Why apple support don't know about this is ridiculous) fixed the disk!

If you experience these kind of errors it looks like they are on the snapshots but the problem is the disk itself. Use the magic view menu first and show your snapshots. Delete them and then check the disk in recovery mode. If you keep the snapshots then when you check the disk later the errors get shown in the snapshots even though the disk is fixed as the snap shots are of the unfixed disc. This could lead to confusion over whether the disc is fixed or not

Thanks for the reminder, I finally solved it. This problem has troubled me for many years. I am used to using CCC to back up the system, but once this problem occurs, the backup will go wrong. I installed your prompt to delete all snapshots under the -Data partition and then perform "First Aid" repair to solve it. Thank you very much.

 

[DBW_Chicago]

Have you tried running Disk Utility from the macOS Recovery system? This page has startup key combinations; you want Command (⌘)-R.

Try disk first aid on the containers, as I mentioned.

Greetings darkpaw - followed the steps above in the thread - thank you - however, when I run the First Aid on the container I receive:

”warning: container has been mounted by APFS version 2235.41.1, which is newer than 1934.141.2.700.2
warning: disabling overallocation repairs by default; use -o to override”

Volume 1 checks out ok

then after the 2nd “Checking the APFS volume super lock.” There is:
”warning: apfs superblock at index1: apfs_doc_id_index_flags_has unrecognized flags (0x11)”

And

”error: btn: oid (21958177), did (11676965), type (0x100000003), subtype (0xe), flags (ox2) level (0)
error: btn: invalid value (18304, 24)
fsroot tree is invalid
The volume /dev/rdisk3s2 was found to corrupt and cannot be repaired”

All of the other four volumes “appear to be OK” - so the problem seems to be just with Volume 2

The parent drive to the container “APPLE SSD AP12024N Media” and child “Macintosh HD volumes” and that child’s “Macintosh HD” and “Macintosh HD - Data” both repair properly and check out

So do I have to erase the whole container and start over, or, is there a better solution at this point?

[My suspicion is as a novice coder I loaded things in via command line and it used the newer APFS version and f‘d things up]

And - when I open “Disk Image” there only appears to be four volumes and not six

Any guidance would be greatly appreciated - THX!!

 

[darkpaw]

Greetings darkpaw - followed the steps above in the thread - thank you - however, when I run the First Aid on the container I receive:

”warning: container has been mounted by APFS version 2235.41.1, which is newer than 1934.141.2.700.2
warning: disabling overallocation repairs by default; use -o to override”

Volume 1 checks out ok

then after the 2nd “Checking the APFS volume super lock.” There is:
”warning: apfs superblock at index1: apfs_doc_id_index_flags_has unrecognized flags (0x11)”

And

”error: btn: oid (21958177), did (11676965), type (0x100000003), subtype (0xe), flags (ox2) level (0)
error: btn: invalid value (18304, 24)
fsroot tree is invalid
The volume /dev/rdisk3s2 was found to corrupt and cannot be repaired”

All of the other four volumes “appear to be OK” - so the problem seems to be just with Volume 2

The parent drive to the container “APPLE SSD AP12024N Media” and child “Macintosh HD volumes” and that child’s “Macintosh HD” and “Macintosh HD - Data” both repair properly and check out

So do I have to erase the whole container and start over, or, is there a better solution at this point?

[My suspicion is as a novice coder I loaded things in via command line and it used the newer APFS version and f‘d things up]

And - when I open “Disk Image” there only appears to be four volumes and not six

Any guidance would be greatly appreciated - THX!!

Screenshot?

I can't really say how to fix that - I'm not a drive master by any means - but I'd keep plugging away at the repair options on all the drives and containers.

Failing that, run a full Time Machine backup, wipe the original drive, check it for errors and restore from the new backup?

 

[DBW_Chicago]

Screenshot?

I can't really say how to fix that - I'm not a drive master by any means - but I'd keep plugging away at the repair options on all the drives and containers.

Failing that, run a full Time Machine backup, wipe the original drive, check it for errors and restore from the new backup?

Thx for the prompt response! The challenge is the computer will not boot up at all. The problem started when I went to update the OS. The update would download and start, and then fail about halfway through. So, I decided to do a recovery load and that’s when I fell into this pit of despair. Now when I power up it’s caught in a doom loop and can’t launch from the internal drive.

And, before I wipe it, I want to copy all of the apps I have loaded. So, I’m now trying to download MacOS onto an external drive to boot from temporarily. Then, I’ll copy over the apps, flush the drive, and try a clean install. I don’t have another Thunderbolt Mac to use for Target Disk file exchange.

Thoughts?

 

[DBW_Chicago]

Thx for the prompt response! The challenge is the computer will not boot up at all. The problem started when I went to update the OS. The update would download and start, and then fail about halfway through. So, I decided to do a recovery load and that’s when I fell into this pit of despair. Now when I power up it’s caught in a doom loop and can’t launch from the internal drive.

And, before I wipe it, I want to copy all of the apps I have loaded. So, I’m now trying to download MacOS onto an external drive to boot from temporarily. Then, I’ll copy over the apps, flush the drive, and try a clean install. I don’t have another Thunderbolt Mac to use for Target Disk file exchange.

Thoughts?

Just wanted to close the loop - the problem was a corrupted index in one of the volumes - erasing and reinstalling did the trick - but because I did not have another Mac to do the Target Drive with I lost a lot of data that I failed to have in iCloud

darkpaw - thanks again for your posts and help - it saved me from going to get it serviced and being told I need a new SSD - cheers mate!