Volume Hash Mismatch

Hi,

I've installed Monterey Beta 1 .... and then did an OTA update to MR B2.

After the update to MR B2 ... I've started to get this "Volume Hash Mismatch" in my notification center ...

I've tried to reboot into Recovery, and do a "First Aid" an all volumes in my MacBook Air's ssd ...

But this message still re-appears.

Any idea why this happens? or a fix?

cheers, Daniel.

hmm

I even did a total re-install of macOS Monterey Beta 2 (erased the SSD and a fresh install).

And yet again, this "Volume Hash Mismatch" is persistent

Hmm

So, I did:

fsck_apfs /dev/rdisk1s5

From Recovery .... on all Volumes and the disk itself.

Back in macOS MR B2 ... Still getting this annoying notification hmm

same... now just waiting for another quick update from apple.

Same

I just started getting this today. The system is also unstable, I've been getting random Kernal Panics.

Update: I tried Beta 3 ... and now running Beta 4 .... on my MBA ... and I'm still getting them.

I have to say, it's gotten a bit worse ... since Finder and other vital "vital mac apps" crash and they won't re-spawn. And I end up with no apps running (read: showing). Funny when you just have the WindowServer app running and everything else has crashed, and didn't re-spawn.

Luckily pressing the PowerButton does pop up the "shutdown window" ... and I can restart my MBA from it (and not force...)

BTW: ... something I noticed is I was getting the error when using / having Safari open ... so I'm going to test using Firefox instead .... and try extra not to start any other "Apple apps" (just 3rd party apps) and see ...

I got the volume hash mismatch but it is not my volume where I downloaded macOS Monterey

Having this issue too, though without the popup and on Big Sur. I've discovered that a sudo purge works as a quick fix, though it ends up coming back. You can run it over SSH too if you can't open Terminal anymore. Hope there's a real solution for this soon.

Ok turns out my issue was caused by failing RAM, replacing it solved my issue (I have a MacBook Pro that has user-upgradable RAM). Probably not related to the issues in Monterey.

Is anyone still getting this issue with 12.1? I often get the notification and also experience a very unstable system with various app crashes. This did not go away with a completely fresh install (erase disk).

For what is worth I’m getting this issue on a 2019 16’’, another 2019 13’’ I own is running fine.

My MacBook (early 2015) has OS Monterey 12.01 with the same problem.

I am facing this same issue with my 2021 16 inch MacBook Pro with M1 Pro chip. Earlier when I bought this laptop it was working just fine with Monterey 12.0 but when I updated to Monterey 12.1 I started seeing this "Volume Hash Mismatch" notification. Also, all of my regular use applications like Docker, PyCharm, VSCode, Slack, Chrome & Python are now crashing every 10 mins. I contacted apple support & was told to reinstall the MacOs Monterey using bootable USB. I did that & it didn't work. Then I was told to reinstall MacOs via internet recovery mode. I did that too but it didn't solve the problem. I was also asked to upload the screenshots of issues so that it can be escalated to their engineering team. Never ever heard back from the engineering team.

Then I was told to visit iVenus store(Apple authorised service provider) which is in Kothrud, Pune, Maharashtra, India. I submitted my laptop there and after a day I got it back with the freshly installed MacOS Monterey 12.1. The issue still persisted. I visited the iVenus store again the next day with those same issues. I was told to install application from App Store only as the third party application like Docker, Pycharm, Slack, Chrome, VSCode & Python are not yet supported by the Apple Silicon. I went to the website of these applications and pointed out the statement which says "Stable release for Apple Silicon".

I was denied to provide any further services by the iVenus store as their support team concluded that it is a problem of the application and it has to do nothing with the machine.

This morning I contacted Apple Support again and I was told to wait for another day so that they could escalate this issue to engineering team.

I will be receiving the next call tomorrow at 11:30 in the morning. I pretty sure "incapable apple" wouldn't be able to solve my issues.

I invested in a ****** product and yet the support team tends to congratulate me for using premium Apple product every time I got on a call with them.

Here are some of the screenshot I took recently -

Same problem in 12.2 beta2. It often appears when using safari , then Mac will freeze . I think Apple didn't notice this problem 😔

Incompetent & Incapable Apple here are few more screenshots -

BTW Apple support has denied the repair, replacement or repair of my machine.

To the most asshole company of all time -

Here is another issue while reinstalling the MacOS Monterey.

What a losers -

