Armitage318
asked on
Serious issue with one storage (VMware cluster)
Hi, I have a 9 nodes VMware cluster (ESXi 6.0).
I have a SAN with five storage (Dell) mounted through iSCSI.
One of our storage is having serious issues (it appears "unresponsive" in PowerVault GUI).
Fortunately, there is just one VM on that storage.
I suspect that this storage issue is causing problem on all hosts (4 hosts appear as "unreachable").
I powered off and re-registered affected VM (I mean: the one that has disks on problematic storage).
I would like to simply unmount that datastore from my cluster.. but I can't do that.
Even if there is no VM running on that datastore, it seems "in use".
How can I forcefully unmount it?
Thank you
I have a SAN with five storage (Dell) mounted through iSCSI.
One of our storage is having serious issues (it appears "unresponsive" in PowerVault GUI).
Fortunately, there is just one VM on that storage.
I suspect that this storage issue is causing problem on all hosts (4 hosts appear as "unreachable").
I powered off and re-registered affected VM (I mean: the one that has disks on problematic storage).
I would like to simply unmount that datastore from my cluster.. but I can't do that.
Even if there is no VM running on that datastore, it seems "in use".
How can I forcefully unmount it?
Thank you
I've seen what sounds like similar behaviour from ESXi hosts when a SAN controller partially failed.
It sounds as if you have 5 LUNs on a single SAN. If the VM is shut down, you might try removing the host mappings from the SAN at which point it should be possible to remove the datastore.
It sounds as if you have 5 LUNs on a single SAN. If the VM is shut down, you might try removing the host mappings from the SAN at which point it should be possible to remove the datastore.
Hi,
even if you don't have VM anymore on this datastore it can be use by :
- iso
- esx logs (syslog and scratch partition)
- HA datastore heartbeat
- ESX locks never released for some reasons
- maybe other thing...
so unmount will failed
If I were you I would not unmap or delete it before looking it deeply and understanding what is used on it
even if you don't have VM anymore on this datastore it can be use by :
- iso
- esx logs (syslog and scratch partition)
- HA datastore heartbeat
- ESX locks never released for some reasons
- maybe other thing...
so unmount will failed
If I were you I would not unmap or delete it before looking it deeply and understanding what is used on it
ASKER
Hi Mr Tortur,
I am sure that I had no ISOs or logs on that datastore.
I don't know precisely how to check datastore heartbeat. I see this through vSphere client:
how can I check further for ESX locks?
Thank you!
I am sure that I had no ISOs or logs on that datastore.
I don't know precisely how to check datastore heartbeat. I see this through vSphere client:
how can I check further for ESX locks?
Thank you!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Torture very accurate
Glad it was usefull then :-)
ASKER
Another host display warning "Virtual machine creation may fail because agent is unable to retrieve VM creation options from the host (N5Vmomi5Fault17HostCommun