ESXi 8 U2, nfs4 - Core works fine but Scale is causing issues

TrueNAS General
, , ,
62

When it happens, vCenter shows the same error as before:

“The virtual disk is either corrupted or not a supported format”

The host’s VMkernel log shows:

VmMemXfer: Evicting VM with path: /vmfs/volumes/1234/test-vm1/test-vm1.vmx
VmMemXfer: Creating crypto hash
VmMemXfer: Could not find MemXferFS region for /vmfs/volumes/1234/test-vm1/test-vm1.vmx
63

Having the same issue here. Also running 8.0.3 and so far 25.10.2, 25.10.2.1, and 25.10.3 all exhibit the same behavior. We’re running iXsystems enterprise hardware and have support, so I have a ticket in on the matter.

While the VM is powered on:
A fatal internal error occurred. See the virtual machine’s log for more details. Failed waiting for data. Error 195887107. Not found. Failed to load one or more destination disks.

While the VM is powered off:
The virtual disk is either corrupted or not a supported format.

NFS4.1 worked fine on Core, and an earlier version of SCALE…but I don’t recall what version we were on at that time. It was prior to 25.10. However, with that version NFS failovers weren’t working (at least with NFS4.1). I think that problem has been resolved, based on limited Linux client testing, but now this one popped up…

64

Had just about the same experience.

Lost track of what the previous version was ( I assume it was working fine, but cannot be really sure ).

Then I just spent the day debugging the issue, and the fix for “The virtual disk is either corrupted or not a supported format." was to change sync settings to at least standard.

sync=disable works fine for file/folder copy, cmdk copy via vmkfstools, but VM/template cloning did not work at all. Just double checked on another unit running CORE version and it is working fine with sync=disabled….

I had to recover the vCenter from backup and thought it was the restore operation’s fault, but it turned out no to tbe the case.

1 Like