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

iMacPro, Mac OS 10.13.2


Diskutil gives this warning when running "first aid": warning: crypto_val: object (oid 0x4): invalid state.major_version (0)


Strange that brand new computer gives warnings, should I be worried about this?


This is whole message list:

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.

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.

iMac Pro, macOS High Sierra (10.13.2)

Posted on Jan 4, 2018 11:55 AM

Reply
Question marked as Top-ranking reply

Posted on Jan 31, 2018 7:31 AM

Just an update for anyone who may be helped by my experience.


About 10 days ago I decided to take the extreme measure of erasing the hard drive and reinstalling the OS after trying the other steps suggested including disabling FileVault and installing the OS in recovery mode.


Phase 1: Started iMac Pro in Safe Mode and erased hard drive using Disk Utility. I then did a fresh install of macOS High Sierra. I ran Disk Utility First Aid on the fresh install and all three crypto_val warnings were gone and Disk Utility reported the disk was fine.


Phase 2: Enabled FileVault. Then I ran First Aid and Disk Utility reported the disk was fine with no sign of the crypto_val warnings.


Phase 3: I again booted the iMac Pro in Safe Mode, erased the hard drive and did a full system restore from Time Machine. I then ran Disk Utility First Aid on the fresh Time Machine install and all three crypto_val warnings were gone and Disk Utility reported the disk was fine.


Phase 4: Enabled FileVault again. Then I ran First Aid and Disk Utility reported the disk was fine with no crypto_val warnings.


Phase 5: Partitioned hard drive and installed Windows 10 Home via Bootcamp Assistant. Then booted back to macOS and ran First Aid and Disk Utility which reported the disk was fine, still no crypto_val warnings.


Of note however, ever since the fresh installs if I run Disk Utility First Aid I always have to force relaunch Finder because all my folders / files disappear particularly on my external hard drives and Dropbox. However, force relaunch brings them back... so there seems to be some bugginess remaining although the machine seems to be running fine with no other issues as of now.

129 replies

May 10, 2018 4:46 PM in response to Nevering

UPDATE: Further to my earlier post, I've again backed up to Time Machine, and have now gone through an SSD erase and OSX reinstall from Internet Recovery (rather than using the OS stored in the recovery partition). Then used Migrate Assistant to restore user accounts, apps, settings etc.


Crypto_val errors aren't present as before, but I still have the problem of screen brightness resetting, and external HD spinning up over and over again while in sleep mode (therefore worried about the effects on a hard drive that's effectively always on/off/on/off/on/off etc etc).


Going to leave it to sleep overnight, and see whether the sleep crashes occur.


Seriously thinking about getting this refunded, and speccing out a standard 5K 27" iMac with best available graphics card and SSD (effectively what I use at work, with none of the issues we're all seeing on the so-called 'Pro').


Cheers Apple.

Feb 19, 2018 2:32 AM in response to Peter Lemon

Need to do some update on this matter: After my previous message and a couple of restarts my iMac Pro froze totally. It just didn't start anymore with or without safe mode or any other procedure. When using Disk Utility I noticed my main partition, where the MacOS is installed was using a new filesystem and it was crypted. None of the tips at web support helped me so I contacted Apple Care.


With the support person we tried the same procedures I did already and after that he told me as a last option I should format my main drive, reinstall the MacOS and migrate all my data manually - so I did. I chose to use unencrypted filesystem.


A few days ago they called me from Apple to ask some questions and get a log file so they can investigate the problem. After all this it didn't come clear to me what the problem was. It may have been the cryption and formation of the drive, a bad data migration from my previous iMac or a bad device or driver when doing my first installation or something else.


Never the less after the reinstallation and manual data migration my iMac Pro is now working like a charm! And there is no Crypto_val error anymore.

Mar 1, 2018 2:45 PM in response to th10gt

th10gt wrote:


iMac Pros are running a different version of High Sierra. That's NOT a joke. Apple just published a dedicated combo update for the iMac Pro only...

This is a common occurrence for new Mac hardware when it is as different from "normal" Macs as this iMac Pro is from what came before it. It takes several point updates for the old and new hardware to converge on one installer, it'll likely be 10.13.4 or 10.13.5 before we get just one. Until then iMac Pro will have a different version number and its own Combo Installer and Supplemental Updates. This happened with the Mac Pro (late 2013), and numerous of my new MacBook Pro hardware updates through the years.


Until that convergence, there is no High Sierra installer you can download from which to create a USB stick installer that will boot the iMac Pro. I am looking forward to it as I create a USB bootable installer with every new point update so that I may run Disk Utility, and/or install a fresh OS if things are not working well.


If your USB stick has a clone made from the currently running OS on the iMac Pro, it should boot just fine if your settings allow external drive booting. I believe that'd be the only external macOS drive you could boot from at this time.

Mar 4, 2018 6:19 AM in response to th10gt

