Cannot mount iSCSI Datastore

[virtually77]

After my Synology array automatic upgrade and subsequent reboot, my (3) ESXi nodes lost access to their iSCSI datastore. Reset of the ESXi nodes and the array have not allowed me to recover the iSCSI datastore. The other devices, NFS and other file partitions are OK on the array and no errors are apparent.

The datastore device, has a label, partition table and VOMA check returns no errors:

root@lab1:/var/log] esxcli storage vmfs extent list

Volume Name       VMFS UUID                            Extent Number  Device Name                           Partition

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

datastore1        58b98e95-b33ef9f3-efd1-00219b8ef6d6              0  naa.60024e806d55630012d4662f0a53de21          3

MYDS01            57d71aab-d3e309a5-1bc7-00219b8ef6d6              0  naa.6001405affe9843d81d6d412ad80f7df          1

[root@lab1:/var/log] partedUtil getptbl /vmfs/devices/disks/naa.6001405affe9843d81d6d412ad80f7df
gpt
14490 255 63 232783872
1 2048 232783838 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

[root@lab1:/var/log] voma -m vmfs -f check -d /vmfs/devices/disks/naa.6001405affe9843d81d6d412ad80f7df:1
Checking if device is actively used by other hosts
Running VMFS Checker version 1.2 in check mode
Initializing LVM metadata, Basic Checks will be done
Phase 1: Checking VMFS header and resource files
Detected VMFS file system (labeled:'MYDS01') with UUID:57d71aab-d3e309a5-1bc7-00219b8ef6d6, Version 5:60
Phase 2: Checking VMFS heartbeat region
Phase 3: Checking all file descriptors.
Phase 4: Checking pathname and connectivity.
Phase 5: Checking resource reference counts.

Total Errors Found: 0

If I try to look at the volume at "/vmfs/volumes", I get the below error:

[root@lab1:/vmfs/volumes] ls
ls: ./57d71aab-d3e309a5-1bc7-00219b8ef6d6: Function not implemented

The vmkernel.log is seeing the below errors

2017-03-03T21:21:00.568Z cpu0:35235)HBX: 955: 'MYDS01': HB at offset 3477504 - Setting pulse failed: Not supported:

2017-03-03T21:21:00.568Z cpu0:35235)  [HB state abcdef02 offset 3477504 gen 12081 stampUS 19771280330 uuid 58b9911c-f5fc16cb-57f2-00219b8ef6d6 jrnl <FB 0> drv 14.61 lockIm

2017-03-03T21:21:00.568Z cpu0:35235)WARNING: FSAts: 1498: Denying reservation access on an ATS-only vol 'MYDS01'

2017-03-03T21:21:00.568Z cpu0:35235)WARNING: HBX: 2227: ATS-Only VMFS volume 'MYDS01' is not mounted. This host does not support ATS, or ATS initialization failed.

2017-03-03T21:21:00.568Z cpu0:35235)WARNING: HBX: 2240: Failed to initialize VMFS distributed locking on volume 57d71aab-d3e309a5-1bc7-00219b8ef6d6: Not supported

2017-03-03T21:21:00.568Z cpu0:35235)Vol3: 3147: Failed to get object 28 type 1 uuid 57d71aab-d3e309a5-1bc7-00219b8ef6d6 FD 0 gen 0 :Not supported

2017-03-03T21:21:00.568Z cpu0:35235)WARNING: Fil3: 2469: Failed to reserve volume f530 28 1 57d71aab d3e309a5 21001bc7 d6f68e9b 0 0 0 0 0 0 0

2017-03-03T21:21:00.568Z cpu0:35235)Vol3: 3147: Failed to get object 28 type 2 uuid 57d71aab-d3e309a5-1bc7-00219b8ef6d6 FD 4 gen 1 :Not supported

I cannot come up with process/procedure to recover the datastore.

I tried a "vmkfstools -L lunreset", though it didn't resolve anything.

Any ideas or help?

[nettech1 · Accepted solution]

have you tried connecting to your Synology iSCSI LUN from a Windows PC?

[RAJ_RAJ]

Hi ,

Kindly check you have chap configuration , then please remove that and try to connect .

Also iSCSI port binding configuration .

Check the iSCSI lun is accessible from any other machine (windows / linux )

[virtually77]

Using Windows was good hint, but I couldn't find a solution to complete it. Seems like most of what I found was related to "vmfs3".

I did find a tool called "VMFS_Recovery" but can only use it in "read" mode, so no "recovery".

I was able to use Ubuntu and a package "vmfs-tools" to mount the datastores and copy the relevant VM folders.

ownside is they all come back as "thick" vs. "thin".

Thanks for the suggestion.