Solved

VSphere 5 iSCSI Datastore not found

Posted on 2014-01-20
12
1,067 Views
Last Modified: 2014-07-01
Question: Why did I lose my datastore?

The environment is (2) esxi hosts (5.0.1, and 5.1) with iSCSI (Synology software iSCSI)
In the process of shutting down and moving hardware (no changes) , the iSCSI datastore was not found after startup by either host. iSCSI LUN was found and all paths checked out, however it was unable to mount datastore.
The only way I was able to mount datastore was to re-signature datastore with new UUID. This datastore is only used for backup, and we were able to make necessary changes. Just need to understand what happened.
0
Comment
Question by:toadstool331
  • 6
  • 5
12 Comments
 
LVL 119
ID: 39794721
This does occasionally does happen (no matter which SAN you have!), and there was no need to re-sig the datastore, you could have re-attached without doing this.

You probably found the LUN was presented, to the Hosts, but the datastore was missing?

You are not the first to ask this question on EE, it's asked about 30 times a year!

Is your Synology iSCSI SAN on the VMware HCL ?
0
 

Author Comment

by:toadstool331
ID: 39794762
Synology model is DS1512+ (listed in compatibility guide)

Yes, the LUN was presented. When adding datastore, first option to mount existing (without modifying sig) failed repeatedly.
0
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 250 total points
ID: 39794775
Again, this does happen on occasion, and the correct method, is to go to the console or remotely via ssh, and use the esxcfg-mpath command to re-attach the iSCSI LUN permanently.
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 

Author Comment

by:toadstool331
ID: 39794913
What is the easiest way after the re-signature for the guest OSs to connect to the updated datastore?
0
 
LVL 119
ID: 39794954
Guest OS, this was used as an RDM?

Guest VMs are normally located on the datastore?

what's the issue?
0
 

Author Comment

by:toadstool331
ID: 39795034
The guest OS cannot start because it does not see the hard disk vmdk files on the iscsi datastore.  After the re-signature of the datastore the datastore name has been changed.  There is something that needs to be edited I believe to tell the guest where to find those vmdk files now.
0
 
LVL 119
ID: 39795066
Check the datastore is not missing the disks?

Easiest way, would be to remove the virtual disks from the VM inventory, e.g. remove from VM, do not delete from disk.

Add the disks again, by browsing the datastore.

Does this issue, of datastore loss, happen alot?

you may want to check your ESXi/ESX logs (/var/log/vmkernel.log)

but the logs are no presistant between reboots on ESXi, unless you are logging to persistent storage of Remote Syslog Server.

and look for path loss, information
0
 

Author Comment

by:toadstool331
ID: 39795118
Trying to remove the virtual disk from the vm results in an error, Invalid configuration for device '0'.  It will not remove the virtual disk.
0
 
LVL 119
ID: 39795132
Unregister the VM from the inventory. (do not delete from disk).

edit the VMX file with VI, WinSCP, and Remove the reference to the virtual disks.

make sure you have a backup of the VMX file.
0
 

Author Closing Comment

by:toadstool331
ID: 39795135
Thanks Savant!
0
 
LVL 119
ID: 39795157
No problems, you also missed MVE, & Expert of the Year 2013, 2011, 2012!

keep an observation on your logs!
0
 

Expert Comment

by:benfis
ID: 40170523
I had a similar problem with a HA cluster, where the passive server was lost during firmware upgrades.

Problem:
On two ESXi 5.1 hosts, I was able to remount a volume using the vSphere Client after selecting the corresponding path and choosing "use existing signature" for mounting.
On a third ESXi 5.1 host, I only was offered the option "format", while "use existing signature" and "resignature" as well where in-active.

Cause: It appears that the volume was mistaken for a snapshot by this host.

Solution:
I logged into the esxi-host by ssh and checked for snapshots by
# esxcli storage vmfs snapshot list

Subsequently I mounted the volume by
# esxcli storage vmfs snapshot mount -l <label>|-u uuid

I was surprised but glad this worked even though the vSphere GUI refused to do such.
More details can be found in KB article 1011387 from vmware, e.g. you may need to unmount the "snapshot" as such after mounting the volume.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question