Heartbeat issues, persistent errors in logs... possibly related crash

[seanmcg182]

Hello all, been having a few errors. Unsure how long they've been going on.

Had an #PF Exception 14 Error Today, and while examining logs, I found this segment repeating hundreds, if not thousands of times...

Unsure if this error is even related... if it is, at least I have a cause... if it's not, I dont know what else would have cause my PSOD

NOTE: Even after rebooting the server, this error has already come into the logs a few times within 10 minutes....

cpu2:1048742)WARNING: HBX: 2669: Failed to cleanup VMFS heartbeat on volume60c922ea-525563c5-3814-001b213b04e0: Failure

cpu2:1048742)Vol3: 4248: Error closing the volume: Failure. Eviction fails.

cpu3:1051661)HBX: 6548: 'LOCKER-60c922ea-525563c5-3814-001b213b04e0': HB at offset 3145728 - Marking HB:

cpu3:1051661) [HB state abcdef02 offset 3145728 gen 37003 stampUS 95122067625 uuid 60d3c723-e7f5e6f0-5730-001b213b04e0 jrnl <FB 0> drv 24.82 lockImpl 1 ip 192.168.1.XXX]

cpu3:1051661)HBX: 6552: HB at 3145728 on vol 'LOCKER-60c922ea-525563c5-3814-001b213b04e0' replayHostHB: 0 replayHostHBgen: 0 replayHostUUID: (00000000-00000000-0000-000000000000).

cpu3:1051661)HBX: 6667: 'LOCKER-60c922ea-525563c5-3814-001b213b04e0': HB at offset 3145728 - Marked HB:

cpu3:1051661) [HB state abcdef01 offset 3145728 gen 37004 stampUS 751856881 uuid 00000000-00000000-0000-000000000000 jrnl <FB 0> drv 24.82 lockImpl 1 ip 192.168.1.XXX]

cpu3:1051661)HBX: 4720: 1 stale HB slot(s) owned by me have been garbage collected on vol 'LOCKER-60c922ea-525563c5-3814-001b213b04e0'

cpu1:1048742)HBX: 2595: Mismatch between in-memory and on-disk HB at offset: 0x301000 on vol '60c922ea-525563c5-3814-001b213b04e0'.

cpu1:1048742)HBX: 2596: 'LOCKER-60c922ea-525563c5-3814-001b213b04e0': HB at offset 3149824 - In-memory version:

cpu1:1048742) [HB state abcdef02 offset 3149824 gen 1 stampUS 751857372 uuid 60df71e2-17594e6d-2e7d-001b213b04e0 jrnl <FB 0> drv 24.82 lockImpl 1 ip 192.168.1.XXX]

cpu1:1048742)HBX: 2597: 'LOCKER-60c922ea-525563c5-3814-001b213b04e0': HB at offset 3149824 - On-disk version:

cpu1:1048742) [HB state abcdef01 offset 3149824 gen 0 stampUS 0 uuid 00000000-00000000-0000-000000000000 jrnl <FB 0> drv 0.0]

cpu1:1048742)HBX: 2600: 'LOCKER-60c922ea-525563c5-3814-001b213b04e0': HB slot (offset: 0x301000) was freed/reacquired by another host on vol '60c922ea-525563c5-3814-001b213b04e0'.

cpu1:1048742)WARNING: FS3: 608: VMFS volume LOCKER-60c922ea-525563c5-3814-001b213b04e0/60c922ea-525563c5-3814-001b213b04e0 on mpx.vmhba32:C0:T0:L0:7 has been detected corrupted

For Reference, My system has ESXI 7.0 U2 installed on an External USB Flash Drive for booting.

The ScratchConfig.ConfiguredScratchLocation setting is using '/vmfs/volumes/605f8471-24a81839-53df-7085c2f92b57/.locker' which is located on an internal NVME SSD.

The Syslog.global.logDir setting is using '[VMStore] Logs'... [VMStore] is the datastore located on the NVME SSD listed above.

The VMkernel.Boot.disableACSCheck setting is set to true.

These are the only settings I have changed.

Motherboard is an AsRock B450M Pro4, with a Ryzen 2700X. I have an Intel NIC Card in a PCI slot, and an LSI SAS Card for my NAS.

I don't know where Volume/Locker 60c922ea-525563c5-3814-001b213b04e0 even is.

Any Help would be appreciated