This is a companion discussion topic for the original entry at https://level1techs.com/video/synology-active-backup-free-vmware-backup-and-restore
“It works really well on AM4 these days”?
Any idea why 6.7 u3 setup is throwing a psod with an ASRock Rack X470D4U/BIOS 3.10, BMC 1.60/3700X, PBO disabled/128 GB RAM?
ASRock Rack has created the first AM4 socket server board
that bios has the buggy agesa with the bad rng generator, you will have to flash to 126.96.36.199abb which idk if it is out yet for the x470, maybe?
According to ASRock Rack’s Tech Support/Europe the public BIOS 3.10 already has AGESA 1003ABB.
They’ve sent me a new test BIOS (3.11, file dated July 29th), will test that one as soon as I have a little time.
Is there are reason that L1 isn’t reviewing ASRock Rack’s AMD home server solutions yet?
I would have thought you’d be fawning over Threadripper and AM4 boards with a full onboard KVM BMC.
no, I need to, I am unsure who to reach out to and one that I ordered on ebay never made it.
that PSOD is what you get when rdrand doesn’t return random numbers, so probably it didnt really have abb, or was incomplete.
I hope that, too and that 3.11 is fixed in that regard.
If packages by random weirdos on the interwebs aren’t a concern for you I could retail purchase all the stuff in Germany and send them over to you.
is a fresh install on the new BIOS worth a try?
I’ve flashed 3.11 twice and am actually trying to make a fresh ESXi install from an USB thumb drive that was created with VMware’s vanilla ESXi 6.7 U3 setup iso file. The PSOD appears shortly after the window changes to the yellow/grey split screen.
Don’t know what else to try
It’s still complaining about the rng. Can you try fedora 30? I’m curious if it boots or hangs on system d. That will be an indicator as to whether rng/rdrand is working.
Will give it a try this evening and report back!
I tested fedora 30 on that motherboard with the p3.10 bios and a R7-2700. Had no issues… mine is currently running proxmox 6.0 right now.
Edit - Never mind
I had similar psod till the abb update then all was good after that.
I don’t think there is anything in the rng health check that would be esxi specific so it’s probably still useful for you to try fedora 30.
is there a way to test if its really there or not? (dmidecode,lshw…etc?)
also this suggests that Ryzen is just not supported in ESXi
Yeah, I’d be happy if it just ran without VMware “supporting” it
Can anyone see with these details if it is really running 1003ABB?
Test the rdrand instruction. Fedora or newer popos do this at boot time via systemd.
how exactly? … i see the flag is there on proxmox 6.0
you’d have to boot up the free esxi installer to see if your system PSODs. I’m guessing not. to close the loop on what we’re diagnosing here?
proxmox is old debian, so it may not depend on rdrand working right to boot.
But you said you tested fedora, so I’d expect fedora not to boot if rdrand is advertised, but not functional.
Ideally you test ESXI or @aBav.Normie-Pleb tests fedora 30 to see what happens.