My hours of testing this stuff showed I can make a clone, but I’m not able to boot the iMac Pro from the clone- the Pro reported to me that it requires an APFS volume to boot. I gave up at 4am before I was able to get one to work. I have had other first versions of Apple computers/OS that would not work with previously available software. Third part disk repair type apps almost always put up warnings that they are not yet updated when a new macOS comes out, this Pro is not only new hardware but has High Sierra that uses this new APFS.


Regarding clones, MicroMat's TechTool Pro 9.6 includes Protogo, eDrive, and Volume Cloning- three different types of cloning options. In years past I used Protogo to make emergency booting thumb drives, it was great when I configured it to contain all my 3rd party drive repair apps. Protogo appears to reformat the Volume to HFS+ when creating its special clone and the iMac Pro would not boot from it. It is possible that I could have formatted the thumb drive to APFS and gotten it to work, but after hours of experimenting, I went to bed instead. Again, I would expect them to update these functions in future releases.


I use Bombich Software's Carbon Copy Cloner for backup clones on all my Macs. Though I’ve not actually cloned and booted from a CCC backup from the iMac Pro (I focused my testing on the Protogo yesterday), I have done this hundreds of times with dozens of Macs over the last 15 years. I would expect that if CCC does not work yet with the appropriate options for the iMac Pro, it will eventually work when APFS is fully documented for developers (lack of adequate documentation is one of the challenges Bombich has reported with updating CCC to APFS in High Sierra) and the iMac Pro installers converge with the rest of the Mac line.


Bottom line: there are ways of cloning now, but this new computer has special requirements that have not yet been met for booting from it.

Jan 10, 2018 3:39 PM in response to spertti

Same issue here. A few additional symptoms:

  • Downloaded DMG are available in Disk Utility yet not found in the Finder.
  • It seems some downloadable files are not found in the download folder
  • a few kernel panics today as well with straight reboot
  • Tons of folders just disappeared from DropBox as well (were there yesterday).
  • Disk util did not fix it


Maybe I should have completed a user migration my user info?

Will try a Recovery and see if that works-full reinstall if needed.... 😟


update: ended up booting to recovery and running disk util-my dropbox folders have reappeared and the DMGs are now seen again and can be mounted...but the warning still appears when running disk util after reboot and during the recovery/first aid-may try to run Drive Genius or Onyx....


I guess it was temporary relief-some files are still returning an error -43 when trying to open, and newer downloads are not appearing in the Finder...

Feb 23, 2018 2:21 PM in response to AngelaLinCA

I'm having a problem also. It seems to be common on the IMac Pro. Apple says that is a known. Hopefully decide to fix it sooner than later.


Additional problems on the IMac Pro. 18 core 128 mb 2Tb drive 16Gb video


1) letting IMac Pro go to sleep for the night and rebooting. Opening a folder and all the files do not show up. Opening external drive, files don't show.. Reboot, files show up


2) Wired mouse becomes inactive is not used for about 10 minutes, have to unplug and re-plug to get cursor to move. Even though mouse light is still on.


3) Temperature ... Appears that Apple opted for silence over efficient cooling on the IMac Pro. It will often get to 90 C before it seems to want to cool itself with doing very little. For example a just running an anti-virus app that uses all cores will take it up to 90 C very fast. Anything over 60 C is of concern to me. Apple should be giving us an option to adjust fan cooling curves .... and it's not even summer yet.

Mar 30, 2018 3:45 AM in response to arnask

I’m guessing crypto Val errors has something to do with FireVault, so you may want to turn that off to stop the lag etc. if already on. This solved the lag for me. Then, you should do the reinstall. After reinstall, the system seems to work other than error 43 messages after running disk utility, which relaunching finder should fix. Not a perfect solution but seems to be working better than the factory install.

Mar 30, 2018 8:33 AM in response to ag_316

For what’s its worth,


I turned off file vault. Erased disk. Clean install. Crypto gone but ~43 errors after disk utility. Relaunching finder would be a work around then,


I just updated OS re new release out today, no more errors after running disk utility.


I’m afraid to turn on fire vault again though.


Will test the machine and let people know there’s other errors popping up, but it seems to be a good sign.

May 2, 2018 10:13 AM in response to Kadorito

For me, the wipe/restore eliminated all the crypto errors.


My remaining iMac Pro issue is with system sounds sometimes repeating once per second. I have traced that back to Xcode's iOS Simulator running on my iMac Pro, and have submitted a report via Apple's Bug Reporting website. Apple's team has already responded to my report, so they are clearly taking iMac Pro issues seriously.

May 11, 2018 8:30 AM in response to lienffur

Finder problem...


As you'll see inside this thread, I had also the crypto_val errors and a lot of problems. All are solved and my iMac Pro is running well. But to day I discovered the first time the "empty folder error". The situation was a little bit "unusual", because I had Firefox, Cyberduck, 1 Excel file and 8 Word documents open at the same time. After closing all apps, Finder was showing the files again. I did neither a restart of Finder nor a reboot, just closing all the apps...


Maybe that might help others.


Greetings from Germany!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.