Jump to content

Silent Knight reports EFI version found 1968.100.16.0.1; expected 2020.80.5.0.0


7 posts in this topic

Recommended Posts

thx @pico joe... I am using clover 5157 and updated through config.plist/smbios to latest efi version ..., I've had restart problems and am checking all possibilities...we will see how it goes

Link to comment
Share on other sites

Posted (edited)

also, if I may, after sonoma install my hibernatemode changed from 0 to 3 ...same machine running monterey, hibernatemode 0. I am assuming 0 is the correct setting?

 

...got through 1 restart with updated efi version, fingers crossed

 

Edited by RobertX
Link to comment
Share on other sites

Posted (edited)

...when sonoma won't boot, I start monterey and run disk utility first aid on the ssd holding sonoma, this is the result

 

Running First Aid on “Sonoma - Data” (disk3s1)

Checking file system and repairing if necessary and if possible.
Volume was successfully unmounted.
Performing fsck_apfs -y -x /dev/rdisk3s1
Checking the container superblock.
Checking the checkpoint with transaction ID 164541.
warning: container has been mounted by APFS version 2236.101.1, which is newer than 1934.141.2.700.2
warning: disabling overallocation repairs by default; use -o to override
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking the encryption key structures.
Checking volume /dev/rdisk3s1.
Checking the APFS volume superblock.
The volume Sonoma - Data was formatted by diskmanageme (1934.141.2.700.2) and last modified by apfs_kext (1934.141.2.700.2).
warning: apfs superblock at index 0: apfs_doc_id_index_flags has unrecognized flags (0x10)
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the document ID tree.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
Verifying allocated space.
The volume /dev/rdisk3s1 appears to be OK.
File system check exit code is 0.
Restoring the original state found as mounted.

Operation successful.

 

 

...warning: apfs superblock at index 0:  apfs_doc_id_index_flags has unrecognized flags {0x10}

 

after this I can boot to sonoma again but restart is still an issue

Edited by RobertX
Link to comment
Share on other sites

Posted (edited)
Spoiler

1. Mac sleep mode

Putting a Mac into sleep mode leaves its RAM powered on, which allows the Mac to wake up and get back to work very quickly.

Normally, a Mac automatically goes to sleep after a certain period of inactivity (between one minute and three hours).

This energy-saving mode is used by default for desktop Macs and is called hibernatemode 0.

 

3. Mac safe sleep mode

Unlike the simple sleep mode above, this mode is safe because it copies the RAM contents to the startup drive before your Mac goes to sleep, like in hibernation mode. This allows you to recover your data in case of battery failure, hardware damage, or any other unfortunate events that can affect your Mac.

However, in this mode, the RAM remains powered on while your Mac is sleeping, unlike hibernation mode. And that’s why the wake-up process is still as quick as in the standard sleep mode.

Safe sleep is also called hibernatemode 3 and is set up for portable Macs released after 2005 by default. However, not all laptops support this mode.

an explanation of terms of sleep from https://mackeeper.com/blog/mac-sleep-modes-explained/

 

...I believe I could have just rebooted from the monterey drive, and not ran disk utility at all(older version checking newer install}...then restarted from sonoma ssd, but I haven't had any issues restarting after changing hibernatemode  3  to hibernatemode 0 ...still sleeps and wakes, and restarts...just trying to get ready for the next update

Edited by RobertX
Link to comment
Share on other sites

 Share

×
×
  • Create New...