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

I tried today to boot my iMac Pro from an USB stick with High Sierra. I have exactly the same problem as chrisgavr asked all the time for a software update than my iMac Pro powers down and if I try again to boot from the USB stick, I'm forced to perform a software update.

Fortunately I don't have all the Finder problems...

Update on "Success"...

After reinstalling my widgets to Dashboard I received the notice that Dashboard freezed. After that my trackpad wasn't working and my iMac powered off. Does that mean I was exactly at that point where my trouble started? No! The crypto_val errors are still gone and after deleting all widgets from Dashboard, my iMac Pro is running fine.

I hope this will become a stable status.

Nevering wrote:

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.

Just a couple remarks. First, I have none of the problems you mentioned.

Now, you should not be running an anti-virus program on any Mac. An anti-virus app that is using all cores is in a runaway state, isn't compatible, and would certainly cause overheating. Stop using it and uninstall.

Regarding temperature: Up to yesterday I was thinking there aren't any fans inside my iMac Pro or they're very very silent. I never was able to hear them, even when rendering 4k movies with iMovie (this let the fans of my old iMac making noise after some few seconds). But yesterday I noticed the fans pretty loud. Funny what my iMac Pro was doing: Nothing! It was in sleep mode but with the internal screen saver running.
Does this screen saver need more performance than iMovie? I can't believe...

I just opened another thread on my iMac here: Re: my iMac Pro issuesRe: my iMac Pro issues

Hi all,
if you'll look into the other thread, I've mentioned above, you'll learn (as me) why booting from an USB stick failed. 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...

How do you get the update? I don't see anything in AppStore. The High Sierra version on my iMac Pro is 17D2102. That shouldn't prevent it from booting a USB stick though, no? With SecureBoot turned off that is.

I believe 17D2102 is the version after the supplemental update. Before one gets version 17D2047. I'm stuck on that version, and the supplemental update refuses to install.

Perhaps it is the pesky crypo_val errors that prevent this?

Possible. I'm getting Error 43 left and right with Finder. On a replacement iMac Pro right now. All in all this one behaves better than the first but this is still pretty bad. "It doesn't just work!"

CleefMon wrote:

After the update, the version is now 10.13.3 (17D2104).

That's pretty wild! I see another one too! In my 5 Macs in my office, I only see today's new Supplemental Update on my iMac Pro. Glad to see that it is an updated version number as I did install that update on my iMac Pro at least 4 times last week before it appeared to stick! I think all but one of my Macs took more than one try to get it to not show the update still available.

I'm off to give this one a try and see how it works out.

Hi

I also have this crypto_val issue (a lot, see below), and I got the -43/blank folders issue once. The -43 disappeared after a reboot but the crypto val remains.

I'm thinking about doing a reinstall, but I'm not sure how far I can trust the TM backup. I mean if the issue is on the disk, will the TM restore bring back the problems ?

As this problem looks common, can some Apple engineer work on the issue and help us for real ? Or is that going to be another Apple cryptic lack of transparency ?

For the record I'm running the latest os (build xxxx2104)

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 24.

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 24.

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 24.

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 24.

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 24.

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 24.

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 24.

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 8 of 24.

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 9 of 24.

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 10 of 24.

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 11 of 24.

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 12 of 24.

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 13 of 24.

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 14 of 24.

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 15 of 24.

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 16 of 24.

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

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

Checking snapshot 17 of 24.

Checking snapshot 18 of 24.

Checking snapshot 19 of 24.

Checking snapshot 20 of 24.

Checking snapshot 21 of 24.

Checking snapshot 22 of 24.

Checking snapshot 23 of 24.

Checking snapshot 24 of 24.

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.

L’opération a été effectuée.

Yes but then there’s read write issues on the SSD after running first aid (error 43), requiring force quit and relaunch of the finder to resolve or reload. This should not be happening. Further, people have reported long-term issues of the same without running first aid so while there’s a workaround it can get highly annoying and should not be happening to this high end line of computers.

I have always had problems with files disappearing and not showing up again until a restart. This happens on the internal SSD and on external drives and usb sticks. It's really obnoxious that these problems are happening on a $12K computer, and the only option Apple has is to send you another defective one.

@th10gt .. Widgets not deleted in full wipe of system ? I have the same concerns that Kadorito has below regarding copying the problems in the backup ? Can you update us on whether problem has returned or not ?

thanks

@Nevering: I've installed them when I've setup my new iMac Pro from scratch. Sometimes it freezes (as reported). After deleting all widgets from the dashboard - but still NOT deactivating dashboard - this problem is gone...

@ag_316: Not a surprise when the replacement was mastered at the same production line with the same faulty master. I'm guessing that the probability of a device being ok is quite low.

I have the same crypto_val warning with Disk Utility's First Aid. I don't have the vanishing files/folder bug on my machine though but sometimes Quick Look (on video files mainly) is freezing for up to a minute.

Seems to me all bad software issues which are hopefully soon fixed. I will try to avoid a reinstall since the only issue is only the Disk Utility warning. I'm afraid I will get bitten by the folder vanishing bug as well when I reinstall...

Keeping my fingers crossed.