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

Mar 22, 2018 7:22 PM in response to chrisgavr

Steve Jobs would be rolling over in his grave. I agreed to return mine and place a new order. I will let you know if the new Mac has the same problems (which Is expected based on this thread). My guess is SSD issue. Apple support useless; claims to never have heard this issue and does not want to even read this thread, I probably will return the 2nd one if it has same problem (as it’s less stable then my late 2014 high end iMac and not that much faster for single core activity) and wait for 2nd generation. If you are within 14 day return window you may want to do the same. I think it would otherwise drive me nuts.

Mar 26, 2018 9:20 PM in response to Nevering

@Kadorito: If you have setup your iMac Pro with a clean install in the past, you can perform a Time Maschine backup, booting from the recovery partition (other short cut as usual, it works with the one for reset of the NVRAM: cmd + alt + P + R), delete the old partition, create a new one, install High Sierra (from the recovery partition) and restore from Time Machine.


@Nevering: Due to the fact that a lot of iMac Pros have this problem but not all, I still guess it's due to a faulty image at (at least) one of the production lines when putting the image onto the hard disk. Because the partition is faulty (which might cause the disappearing files inside Finder (fortunately I never had that problem) I don't think, Apple will be able to sort this problem out by a software update.


Since I've did, what I just wrote at the beginning and deleted all widgets from my dashboard (but still have dashboard enabled), my iMac Pro is running well.


Greetings from Germany!

Mar 30, 2018 12:50 AM in response to arnask

My machine also died yesterday. Everything was extremely laggy and had intermittent freezing. Impossible to work with. Had this issue with my old iMac once and needed to reinstall. Took me all day yesterday to get macOS installed freshly on that machine. Never had that many issues setting up a mac. Internet restore didn't work with wireless but you don't see an error message or anything. It just doesn't do anything. Switching to LAN worked immediately but took a long time. Now all is freshly installed - even 10.13.4 is on it but guess what: Migration Assistent doesn't work. Restore from Time Capsule: MA just hangs after selection. MA from a cloned hard drive: scans content, starts migration but then aborts because of "unexpected problems". The experience so far has been horrible. I guess I have to start over again and I'm not really happy about that...

Mar 30, 2018 10:15 AM in response to th10gt

My 10.13.4 install by the Combo installer went well. I did get info on screen before the install that the screen would turn off for a few minutes while continuing the installation.


Overall the install went quickly (though not as quickly as I had hoped ::grin:: ) and the machine now shows the same build as the rest of my computers updated to latest macOS, as I had expected with 10.13.4 when 10.13.3 did not.


I am curious about the need for File Vault on the iMac Pro as the T1 chip already encrypts the SSD, if I understood it correctly. I either turned it off or never turned it on when I got the computer in January.


I've had great experience with my iMac Pro after wiping and reinstalling the OS. I had that one moment of not showing my files, but they were displayed as soon as I relaunched Finder or rebooted (I don't remember which one I did) and I have not had that issue again.

Mar 31, 2018 11:20 PM in response to Nevering

@Nevering: With my iMac Pro a full clean and format of the main partition and after that installing High Sierra from the backup partition worked well. Prior to that I've made a full back up with Time Maschine and restored all data back after having installed all applications manually.


Since that time my iMac Pro is working fine but (as written several times here), I've deleted all widgets from the dashboard and also switched off dashboard.


Yesterday I've installed 10.13.4. During installation the iMac Pro powered off and didn't came up again. After pressing the button everything worked. Got the same "problem" with my two MacBookAir. So don't worry, it seems to be a feature, not a bug!

Apr 13, 2018 12:09 PM in response to Kadorito

New iMac Pro (base model) this week - built in December from what I can tell - which has the three crypto errors.


For those of you who have 'solved' this by erasing the SSD and performing a fresh install, I just wanted to check if you've seen it resolve the other common errors people with new iMac Pros seem to be having?


- Kernel Panic shutdowns during sleep mode

- Thunderbolt-linked HDs continually powering up while the iMac sleeps (ie wake signals or similar being sent from the thunderbolt ports)

- Screen brightness resetting to near-max after reboots (rather than returning to user-set preference), despite 'automatically adjust' being switched off.


Wondering if all of these things are symptoms of the same initial production line build mirroring of a dodgy OSX?


Can anyone confirm if all of the above vanish after a wipe/reinstall? If not, my new toy isn't reliable on any front, and will be going back until Apple get themselves a robust set up.

May 10, 2018 10:23 AM in response to 1Ronin

... except that I have both Power Nap and Time Machine turned off (don't even have my Time Machine drive plugged in at present - just general file storage).


No reason for the iMac Pro to be accessing my external drive during sleep. It was doing it right from the beginning on this iMac Pro ... I got it to stop, even before the re-install of OSX, but not sure exactly what I did to stop it. All the power saving settings which would allow for hard drive access were switched off, and I had done several PRAM and SMC resets; one of these must have changed something?


So my chain of events so far is this:


1. Got me a new iMac Pro; found the following problems:

a. Multiple daily crashes, but only during sleep (resulting in the Kernel Panic / Bridge error messages)

b. Screen brightness resetting to 90% of max with every reboot

c. External LaCie hard drive constantly spinning up during sleep (in actual fact, sleep the iMac, LaCie takes 20 seconds to spin off, light goes off for 5 seconds, then comes on again and spins for 20 seconds, before powering off, repeat ad infinitum - ie not good for the life of the LaCie)

d. Using diagnostics during the reboot process revealed the 3 Cryto_Val errors (but not seen when running Disk Utility from within the OS itself).


2. Following forum advice, I switched off FileVault and Power Nap/Wake on Network Access. Subsequently, the Kernel Panic crashes 'a' stopped happening during sleep (but still had b, c and d).


3. Tried a few PRAM and SMC resets to try to solve the screen brightness issue 'b'; at some point, 'c' stopped happening, and the LaCie went to sleep at the same time as the iMac Pro was in sleep. Didn't notice the specific thing I did to cause this; just noticed the disc had stopping running in sleep the whole time. The resets did not solve 'b' or 'd'.


4. Decided to perform the OSC re-install; made a full Time Machine Backup, booted into Recovery, erased the SSD, reinstalled OSX from Recovery, reinstalled my Apps & Settings from Time Machine (about 3 hours of work). Immediately checked the SDD via boot diagnostics - no more Crypto_Val (d) errors. Also did a few full reboots, and found the display brightness issue 'b' was gone (ie the screen brightness, with auto-adjust switched OFF, would stay where I'd set it, at 50%. However, issue 'c' was back ...


5. Last couple of days, and issue 'c' is still happening, and now issue 'b' has returned too. But no sign of crashing (yet) or Crypto_Val.


At the moment, I'm frustrated and completely puzzled that all my issues a,b,c and d have stopped happening at one point or another, but N none of them at the same time!!


One thing I have realised, is that when I reinstalled OSX, I think it was done from the installer which lives in the recovery partition (ie not the same installer than would be used in Internet Recovery). Given that Crypto_Val disappeared, I thought that all was okay, but this isn't the case. I may have one more attempt at a full restore, but via Internet Recovery this time (ie so that I get a full new installer, rather than the master copy in the recovery partition).


I'll need about 3 hours free to nurse the iMac through this process; I remain unconvinced it'll work, but feel the need to try it, just to have tried every possible option.

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.