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
Question marked as Top-ranking reply

Jan 31, 2018 7:31 AM in response to spertti

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.

Jan 5, 2018 10:45 AM in response to spertti

iMacPro, Mac OS 10.13.2


I received my first IMac Pro in December and found the 3 crypto_val warnings. I was only able to clear this by erasing the hard drive and reinstalling the OS. On the same computer, I also has finder issues. When creating a new folder, i would get an error code -43). Ultimately Apple issued a return.


Jump forward to today 010518, the new iMac Pro arrived. I ran Disk Utility and the 3 crypto_val warnings are on this unit as well. I will be again, erasing the drive and reinstalling the OS to try and resolve.

Feb 21, 2018 8:44 PM in response to th10gt

Success!!!
Due to the fact I wasn't able to boot my iMacPro from an USB stick, I've booted from a recovery partion (by pressing OPTION+COMMAND+P+R (wich usually should reset NVRAM, but on an iMac Pro...). I'm wondering why my internal hard disk was split to 4 volumes, but I didn't care about. I've deleted the volume (partition) Macintosh HD and installed a clean High Sierra.


After that I restored all data from my Time Machine backup. (You should have a full Time Machine backup of your Macintosh HD!) Launching First Aid on Macintosh HD all crypto_val errors are gone. I've checked for updates in App Store and there was again a supplementary 10.13.3 update. It took roughly 20 minutes (and 4 reboots) to install. The crypto_val errors are still gone.


I need to rearrange all my apps in Launchpad and now I'm nosy to discover if all problems are gone. My feeling was, I had some with Dashboard and especially with the widget Screenshot Plus. Next step will be to reinstall all widgets.


If I'll run in trouble again, I'll report here. If not, this post will be the last one on this topic.


Good luck to all of you fighting with crypro_val errors!

Feb 1, 2018 8:11 PM in response to acantril

Okay...here is an update.

Since my last post, I did the following:

1. Ran the Apple HardWare Test/Diagnostics (as per this link) and no errors were reported and everything was in good shape 🙂

2. Booted into recovery mode and ran Disk Utility there... Disk Utility went thru the 17 snapshots and showed this same error (3 times) with each snapshot BUT ended with a report that the main volume was OK !!

3. Called Apple Support and described this in detail to them and they told me that this error was really nothing to worry about.


I am happy to ignore it for now because I am not having any other issues going on and I CERTAINLY don't want to wipe and reinstall everything. I will keep you posted with any other updates!!

Feb 19, 2018 6:26 PM in response to spertti

In case this helps someone else... I was also able to get the crypto_val warning to vanish by: booting into recovery mode (cmd-R at startup); running Disk Utility from there; erasing the startup SSD; re-installing High Sierra (from recovery mode); then restoring my data from a Time Machine backup. After all this completed I: booted back to recovery mode; ran Disk Utility; then repaired the startup SSD; and there were no more crypto_val warnings.

May 1, 2018 9:32 PM in response to Nevering

Ken, I wrote about that already several times, but, maybe, not inside this thread: I guess the problem is caused by a faulty master, when they prepared the SSD at their factories. That would explain, why a lot of devices are impacted but not all (a different manufacturing line with a good master).


If that's true, I can't believe that any patch will overcome the problem. I've corrected the crypto val errors by wiping and reinstall and the problem never came up again.


My other problems were caused by the widget "iStat Pro" (iStat Pro für Mac - Download) which is very close to the hardware. After deleting it (wasn't such easy) all is running fine. Fortunately I never had the problem with "missing files in Finder".


Greetings from Germany - Olaf

May 6, 2018 3:52 PM in response to Nevering

I'm with you on doing the reinstall. But after I turned off most of the things that seemed to trigger it, power nap. wake with net access, etc. It still did it although less frequently. But I got tired of it nonetheless, so I bit the bullet and did it this morning. Surprisingly enough it was a non-event. Made sure my time machine backup was current and away I went. I did a full erase, reinstalled MacOS and then did a migration from time machine. Three hours later, everything was done. No more messages and no errors when I run disk utility. I just wanted the peace of mind knowing that it really was just a software error and not a hardware issue on my brand new iMac Pro. Good Hunting!

May 7, 2018 6:22 AM in response to lienffur

Okay - replying to my old comment now; here's what I've found:


iMac Pro base model 3.2Ghz 8 core 32GB RAM, Radeon Pro Vega 56, less than a month since purchase


Original issues:

Screen brightness resetting after every hard reboot (I would manually adjust to 50%, but it would reset to almost full brightness - 2 bars from max - with each full reboot).


In the first week, several crashes during sleep. Would either put the machine to sleep manually, or leave it running (so it put itself to sleep); would return the following morning, or in some cases, after only 30 minutes, to find it awaiting login after a full restart, complete with a Kernel Panic error message. This appeared to stop after disabling 'power nap' in the energy saving settings, although other users have had crashes occur (albeit less frequently) after doing the same.


Running diagnostics (holding 'D' after a reboot) turned up the three 'crypto_val' errors mentioned in this thread.


I was uncertain whether any of the above were inter-related ...


Action taken:

Following @1Ronin's earlier message, I decided to bite the bullet, and made a Time Machine backup using a 2TB WD Elements USB 3 hard drive I had going spare.


I then booted into Recovery mode (Command + R) and used Disk Utility to erase and reformat the SSD, then returned to the Recovery menu.


I then performed a clean install of OSX High Sierra (less than 30 minutes), and returned to the Recovery menu (ie without booting into the OS).


I then selected the option of restoring settings (apps, user accounts etc) from Time Machine (effectively reinstalling everything other than the OS from the Time Machine disk, as you would via Migration Assistant) - took maybe 90 minutes max (including Logic Pro, the bulk of the Adobe Creative Cloud suite etc).


Results so far:

First thing I checked was the boot diagnostics (holding 'D' after restart) - no crypto_val error reported. Result!


Second thing I checked was screen brightness; this is no longer resetting after a reboot. Result!


Third thing I checked - OSX version is 10.13.4 (curious here, as I haven't gone to the App Store yet to reapply OSX updates. Pretty sure a couple of patches had been applied since the 'out of the box' state, so these appear to have been added during the Time Machine restoration). I was on 10.13.4 before I began the process this morning, and the above bugs were present.


Can't be 100% certain that the Kernel Panic crashes won't occur again, but will be re-enabling 'power nap' to see what happens here. I'll post an update.


At this point, I remain hopeful that everything works as intended. It does seem to give credence to the idea that a batch of new iMac Pros were cloned from a bad image, and the reinstall of the OS is the fix. Might also explain why Apple hasn't acted more quickly in issuing their own fix? Perhaps the number of affected machines is in the minority - maybe not even affecting their own hardware?

Jun 1, 2018 11:04 AM in response to spertti

Hi,


I have no idea if anyone will find this useful. I had the same problem. I tried everything short of re installing MacOs. I tried one last thing. I removed most of my data from the Mac, it was stored in Dropbox. I restarted the Mac and then checked FileVault again, it told me that is was encrypting and would take 11 hours to complete. Up to that point it had claimed that it was already complete. Any way I waited for the encryption to complete and now my drive is error free. It now gives me to option to remove encryption which was previously greyed out. Can't explain this but it worked.

Feb 20, 2018 6:32 AM in response to CleefMon

Having the same issue and did what you did with Recovery Mode, killing Mac HD, then creating new Volume and reinstalling MacOS. Fixed the crypto_val errors, however the Finder errors (missing files, folders looking like paper sheets, error 43) all remained.


So I tried making a macOS flash drive, every time I attempt to run it, the computer tells me i need a software update to use that Startup disk. Secure Boot is off, and I run that update, no dice. So instead...


In the process of doing an Internet Recovery and I’m going to wipe SSD clean, start a new Container/Volume altogether and see if that helps.


It’s nice to know I’m not the only one having issues with the new iMac Pro, but this *****. By the way my NEW iMac Pro was dented right out of the box too - so either way this thing is going back, but I’m trying to troubleshoot abuse solutions on this unit before attempting to get a new one. If a new, new iMac Pro reports the same problems I think I’mma have to hang up the towel on this one and skip this gen. Shame - that space gray is stunning.

May 7, 2018 7:07 AM in response to Kadorito

Yes and If is is the same issue that everyone is talking about on this stream you do not want to restore at this point from Time machine. From macOS Utlities, instead of doing a restore from Time Machine Backup which most likely will not cure the problem, you want to go to the disk utilities menu and erase your HD. Then once that is done you will quit disk utilities and that that will take you to the screen to reinstall macOS. Once that is done you get a setup assistant screen that asks you if you want to transfer files from another Mac or Time machine. This is where you migrate the files from Time Machine back on to you Mac. If you go to Apple.com and type in "How to reinstall macOS" in the support drop down, a really nice tutorial comes up. Good luck.

Apr 15, 2018 9:15 AM in response to spertti

I just got off chat about this same situation - My new iMac pro is about a month old - this was his response: "Good news all around, the alert is not related to any hardware based issue with the Mac, and it is being investigated this was updated as early as 4/13/18 so the matter is now known to the engineering team"

Soooo...it seems like they are working on a patch/solution to this. The tech said that Apple would most likely email those of us with this reported issue when there is a fix. So, hopefully this is soon - I really don't want to wipe and reinstall, and for the price of this unit, it should not be having any of these warnings.

May 9, 2018 4:40 PM in response to 1Ronin

Yesterday I bit the bullet and did the wipe, install, and Time Machine transfer. Things went well and the crypt... is gone for now. I had sound, network, files disappearing, and screen issues. Time will determine whether this has fixed the problems. I have never had Kernel Panic, knock on wood.


Very disappointed in Apple not taking this seriously.. Even after their senior support staff promised to followup and help, they did not return calls, even after several uploads of diagnostics to them.


I wanted to clarify something that about the Time Machine reinstall that was not clear, and Apple senior support couldn't help with either ??


The Time Machine file transfer comes in while you are rebooting the new system. It will ask you if you want to do a file transfer from another Mac or Time Machine. This is where you select Time Machine and the items to include/exclude. I included all. Started off saying about 8 hours to restore, however quickly went down to about 30 minutes for a 1.2 Tb backup.

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.