Volume Hash Mismatch?

Hi amna2k1,

We understand that you're seeing an error message after installing macOS Monterey. In this case, let's try reinstalling macOS using these instructions: How to reinstall macOS - Apple Support

Take care.

FWIW, YMMV - Macbook Pro 16-inch 2019, running Monterey 12.3. Just yesterday got the "volume hash mismatch" message, with the instruction to reinstall the OS. Tried looking for answers (here and elsewhere) and discovered lots of suggestions, no solid answers. Tried reinstalling the OS via recovery (CMD-R on startup) and halfway through that process got another error message "an error occurred loading the update." Tried again, same error. Called Apple, spent time with the tech, tried Disk Utility First Aid, then tried (3rd time) to reinstall via internet recovery (OPT-CMD-R), same error message halfway through. Finally tried another suggestion to reset PRAM/NVRAM and CSM and *that* appears - for now - to have made the "volume hash mismatch" alert go away.

My takeaway from all this, as a Mac user since 1984, is a very mixed emotion. The tech is getting more and more amazing in what it can do, at the same time it's getting more and more fragile and prey to the tiniest glitches. It's not reassuring.

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.

I am also experiencing this issue. Attempted to reinstall MacOS Monterey 12.1, the issue persists. It’s causing apps to crash, webpages to reload, system restarts, black screens, etc. Hope this issue gets addressed soon, as I need my computer for school.

Edit: I’m experiencing this issue on my new 14” M1 Pro MacBook Pro.

Hi amna2k1,

It looks like you ran into a security mechanism intended to protect you and your Mac. If you started up in macOS Recovery (gray background), I think the error was caused by a misconfigured Secure Boot policy (also known as the LocalPolicy).

Try these steps to reinstall macOS and rewrite the Secure Boot policy:

1. Shut down your MacBook Air.
2. Press and hold the power button (Touch ID) until you see the message "Loading startup options".
3. Select Options and click Continue.
4. If you're prompted for an administrator password, enter it to continue.
5. Select Install (or Reinstall) macOS, then follow the onscreen instructions to reinstall macOS.

If you run into a startup disk dialog that includes the Target Disk Mode option, go to the top of the screen and select Startup Disk -> Quit.

This is seriously concerning, I know I’m going to lose my OS at this point.

I want to try and perform a disk backup beforehand. What’s the best way to get a machine in this state stable enough to pull data, even manually copying directories?

Right now, after the login screen, the OS starts to load then shows this notification. About 20 seconds later there is a whoosh sound that I’ve never heard from the Mac before, and it crashes to cold boot.

The only pause in this loop is at the login screen.

btw, the OS is updated as of yesterday, 12.2.1

Hello amna2k1,

Thanks for following up.

We recommend restarting you Mac and trying to reinstall one more time. If you get the same message and the start up disk does not appear, then you'd want to reach out to Apple Support for further assistance.

Get Support

All the best!

I had the same problem on a Late 2015 iMac, that unfortunately has had problems anyway. But, the new OS IMHO triggered this new issue. I dunno. Maybe it found an underlying issue that has been lurking. I had done a full wipe of the HD when this problem first arrived with 12.1. Then brought in data from TimeMachine. Issue surfaced again.

Yesterday, I downloaded 12.1 from the Apple App. Store, and just did an OS re-install. I've only had about an hour in front of the iMac, and so far no re-surfacing of this issue.

Seems like I'm not the only one that had this problem, so I don't know if I can blame my oldie but goodie iMac.

As a last ditch effort I did an erase and clean install, but I still got the hash error again. Days later my computer froze and I attempted to restart it and it’s completely bricked now. Won’t go past Apple logo. Can’t access local or web recovery. Can’t boot from a startup disk. I think I must have had a hardware failure.

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 recently had this problem about a month after I checked about this MAC, it recommended a software upgrade I upgraded to Monterey 12.1, which was the second upgrade? The upgrade went thru some extra steps it seemed but after that the 27" Inch Imac with solid state drive and 128 GB memory seemed to work OK for about a month. A few days ago I got the random Hash alert, and whent to applecare. They recommended shut down, wait about a minute and start up using command -R. When it booted I was advised to go to disk repair and select the drives and run the disk repair on both of the items. Then shut down and restarted. That was four days ago and I havn't noticed anything yet. The alert has not come back yet. I do not let it go into the sleep mode as the SS drive has no moving parts. I found it to be much less problematic to just shut the screen saver off, and do a restart once a week or so. The apple tech said that if the alert came back again to run the disk utily from the command R boot mode (not from desktop dock preferences), back up everything, shut off power, and then reinstall the OS again with out wiping the drive. I assume the next thing would be to totally erase the drive and reinstall from Time Machine. They said the problem could have been in th startup items on some of the solid state drives, and are working on a fix?

I have encountered the same problem on my Mac Mini (2018) following Monterey 12.1 install. The machine has restarted spontaneously twice in the last few hours. The following are the beginnings of the diagnostic screen. Full details available on request from Apple Support. Then I got the ‘hash mismatch detected on volume disk1s5

macOS should be reinstalled on this volume’ message.

panic(cpu 8 caller
0xffffff8009db6ce9): Possible memory corruption:
pmap_pv_remove(0xffffff9568f56f00,0x10f45d000,0xf7944f, 0x8000000f7944f004,
0xffffffe101e9bbc4, 0xfffffe9e2bc552e8): null pv_list, priors: 1
@pmap_internal.h:903

Panicked task 0xffffff870b6156d0:
1 threads: pid 1212: mdworker_shared

Backtrace (CPU 8), panicked
thread: 0xffffff9a342b8aa0, Frame : Return Address

and

panic(cpu 0 caller
0xffffff8008e3ebf1):
IOSCSIPeripheralDeviceType00::setPowerState(0xffffff8bcea716c0 :
0xffffff800b22de0a, 3 -> 2) timed out after 102100 ms @IOServicePM.cpp:5524

Panicked task 0xffffff909aa33670:
229 threads: pid 0: kernel_task

Backtrace (CPU 0), panicked thread:
0xffffff8bcca14000, 

Here's what I ended up having to do (minus all the dead ends along the way). I backed up my drive, (in my case using Carbon Copy Cloner). I then used Internet Recovery to wipe the drive and install a clean copy of the OS.

Then I used Migration Assistant to restore my files, but when choosing what to restore I unchecked 'System & Network'.

That seems to have fixed it. Previously when I had restored everything, including System & Network, the volume hash mismatch message was there as soon as I logged in. It's been a week now and the message hasn't come back.

Well… that wasn’t it after all. It took a while but the message is back. Genius Bar recommended I wipe and reinstall without restoring any of my data just to narrow down whether it’s something in my user account… which I guess is my next step.

if that doesn’t work it must be hardware, right?