Volume Hash Mismatch?

Yeah, I have tried basically everything that you have tried, including wipe and reinstall without data. Still got the same message. I am basically certain it's hardware related, though the Genius Bar ran all sorts of hardware tests and none failed. I ultimately traded the problematic laptop in and got a new one. Restored with same data, using same OS version, and never had the issue again.

I am having this same issue with my 27inch iMac. In my case I have erased and reinstalled the OS three times with the latest version and have added no additional apps or backup info. I've run diagnostics with no hardware issues found. Still getting this error message and a kernel panic error. Mostly happens in sleep mode but recently has randomly restarted while using Safari. Currently working with Apple support and now awaiting feedback from captured data submissions.

I started getting this error this morning on my 2018 Mac mini. (It had unexpectedly restarted over night) This machine has been stable as a rock for years.

The change from me has been that I’ve unplugged my black magic eGPU without waiting for it to fully disconnect.

I’ve had to do this because I have a new work laptop and I have to switch back-and-forth once a day.

Apple does not provide for a way to cleanly move between two machines.

Now I’m here and I have to say this thread makes me very concerned about my machine.

I gave up on my 2019 MacBook Pro (it was a company-issued laptop). Not sure if the standard package of crap that IT installs messed something up, but it began kernel panicking several times a week, and when I tried to reinstall macOS from recovery mode it failed.

So I turned it in and they gave me a 13'' M1 MBP to replace it. This thing is just crazy fast and this isn't even the M1 Pro/Max. Hopefully no more Volume Hash Mismatches....

This continues to be an issue for me even after reinstalling Monterey. Is there actually a fix for this issue? It seems to be a larger problem:

https://osxdaily.com/2021/11/10/volume-hash-mismatch-error-in-macos-monterey/#:~:text=%E2%80%9CVolume%20Hash%20Mismatch%20%E2%80%93%20Hash%20mismatch,which%20the%20error%20constantly%20reappears.

I have not had a chance to update this thread, but I now strongly believe that this is a hardware failure.

If you’re willing to create a memtest86 USB boot drive, and do the boot configuration change needed to use it under Monterey, I bet you find out that your MacBook Pro is throwing errors.

this is what happened when I swapped ram sticks twice. It was a lot of extra work to run a memory test tool but validated what a few people have said here and elsewhere about this mismatch issue.

It also triggered an RMA request to Crucial for me.

I now believe that Monterey is much more sensitive to hardware issues in memory than Big Sur.

Update: Within a couple of hours after my previous post, the VHM error reappeared. I figured I'd done everything but a complete wipe of the SSD and a clean reinstall (via online recovery), so that was the next step. Made a Time Machine backup, did the wipe and reinstall, migrated everything back onto the fresh OS, and - knock wood - so far so good.

I may try the deeper dive of using memtest86, but right now I've already spent a ton of time on this.

Since my last post, I did reinstall the OS (when I had access to fast internet). That seemed to help for a while but then the error came back. Over time, the apps I use most (Safari, Mail, Messages, etc) began becoming more unstable and would crash. Safari became pretty much unusable.

I backed up everything and Erased All Content and Settings this past weekend. I have not reinstalled the OS again (as I don't currently have access to fast internet and satellite can't even allow the normal software update to download properly). For a few days, it was all good. Then yesterday I got the error again and Mail randomly crashed. So 1 error and 1 crash so far. I was hoping wiping it all would help. At least it made it more usable for the time being.

Please let me know if the wipe + reinstall does the trick. I am getting to a point where my MacBook Pro is essentially a brick.

I know it’s a lot of time, cause I went through it.

if you find some time, you need a 512mb+ usb that can be erased, one reboot to change the boot settings then the memtest86 should would likely be throwing errors within 5 minutes.

Otherwise, please consider a reminder to post again here in 30-90 days with status.

I ran memtest yesterday on my computer and it actually passed without any errors. I ran all 13 tests with 4 passes.

I still feel like there is an issue with the OS and this specific hardware which causes the VHM error and corruption on the disk.

jdp107, thank you very much for taking the time to complete that test. I know it was extra steps so thanks for taking that time. Hopefully it was interesting in some way.

I'm planning to write this issue up in a blog entry, and will incorporate this feedback. For me, it absolutely was corrupted memory that was detected by memtest86. It is good to know that it can appear and not be related to memory issues detectable by memtest86.

From learning this, my suggestion to people encountering the volume hash mismatch in monterey for the first time to first run memtest86. If it has failures, that's a replace it problem.

If it passes memtest86 as it did for jdp107, then the person should try the pram/nvram reset that seems to have worked (so far) for jdp107. This is part of the instructions Apple has in support for this issue.

jdp107, would you mind sharing your specific HW config and what (if any) specific event triggered the error?

Again, FWIW. So far, a week after I completely wiped the SSD, downloaded Monterey from Apple, and imported all data, apps, etc. from a backup, I've had zero "volume hash mismatch" error messages. I am cautiously optimistic that the clean reinstall has done the trick.

(NOTE: I also changed the APFS partition(s) of the drive. Before, I had created 3 volumes, for different storage reasons. I had, unwittingly, also created the 3 as fixed partitions as opposed to flexible APFS volumes. Force of habit from the old days. When I wiped the SSD clean, I created only one APFS volume. Everything on the other two previous volumes was simply data, and I figured I could as easily put all that into folders on the one volume, instead of having 3 separate volumes. I have no idea if that had any effect on the volume hash errors.)

I also just got a copy of MemTest 86 and have been running it. So far, 2 passes and zero errors. I will let it go overnight to do justice to the advice everyone gives about "how many passes" - again, I am cautiously optimistic it will give me no errors.

Thank you for the update! I’m glad to hear that this can work for some people. A lot of the postings are from people who have tried this or something similar and failed.

Your experience validates this as a step suggested by Apple.

Though, it is a lot less trouble to perform a memtest86 before starting from nothing.

What I mean to say is if someone encounters a volume hash mismatch, they are should test for a memory issue first because no reformatting / clean install will fix that.

I’m curious if we’ll see new reports of VHM errors on late versions of Monterey on macs with otherwise healthy hardware.

Here the same problem

MacBookPro 16 Monterey 12.3.1

Try everything :

Reset Pram / NVRam

Reset SMC

Delete all partitions and erase disk

Reinstall all without any recover data

The problem persists

Getting really bored

When did the problem first appear?

Was there a crash prior to seeing the error or did it seem to start showing out of the blue?

My guess is you need to replace the RAM on the machine.

You can find out for sure by making a memtest86 USB boot drive, and running the test. I had a ton of errors, replaced the ram and it fixed it.

Please run memtest86 and report results.