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.
Thank you for the follow up. Helpful to know the RAM is factory. Hope it stays stable for you.
Can an OS update bring on hardware failure. To be fair, I know my Late 2015 has been diagnosed with the need for a full on motherboard replacement for $700.00 prior to the most recent OS update issues that some here are having. Frankly, I'm not sure if my Apple Authorized repair guys really ever found the issue, and the motherboard replacement recommendation was just not a "Hail Mary" ;).So, I guess I'm not really in a position to complain.
But, it seems interesting that others, with a varying number of different Macs are seeing this crop up. Is 12.1 "smarter" and has better diagnostics than previous versions? Or is this another OS upgrade bug?
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.
Volume Hash Mismatch?
