Hi @m4biz ,
To begin with, I would like to say that it is advised not to be running any production/critical workloads on a legacy/unsupported ESXi version.
vSphere 5.0 is long gone. Consider upgrading to a supported version.
For the issue, it could be storage/storage performance issue. Please connect via SSH and run the following commands:
1. Datastore utilization: df -h
2. Try to access the datatsore: cd /vmfs/volumes/datastorename
3. If you can access, try creating a test folder: mkdir test
Hey @m4biz,
Am I seeing well or you have two datastores with the same name? Try what @ashilkrishnan propose you of checking from inside the ESXi OS but if that does not work give it a try of renaming one of the datastores as I do not know how do you have two with the same name as it is not possible.
@Lalegre ,
Interesting. I completely missed that out.
Hi.
sorry for delay.
Yes , the issue, I think, is related to the two datastores with the same name even if each datastore has a different hard drive (the server has two, different, physical drive):
Hey @m4biz,
Go to the datastore tab, right click on it and rename it.
After that try to browse again.
Regards!
This post seems to be a test on the troubleshooting skills of the VMTN posse.
Thats a welcome change to the daily routine - I bite 😎
For arguments sake lets assume the screenshots posted here are NOT carefully photoshopped to be misguiding.
If yes - then the answer is simple: you cant browse datastore because you have no VMFS-volumes at all.
See screenshots with the partition-tables !
On ESXi 5 the expected partition-number of a VMFS-volume is 1 or 3.
Please post screenshots that proove that you actually have VMFS-partitions. 😏
Ulli