I downloaded the new software update macOS Monterey 12.0.1 on my MacBook Air yesterday and today I got a notification saying ‘volume hash mismatch’ for context the rest of the notification said
‘hash mismatch detected on volume disk1s5
macOS should be reinstalled on this volume’
I’m quite confused as what to do next and if this is going to cause a problem on my Mac
MacBook Air
Guys i am just coming over here from another discussion about this problem and also encountered this problem on my 2019 macbook pro 16" laptop. Went to genius bar did all fresh installs for weeks, had same problems of fresh installs not going through until i finally got lucky with a Big Sur install finishing. A week later still the same error. I finally found a developer thread in my developers forums that was discussing the same problem and one of the guys was suggesting to not run the apple diagnostics, but the standard memtest86. It is a command line tool, but there is a OSX compiled easy GUI version, called "Rember", that you can freely download here: http://www.kelleycomputing.net/Rember/
Please run this test and i am 99% sure it will show up with a memory error. So did mine and so did a bunch of others who ran the test. Unfortunately my laptop is out of warranty, so I would have to do a motherboard swap and pay the 680 bucks for that, which makes no economical sense. But the i realized, that this is somewhat weird??? How come that all these 2019 macbooks have this problem and all apparently upon upgrading either to the beta version of Monterey (which is the issue that came up in the developer forums) or upon upgrading to the release version of Monterey (if you are a regular customer). There has to be some sort of low level firmware that has to have triggered something within our machines, since it seems to only happen upon upgrading to Monterey.
BTW, my posts have been taken down from Apple, since i apparently violate the communities User Agreement, so now the above post is listed without my theory of why this might happen, this way it might help someone and not get pulled from apple.
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:
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 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.
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
That’s a bummer.
Since you have run memtest86 and you’ve done the complete system format and OS install it must be a hardware failure outside of memory.
Possibly the logic board has got some thing wrong with it. Have you done any customizations to this laptop or is it a stock factory device?
Other than reverting to Big Sur which seems to be less sensitive to hardware problems, you may need a new computer.
jdp: Thanks for the update. Sorry to hear this continued to be a problem for you. I agree, 2019 isn’t exactly “older” yet. Both my macs are 2018.
I think perhaps five years is starting to get in the older side of things. But this is mostly because of the massive hardware capability increases Apple Silicon has been delivering on Mac and before that on iOS devices.
IIRC, you have a 2019 MBP, is that right.
Would you please post the full hardware spec so there’s a record here?
Also, if I have that right, the 2019 MBP does support user upgradeable memory. Would you please confirm if you’re using the RAM that came with the system, or if you’re using an upgrade which brand / config?
Even if it passed memtest, it would be good to know this stuff.
Finally, would you mind marking your calendar to come back in 30-45 days to report on stability under Big Sur?
Just to update:
Currently running Big Sur 11.6.5
MacBook Pro (16-inch, 2019)
2.3 GHz 8-Core Intel Core i9
16 GB 2667 MHz DDR4
Intel UHD Graphics 630 1536 MB
It does not have user-upgradeable memory, so everything is as it came from Apple.
It has been 2 weeks since reverting back to Big Sur. Overall it seems fine. No Volume Hash Mismatch warnings. Disk Utility is clean. I think Safari may have crashed once a week ago or so but nothing really beyond that.
Fingers crossed it keeps up.
I’m seeing this too on my 2019 MacBook Pro. Never had a problem with this computer until Monterey.
I had this happen too. It took me two tries and a very long time - most of a day - to install Monterey, and now I have to reinstall it?? Urghhhh.....
Having same issue. Initially had trouble installing 12.0.1, and now getting this hash error. I'm on a 2019 MacBook Pro.
I have an iMac from 2016 with Monterey 12.01 and got the message „hash mismatch on volume…“
How can I fix it?
Thanks
Volume Hash Mismatch. Hash mismatch detected on volume disk1s5. macOS should be reinstalled on this volume.
What does this mean?
Hi
in my case only appears the message and the system continues working but unstable
the problem appears random
I just got another Volume Hash Mismatch error. Problem persists. So far the only application impacted is Mail. It has crashed twice and had to reindex email upon restart.
What do I do with this?
Volume Hash Mismatch?
