jezg
asked on
how to remount an existing datastore to a vmware esxi6.7 system
I was getting disk read errors on a virtual server running on the host so I tried to move the VM to a different datastore ,after unregistering, it but got errors.
I then unregistered all other VMs so I could unmount the drive containing the datastore and remove it to carry out offline disk checking.
I have since replace the drive, and it is visible, but cannot find any help about remounting the datastore, it will only let me create a new one.
Does anybody have any ideas ?
I then unregistered all other VMs so I could unmount the drive containing the datastore and remove it to carry out offline disk checking.
I have since replace the drive, and it is visible, but cannot find any help about remounting the datastore, it will only let me create a new one.
Does anybody have any ideas ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is this a local datastore or shared storage?
ASKER
Local data storage
Oh, you've selected and answer and closed this question!
I've no idea how that Answer is relevant if you have Local Storage not iSCSI shared storage.
Did that fix your issue?
I've no idea how that Answer is relevant if you have Local Storage not iSCSI shared storage.
Did that fix your issue?
ASKER
Thank you both for your comments:
Lieven,
I rescanned the adapters as suggested and the datastore was available again with no further action required.
Andrew,
Thank you for making me clarify the one missing piece of information
Lieven,
I rescanned the adapters as suggested and the datastore was available again with no further action required.
Andrew,
Thank you for making me clarify the one missing piece of information
getting disk read errors on a virtual server running on the host
needs investigation.
ASKER
Andrew,
I have (eventually) managed to copy all VMs to a different datastore and they all run normally.
I believe the disk read problems on the VMs was due to the HDD for the "faulty" datastore being housed in a drive caddy. However, I will confirm this in a couple of days by connecting the HDD directly when I am able to take the host offline
I have (eventually) managed to copy all VMs to a different datastore and they all run normally.
I believe the disk read problems on the VMs was due to the HDD for the "faulty" datastore being housed in a drive caddy. However, I will confirm this in a couple of days by connecting the HDD directly when I am able to take the host offline
single disk no RAID?