Jump to content
1699 posts in this topic

Recommended Posts

5 minutes ago, SavageAUS said:


Have you tried running first aid?


Sent from my iPhone using Tapatalk

I have tried all the method i have to do.

Such as:

 

First aid in RecoveryHD

Low-level format the disk to “00” then reinstall the monterey

add/delete some kexts or efi drives

 

But with all this method it also show  Volume Hash Mismatch.

And when show Volume Hash Mismatch in notification the system will freeze and cant to use.

  • Sad 1
34 minutes ago, gujiangjiang said:

I have tried all the method i have to do.

Such as:

 

First aid in RecoveryHD

Low-level format the disk to “00” then reinstall the monterey

add/delete some kexts or efi drives

 

But with all this method it also show  Volume Hash Mismatch.

And when show Volume Hash Mismatch in notification the system will freeze and cant to use.

Try "diskutil repairDisk diskX" in Recovery.

18 hours ago, gujiangjiang said:

After the update to Monterey

I've started to get this "Volume Hash Mismatch"

I think I remember that @Slice posted something about this a few days ago but I can't find it.  Maybe I am wrong.

  • Thanks 1
18 hours ago, gujiangjiang said:

After the update to Monterey

I've started to get this "Volume Hash Mismatch" in my notification center

 

0fa4dbfb-d8f2-43c3-888d-feda6bcebeb8.png.74d9b9eae0674eb47ef27152300aa180.png

 

https://developer.apple.com/forums/thread/684276

 

https://developer.apple.com/forums/thread/105397

  • Like 2
3 hours ago, Derty said:

I still dont get how to solve this.

Does this is the bug of APFS file system?

3 hours ago, gujiangjiang said:

I still dont get how to solve this.

Does this is the bug of APFS file system?

As you use ApfsDriverLoader.efi then any possible bug will be corrected by apple with next software update.

But I doubt there is a bug.

May be your drive is not macOS compatible? Or controller.

11 hours ago, gujiangjiang said:

I use this driver but still show “Volume Hash Mismatch"

15551635085943__pic.thumb.jpg.3296ce25242f77d059cba7914afaf6f3.jpg

Try to remove ApfsDriversLoader.efi , HashServiceFix.efi, AppleUiSupport.efi then use this drivers

AppleAPFS.efi.zip

Edited by chris1111
  • Like 3
28 minutes ago, saCULar said:

Updated to 21A559.  Boot to graphical login average of 2 min 50 secs, compared to 43 secs for Big Sur. 😞

 

 

It is first time. When caches will be formed and spotlight finished indexing the boot will be much faster. Just wait.

  • Like 5

Doing a simple search in App Store for "macOS Monterey" magically worked! 😉

(Joking of course, it has been the same last year, and year before that.)

 

Downloading now, hope the Mac(s) do not go up in flames after it installs... 😁 Running Beta 10 on both currently, was never offered RC1 or RC2.

Note: Of course, I first left the Developer Beta, which I do not need to be a part of anymore now that non-Beta, RTM release is out. :) 

Edited by Naki

RC2 build 21A559 is identical to what Apple released today as the final Monterey iteration, so what now??

On my two GA-Z490 Vision G builds, bluetooth is not working after wake from sleep and the i225-V onboard NIC is only working when it wants to, but then for only short periods of time. I think considering this dilemma, it now boils down to solving these issues the "hacking" way, and forget about Apple. This is however beyond my capability, therefore I stick with Big Sur for the time being in the hope that some wizzkit will produce a solution in the near future to also make Monterey "golden" on the GA-Z490 Vision G architectures.

 

Greetings Henties

 

Goodbye Monterey until you become usable on my particular hardware.

Edited by Henties
  • Sad 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...