Yes, you can use putty to launch ssh session. Post the output of all commands here if possible.
Yes, please connect SSH session and perform these commands.
> I took the drive out and connected to another machine and ran a file scan on the drive, all the vmdk and flat files are on there as they were before in the Datastore.
Please explain what you did exactly. If possible use that other host to copy out your VMs.
The log messages shows some failure on the vmw_ahci controller. Not sure why it would behave after a reboot. But you can check how many AHCI controllers are there. Try a rescan and see if it works. If not
1. Then run below commands
esxcli system module list | grep vmw_ahci
If the Native AHCI driver shows disabled then run below command to enable it
esxcli system module set --enabled=true --module=vmw_ahci
2. If the above does not help check vibs using
esxcli software vib list | grep ahci
If this shows both sata–ahci and vmw_ahci vib , then try disabling vmw_ahci driver and let it use the sata-ahci driver.
Via SSH: esxcli system module set –enabled=false –module=vmw_ahci
After entering this command, reboot your host
With this, there are two possibilities, as I check the logs again it seems that the target is not responding (which means when system tried to bring WD drive up it failed as drive wasn't responding. But as you suggested same drive is coming up on other systems, this shouldn't be the drive itself. Next course to get this working on the same system is to update the driver and firmware for the disk.
Another scenario could be the partition table is corrupt and that's why its not getting detected for mount.
I would first update the driver and firmware for the drive and then, will look at the next step (Partition table).
When I took the drive out and connected to another machine I used UFS explorer to get the files out and see that there is a VMFS on the drive.
I ran the commands, esxcli system module list | grep vmw_ahci this showed as enabled
esxcli software vib list | grep ahci , Both show as enabled, if I disable the vmw driver will that stop the other drives working?
I have purchased a new drive and waiting for it to arrive, I think I will make a new Datastore then copy the data back into it but it will be interesting to fix this broken Datastore.
thank you for your help
UFSexplorer can be regarded as the reference tool for reading VMFS.
It can read VMFS-volumes that can NOT be repaired with ESXi itself.
What timezone you are working, we may be able to look at it together.
I have my VMs back up and running with a new drive and data restored from the other drive.
thank you for all the advice and help
I have to reply with the solution I found after going from version 6.5 to 6.7. I have to give all the credit to this person and not me.
[root@esxi:~] esxcli storage vmfs snapshot list
Volume Name: datastore2
VMFS UUID: 5af66348-b31aacc1-b478-ecb1d73e4acc
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
[root@esxi:~] esxcli storage vmfs snapshot listmount -l datastore2