I had the same issue with a 2017 iMac 27. At first I was not able to do a clean install of Monterey. Got the same error as above "An error occurred loading the update". Tried everything. Splitting up fusion drive, installing only on blade ssd, only on hd rebuilt Fusion again. Finally I tried taking out one of the ram sticks. No change. Tried replacing the one left in with the first one I took out, and then I finally managed to install Monterey. Installed Office and some other apps. Everything worked fine. Tried installing the possibly faulty RAM, and then the error "Volume Hash Mismatch" appeared. Took out the RAM, and the error never came up again.

Accepted Answer

[Update 2022-01-29]

macOS 12.2 seems to have a solution for this problem. I've done a complete clean re-install (with re-formating the entire drive).

I've run a 24hr Blackmagic Disk Speed Test, Safari open (the app that most usually made it trigger this issue). Without the issue.

Could more people try 12.2 too? and see if it solved their issue?

Hi, for me message started after I installed macOS 12.2

But I think that main problem was that after updating Monterey I installed Big Sur on external drive (my friend needed it). It was immediately after update so don't know will it happened without Big Sur.

First message was showing regularly, every few hours. Then I remember to choose Monterey disk as startup disk again and message disappeared for almost a day. It showed only once. After that i ran Blackmagic disk speed test and it showed 5% slower speed then before. Normal restart made speed normal again (an no more message so far).

Didn't try clean re-install but will do it if message continues to pop-up

Still same problem in 12.2.1

I've been with this issue for a few months now. I've also downgraded to BigSur which now has other issues (notably multiple kernel panics per day: https://developer.apple.com/forums/thread/678644 and app crashes). Earlier in this thread people reported that this issue was due to a faulty RAM module, which I didn't believe initially. After I run a memtest86 test I'm now convinced that indeed I also have faulty RAM. In my case I have no option than a motherboard replacement as the RAM is soldered.

So imo the error reported here is a symptom, and different versions of macOS show different symptoms (BigSur v Monterey). But the cause is most probably something hardware related, thus I'd recommend for everyone having this issue running a memtest86 test to check if this is the cause of their problem.

Am experiencing this issue on a MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports). Applications crashing regularly. Did a clean install of MacOS Montery incl. re-formatting the disk about half year ago. Also NVRAM reset. Issue disappeared for a month or two but returned (though less crashes than initially till now). Currently running 12.2.1. My Windows machine at the office is more stable :-(

I've now faced this issue on two of the 6 total Macs on my household. Neither with any recognizable patterns I could depict to properly find a reason as to why it happens. On my MBP11,5 it crashes the whole UI, and is unable to start again On my iMac14,1 it just shows the notification, however, the OS randomly starts to increasingly become unstable, like Safari being unusable until a restart. The best conclusion thus far has been to perform an SMC/PRAM reset on my Macbook (where it'd frequent itself like 6 or 9 times a day sometimes, all requiring a reboot), and on my iMac it happened a few minutes as I write this, so no conclusive workaround or solution has been necessary for now.

My MacBook has FV2 enabled, but my iMac does not. Both are running 12.3.1, both are running on an SSD (Apple SSD on the iMac, Crucial P2 on my Macbook, which has otherwise worked flawlessly for a while).

On my MacBook It has shown itself since I first installed Monterey, on 12.2 IIRC, and on my iMac it has just appeared now on 12.3.1. I'm sure It's not related (in both of my cases) to RAM, as both have healthy/working RAM, and all temps and usage are low at some points where I have observed the issue.

Re-installs do not help, as I have unfortunately discovered on my MacBook (With a Time Machine backup), nor a full disk-wide wipe of the SSD (Apple SSD on the iMac was previously completely erased off all of its contents).

I look forward on seeing if Apple is able to resolve this frustrating issue, as downgrading is not really an option for me, and the time loss inflicted by having to save projects and restart because I have my UI crash on me or the OS fall apart ain't fun.

I'm starting to hate Apple. I can't even work now, the emulator often crashes and shows "Volume Hash Mismatch", Monterey stops responding from time to time and restarts automatically frequently. I even wiped the hard drive and reinstalled Monterey , but the problem remains the same. I had to upgrade to Monterey because I had to develop with a new version of Xcode, but the stupid new Xcode need the stupid Monterey!!! I hate Apple, why is this still a serious problem on 12.3.1?!

I am running the latest Monterey 12.4, the problem started after I did a standard update within Monterey. I too encounter the same problem as discussed above.

I have done a memory test using memtest86.com free download to create an USB to test the memory of the computer as there were so many pointers to this.

Here is the result:

Basically test was aborted due to too many errors.

What to do now?????????

Volume Hash Mismatch
 
 
Q