Skip to main content

Unable to mount the datastore on ESXI host with message: This host does not support ATS, or ATS initialization failed

  Symptoms

Host has lost connection with the data store.

In the vmkernel.log you see message similar to:

2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397) [HB state abcdef02 offset 3616768 gen 33 stampUS 17643062981621 uuid 5783c299-eea160ad-aae8-e0db550386c6

jrnl <FB 0> drv 14.61 lockImpl 4]

2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)WARNING: FSAts: 1498: Denying reservation access on an ATS-only vol 'SYN01'

2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)WARNING: HBX: 2227: ATS-Only VMFS volume 'SYN01' is not mounted. This host does not support ATS, or ATS ini

tialization failed.

2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)WARNING: HBX: 2240: Failed to initialize VMFS distributed locking on volume 56f52615-c7d247e4-e688-90b11c26

8865: Not supported

2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)Vol3: 3147: Failed to get object 28 type 1 uuid 56f52615-c7d247e4-e688-90b11c268865 FD 0 gen 0 :Not support

ed

2017-01-31T20:49:15.992Z cpu13:34177 opID=e922c397)WARNING: Fil3: 2469: Failed to reserve volume f530 28 1 56f52615 c7d247e4 b190e688 6588261c 0 0 0 0 0 0 0

 Resolution
  1. Run below command to check the locking mode.

    [root@host108:~] esxcli storage vmfs lockmode list

    You see output similar to:

    Volume Name UUID Type Locking Mode ATS Compatible ATS Upgrade Modes ATS Incompatibility Reason

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

    datastore1 5714d652-9d35c588-8184-a4badb2db0d4 VMFS-5 ATS+SCSI false None Device does not support ATS

    SYN01 56f52615-c7d247e4-e688-90b11c268865 VMFS-5 ATS true No upgrade needed

    SYN02 578356c4-5abc30bc-2cbd-a4badb2db0d4 VMFS-5 ATS+SCSI false None Device does not support ATS

    SYN03 57835724-1494af5a-ff89-a4badb2db0d4 VMFS-5 ATS+SCSI false None Device does not support ATS

    SYN04 57835750-afdce504-9a68-a4badb2db0d4 VMFS-5 ATS+SCSI false None Device does not support ATS

  2. Unmount the VMFS datastore from all the ESXi hosts which are using it and keep it mounted to the ESXi on which its locking mode is showing as ATS.
  3. Run the below command to set the locking mode to ATS+SCSI

esxcli storage vmfs lockmode set -s -l VMFS_label

After running the above command, all the ESXi hosts which were not able to see the datastore will be able to see it now.

Comments

Post a Comment

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...
Post a Comment
Read more