VMware Cloud Community
tom2828
Contributor
Contributor

"Hardware RNG raw data failed health check" installation error

Does anybody know how to troubleshoot the "Hardware RNG raw data failed health check" installation error?

VMware vSphere Hypervisor 6.7 U3 only.

The VMware vSphere Hypervisor 6.7 U2 installs OK.

My system is based on the AMD Ryzen 9 3900X.

Thanks,

Toma

Clipboard01.png

0 Kudos
7 Replies
asajm
Expert
Expert

Hi tom2828

It's not compatible

VMware Compatibility Guide - System Search

If you think your queries have been answered
Marking this response as "Solution " or "Kudo"
ASAJM
0 Kudos
tom2828
Contributor
Contributor

Thank you for answering the question. I understand the compatibility list, but this looks more like an installation bug that was introduced in the U3 version of the software. It works ok in the U2 version, so it is not a core incompatibility. Ryzen 9 are a new and very successful class of processors and I would expect to be supported at least in the future. Is there a place to file a bug report?

0 Kudos
asajm
Expert
Expert

Can you change the installation media?

If you think your queries have been answered
Marking this response as "Solution " or "Kudo"
ASAJM
0 Kudos
tom2828
Contributor
Contributor

I used a bootable USB device and the command line through SSH:

esxcli software vib install -d /vmfs/volumes/datastore1/updates/update-from-esxi6.7-6.7_update03.zip

The same result!

Using the command line, the installation looks successful but I get the same error at startup.

After a reboot the system is reverted back to the U2 version.

I could try to use a different device. What do you suggest?

Thanks,

Toma

0 Kudos
asajm
Expert
Expert

Yes, try a different device.

Are you sure you downloaded the update correctly?

If you think your queries have been answered
Marking this response as "Solution " or "Kudo"
ASAJM
0 Kudos
tom2828
Contributor
Contributor

I looks  correct: update-from-esxi6.7-6.7_update03.zip

Is there a way to officially report a bug to VMWare?

0 Kudos
Thomas40
Contributor
Contributor

Updating the BIOS may work

0 Kudos