So have I. Which is why this was so troubling.
What seemed to work was upgrading to 6.5 and reattaching the old VM. The drive was there and I'm able to get at the files. I am now moving the data off and plan on starting over completely from scratch. Given this weirdness I don't trust that drive, not to mention I can't seem to find the flat file in the Datastore any longer. Next time I'll create smaller VMDKs that I can offload from the host if I need to do this sort of thing again.
This whole thing is just really weird. This is not my first time messing with ESXi and I've never had these sorts of problems.
When I added it to the new VM. Basically what would happen is I'd attach the drive and a message would pop up and say I can't create a new drive that is larger than my available free space. And the area where I could change the size of the disk is grayed out so I couldn't shrink it if I wanted to (which I wouldn't want to).
On 6.0.0u2 I could only ever create a VM version 6, nothing higher. Consequently, I never had the option to attach a USB device (which begs the question why there are USB controllers). Unlike on 6.5 where the USB Device entry in the add device menu was grayed out, it was completely absent.
On 6.5 everything works fine. I can create version 13 VMs all day. It was just 6.0 that had problems.
It's good to hear your experience with the zwave.me controller. I might go that way if it proves that the S2 won't work even after reverting to the legacy USB drivers.
Thanks a ton for all your help. I've got my files back so the major crisis is averted. Now it is just a matter of time to build everything back up again. I should be back in business and then some by this weekend.