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

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.

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!"

Another "macOS High Sierra 10.13.3 Supplemental Update" appeared in the App Store app's Updates tab this morning for my 18-core-- which was already running 10.13.3 (17D2102).

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

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.

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.

I also restored all data from time machine and had no longer any warnings BUT if I started first aid disk utility (without reporting any warnings) after ending the program ALWAYS some files in FInder were missing!!

Apple will replace my iMac Pro and I am waiting for the new machine. I will report if this iMac pro has the same problem!

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.

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.

I got a support discussion today about the 2 topics. The guy told me that the crypto_val was under investigation and should not to be worried about.

Regarding the -43, he was trying to get some details, as it seems more worring. But I could not provide much as it's a transient issue on my side.

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.

As I've already written inside this thread. It's from my point of view caused by mastering the hardware from a faulty macOS image. Wiping the hard disk and installing High Sierra again, the crypto_val errors will disappear

See above...

Greetings from Germany

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.