I can recommend you to upgrade to the latest version of ESXi 6.7 (Build 15160138 released in 12/05/2019). sometimes these kinds of strange problems will be solved by upgrading to the latest version.
Please share if your problem was gone
Hope this could be helpful
Thanks for the suggestion.
I thought the problem might be that I'd "re-used" the VMDK file from one 6TB drive to another that didn't have exactly the same geometry, but no; I deleted the old vmdk file, rebooted the machine, and created a new vmdk file using vmkfstools -z. I'm still getting the same problem: when a WIndows VM accesses a drive through the ESXi vmdk, it appears corrupt, but not when it access the same disk via a SAS controller using PCI passthru.
I'll try updating ESXi and seeing if that solves the problem.
OK, I've updated to Build 15160138. It hasn't made any difference.
So, to recap, the NTFS file system of this drive appears fine to Windows when it's addressing it directly through hardware, but not through an ESXi vmdk.
Win7 is end of life so I would ditch it and give win10 a go
The same problem manifests in Win 2012R2
Do you have anything to work with ? vmware.logs or something like that ?
By the way - I have seen the same. My first idea would be the USB 3.1 with Windows 7 combination.
Anyway - please provide some data then I will look into it.
The problem is when the drive is connected via the motherboards SATA controller, so I don't think the USB3.1 is an issue. Besides, that's being used via passthrough.
As it happens, I'm beginning to think the issue is with the motherboards C612 chipset, which doesn't appear to be supported by vmware (Supermicro says it's supported by ESXi 5.5U1, but I can't find any verification of this on VmWare's site)
Anyway, I installed ESXi 5.5 and had a play, and voila! no disc corruption using the motherboard's SATA controller!
But now I can't seem to passthrough the onboard SAS 3008 to Windows 2012r2. Windows hangs on boot :-p