Hello everyone and thanks in advance for any help you can offer!
I have four hosts in a vCenter cluster that are all mounting a single data store from two different iSCSI servers. Three of these hosts are fine however one of the hosts is no longer mounting the either datastore. The network port binding shows complaint an active for all the hosts. The targets show up and the devices show up. But when I look for datastores, they do not show up on this one particular host. However, from the host that's not mounting the stores I can click new datastore and it looks like it would cheerfully let me create a new datastore on either of the iSCSI devices but warns me "An unresolved VMFS volume with signature 5713f51b-853a7b5f-bc6e-003048f5d0f4 has been detected on this disk.". Obviously, I did not hit the go button, as to not destroy my existing datastores that contain live data.
It's almost as if the host does not recognize the datastore as being valid. I don't know though. I have been though hundreds of KB articles and tried everything I can find in an attempt to resolve and nothing has worked thus far. Short of reinstalling this particular host, I'm at a loss as for what to do next. I can provide whatever debug info might help to better understand what's happening but browsing through the logs, I don't see anything that's glaring or obvious.
Thanks for any help and I apologize in advance if the description seems vague but I don't know what else to provide since I've never ran into this kind of problem (or any other major problems really).
-brian
It's a LUN present issue. =>
Check if the LUN ID is the same across all host. Or unmount the datastore and re-signature it.
PS : I hope it's not a production environment ^^ #FreeNAS
Yeah, it's a production environment. I have VM and host level backups to an external server and I've never had a problem with FreeNAS. But yes, I do know what you mean!
Out of sheer frustration I called support and turns out that the hosts were thinking the DS was a snapshot datastore. All is resolved now and here is the article that resolved it for me.
(BTW, I did _not_ resignature the volumes).
-brian
I knew it was LUNs detected as snapshot (Note that I provided the same KB)
:smileylaugh:
