MacBook Pro 2018 warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Make an appointment at the Apple Genius Bar for service. If you need to find an Apple Store - Find a Store - Apple. If you did not purchase it from Apple then you will need to look to the vendor for service or How to find your nearest Apple Authorized Service Provider (AASP) or Distributor (AAD).

[I posted this on another thread but believe posting it here would be more appropriate]

I purchased a MacBook Pro 2018 with touch bar, which shares the same T2 chip than the iMac Pro. After conducting a clean install and installing all my applications from scratch I ran disk utility first aid as a final check and was dismayed to discover the same "crypto_val: object" warnings listed above. When I called Apple (second tier support) I was told they were aware of the issue and "not to worry about it." Needless to say, I did worry about it even though my computer was working fine. Therefore, I bit the bullet and followed the recommendations posted by others:

1. Complete Time Machine backup to external drive

2. Restart from Mac recovery partition by pressing Common R on startup

3. Open hard disk utility/first aid and erased drive (to default format)

4. Reinstalled MacOS

5. When the computer restarts migrate (not restore) everything: all files, apps, settings, etc. from the the TM external backup drive

6. Installed the supplementary MacOS 2018 update

Fortunately once the above was completed all my files, apps, preferences, etc. were intact and running disk utility no longer showed crypto warnings. Issue resolved!

By the way, I went to the Apple store yesterday and noticed that the MacBook Pros 2018 on the shelf had the exact same crypto_val warnings (attached screenshot) that I observed before reformatting my Mac.

Therefore, I believe that these warning are UNRELATED to any of the computer problems listed by others and may be only cosmetic. However, these warnings will unnecessarily prolong the time Fist Aid checks your hard disk, especially if the disk contains time machine backup snapshots (one set of warnings for each snapshot!).

I hope that above info can be of help to others.

It is part of the new Disk Utility, the new filesystem APFS, and Time Machine. Both APFS and Time Machine can create snapshots. However, Time Machine snapshots have no meaning to Disk Utility, hence they may produce strange errors. I see the same thing where Disk Utility reports 35 snapshots and checks everyone! Takes forever and produces odd errors. But the disk is OK.

After I reformatted the drive (as I explained above) I have made multiple time machine backups and the crypto_val warnings have not reappeared.

By the way, I believe (but not sure) that the snapshots are created by time machine (TM) when you have disconnected your external backup drive for a lengthy period. And that the number of these snapshots temporarily stored in your hard disk decreases once you reconnect to the external backup drive and activate a TM backup.

Brand new MacBook Pro 2018. Same issue.

Verifying file system.

Volume could not be unmounted.

Using live mode.

Performing fsck_apfs -n -l -x /dev/rdisk1s1

Checking volume.

Checking the container superblock.

Checking the EFI jumpstart record.

Checking the space manager.

Checking the object map.

Checking the APFS volume superblock.

Checking the object map.

Checking the fsroot tree.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking the snapshot metadata tree.

Checking the extent ref tree.

Checking the snapshots.

Checking snapshot 1 of 7.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking snapshot 2 of 7.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking snapshot 3 of 7.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking snapshot 4 of 7.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking snapshot 5 of 7.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking snapshot 6 of 7.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Checking snapshot 7 of 7.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Verifying allocated space.

The volume /dev/rdisk1s1 appears to be OK.

File system check exit code is 0.

Restoring the original state found as mounted.

Operation successful.

I'm seeing the same thing on macOS High Sierra 10.13 on a MacBook Pro 2018.

warning: crypto_val: object (oid 0x4): invalid state.major_version (0)

warning: crypto_val: object (oid 0x4): invalid state.key_os_version (0x0)

warning: crypto_val: object (oid 0x4): invalid state.key_revision (0)

Kappy, if you look more closely - it appears that those error warnings are repeatedly propagating into snapshots from persistent conditions present on the startup volume. For better-or-worse, Snapshots are images.

This concern has also been reported via the Desktop Mac forum - as early as last January, and I have recently encountered it out-of-the-box, on multiple factory-fresh MacBook Pros - straight from China. Notwithstanding, when my concern re. these warnings was escalated to Apple Engineering 3 weeks ago - and 9 months after this issue 1st surfaced, the Engineering response came back within hours, as "This is an emerging issue..." Since I intend to continue using FileVault and encryption, Apple's advice to turn-off FileVault is a non-starter for me.

Even so - despite months of churn & chatter on this matter, I haven’t been able to find any definitive (aka, 'official') statement re. the possible effects on performance, stability or security when the conditions producing those crypto warnings are present.

>

This happened to me right out of the box. I don't have any other issues with my Mac, so I am not going to waste time reformatting my computer, if there is no issue. I would like to know why though. My old 2015 MBP same operating system doesn't have them. So why would a brand new computer have them. It is a little concerning when you spend $4000 on a new MBP and no one from Apple can tell us why this is happening. I never upgrade OS for at least 6 months after they come out. I let everyone else figure out all the bugs. Im way to busy for my OS to **** up all my apps.

According to recent reply from Apple Engineering - "Instruct customer to upgrade to MacOS Mojave; see if that fixes..."

Well, it did! 😀

(I booted into Recovery partition immediately after install; crypto warnings were no-longer reported by Disk Util app during repair...)

The errors seem only to appear in the snapshots which you can ignore. The disk is good. Are the snapshots from Time Machine?