This looks like a lazy admin error - did you even try to register the VM in the new location ???
Please try to sum up your problem - without useing more obscure screenshots.
Example: the VMFS-volume with the friendlyname "datastore3" - using the physicaldisk /dev/disks/t10.*******:1 can no longer be mounted via the webinterface.
Did you try
or a resignature ?
I am using esxi (6.7). There were both esxi and datastore on the current disk. ESXi boots normally but I cannot see my virtual machine. Then when I look at the problem, the system cannot see the datastore at all. When I review various blogs, a name that starts with "naa" is always mentioned. But I can't see it at all.
vmkfstools -V output.
I can't resignature because I can't see vmdks in datastore
Please stop using this obscure filehoster - not going to try it one more time !!!! 😡😠
> I can't resignature because I can't see vmdks in datastore.
That is completely unrelated ... so check if datastore is detected as a snapshot and when yes - resignature it.
Read about "resignature a datastore" in the knowledgebase.
If you dump the first 3 gb of partition 3 I can check wether there are still VMs that survived.
The next 30000 lines would be interesting ...
By the way - when I ask for a 3GB file dump then I really mean it ....