@florent Thank you for the feedback. My last import attempt was with 5.93. I had been hopeful that the changes in 5.91 would make the migration work because my prior attempt was pre-5.91.
The drives mounted to that VM are 60.00GB, 1500.00GB, 1819.88GB, 1799.98GB, 1819.88GB and 1023.98GB. That's what it shows for drives sizes in Windows Disk Management. In vCenter the largest are listed as 1.78TB.
Ideally this should be the first VM I migrate. I'm still working on figuring out if XCP-ng will work for us and this migration failure, plus the eclipse in Texas has stalled the testing by a couple weeks now.
Maybe I could detach those drives in ESXi, migrate the VM, change the mac and IP then copy the data between the old and new VM with both of them running. That sounds painful and slow.
Or, probably better, I could create a new temporary VM on XCP-ng with several drive attached then sync those drives through a network share, then detach the drives and migrate the other VM, attach the drives to the migrated VM and remove that temporary VM.
The drives attached to that VM don't have 2TB of data on them, though they are quite full. Perhaps I could shrink the volume in Windows then shrink the vmdk file in ESXi. Not sure if ESXi allows that but I'll have to do some research to find out.
Also, it would be cool if a future version of XO would determine that the vmdk is too big to import so it would fail right away rather than failing after saturating my network bandwidth for 24 to 48 hours. Fortunately in my network that's not a huge deal for the users but it has meant that I've spent 4 days trying to import something that will always fail, since I've tried this import a couple times now.