Skip to main content

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


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


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

  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.


Popular posts from this blog

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: &lt;START vmware-16.log&gt; b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664