That's interesting, there's no way the VM would have been up and running with no storage so either it's not on the storage you were expecting or it's still managing to get to the storage somehow!
If you can enable SSH on the host and SSH in, run the following command to list your storage devices:
esxcli storage vmfs extent list
Then grab the 'Device Name' (eg. naa.60002ac000000000000001c5000abcd5f) of the storage your VM is on and run
esxcli storage nmp device list -d <Device Name>
Where <Device Name> is the Device Name you grabbed in the first command, this will show you the working paths to the device, might give you some clues as to what's going on.
As for the script you'll need PowerCLI to run it, which means you'll need a Windows machine with connectivity to the vCenter. If you're running Windows vCenter then it'll already be installed (though you might have to add the snapin) otherwise you can download PowerCLI and install it.