ESXi 6.5 Connecting FC Datastore

[bmclure]

We have recently installed ESXi 6.5 on one of our hosts.  We are currently running 5.1 but needed ESXi 6 or better for some of the VM's that we wanted to deploy.  This host in question was previously connected to the Fiber Channel (Nexsan) Datastore before we installed 6.5.  How do I get the Datastore back on version 6.5, it shows up on the Devices but I'm worried about it trying to format the Datastore because this already has other VM's shared with our other host in our network. 

[daphnissov]

If it recognizes the file system, it should automatically mount it as a datastore. If it's not doing that and you insist it is a valid VMFS datastore, do not format it or you'll delete the data. I'm unfamiliar with Nexsan, so you may want to contact their support for a procedure.

[HassanAlKak88]

Hello,

From SSH to host, use the following to check the status of your VMFS Datastores: esxcli storage filesystem list . Check the status under the Mounted column False or True.

If it is False use the following to mount it: esxcli storage filesystem mount [-u UUID | -l label | -p path ]

Please consider marking this answer "CORRECT" or "Helpful" if you think your question have been answered correctly.

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak

[bmclure]

Ok, using ssh I have verified that the FC datastores are not showing up in the list. See below..  But it shows the correct datastores under devices on the web ui.

[root@air-esx04:~] esxcli storage filesystem list

Mount Point                                        Volume Name  UUID                                 Mounted  Type       Size       Free

-------------------------------------------------  -----------  -----------------------------------  -------  ----  ---------  ---------

/vmfs/volumes/456b3deb-88742d12-9793-9a47200febaa               456b3deb-88742d12-9793-9a47200febaa     true  vfat  261853184  104968192

/vmfs/volumes/5c487510-de0d4610-57ad-001ec953682a               5c487510-de0d4610-57ad-001ec953682a     true  vfat  299712512   80486400

/vmfs/volumes/412e40ea-2c40a836-f35a-581349625726               412e40ea-2c40a836-f35a-581349625726     true  vfat  261853184  261844992

[a_p_]

Please check whether the steps in the "Command line" section in https://kb.vmware.com/s/article/1011387​ will help.

André

[bmclure]

[root@air-esx04:~] esxcli storage vmfs snapshot list

51899e70-0679072a-c23c-002219c46ec5

   Volume Name: NEXSAN_LUN_1

   VMFS UUID: 51899e70-0679072a-c23c-002219c46ec5

   Can mount: true

   Reason for un-mountability:

   Can resignature: false

   Reason for non-resignaturability: the volume is being actively used

   Unresolved Extent Count: 1

51899e52-65c57303-b24d-002219c46ec5

   Volume Name: NEXSAN_LUN_0

   VMFS UUID: 51899e52-65c57303-b24d-002219c46ec5

   Can mount: true

   Reason for un-mountability:

   Can resignature: false

   Reason for non-resignaturability: the volume is being actively used

   Unresolved Extent Count: 1

Looks like a signature problem with the Nexsan LUN's.  I guess I could mount these without resignature but I don't know if this will be a permanent fix.  I have other hosts that use these same datastores and I'm reluctant to try anything that might disrupt service.

[a_p_ · Accepted solution]

LUNs are considered as Snapshot-LUNs if an ESXi host has seen the same before on another controller, channel, etc.

Anyway, in your case, follow the KB article, and run the command to persistently mount the datastore without resignaturing.

André

[bmclure]

Thanks, that worked perfectly!