Skip to content Skip to sidebar Skip to footer

Vmware Iscsi an Error Occurred Please Try Again

During the migration of virtual machines files from an sometime HP MSA 2000 storage to a new storage organization Dell EMC Unity (both connected to ESXi hosts over SAN) I accept come across a problem when trying to remove an empty VMFS Datastore in VMWare vSphere. When trying to unmount the VMFS Datastore from ESXi hosts, an error message appears proverb that the datastore is still in utilise / decorated:

Unmount VMFS volume vmesxi2.woshub.com. The resource 'Datastore Name: MSA2000_LUN1 VMFS uuid: xxxxx--xxxxx-ten-xxxxx-xxxx' is in apply. Cannot unmount volume Datastore Name VMFS "file organization is busy".

Cannot unmount VMFS Datastore The resource s in use

Based on the mistake, it is clear that the VMFS datastore cannot be removed since ESXi hosts or vSphere are still using storage to write some data. According to the VMWare documentation, when removing LUN from vSphere y'all should check the post-obit points:

  • At that place are no virtual machine, template, snapshot or ISO image files on VMFS datastore (yous must migrate your VMs to another VMFS Datastore, power off and remove them, or unregister VMs in vSphere);
  • Storage I/O Control is disabled for datastore;
  • The datastore is not a part of the Datastore Cluster;
  • The LUN is not used as an RDM device;
  • VMFS datastore is not used to store vSphere HA data, Storage DRS, logs, dumps (/vmkdump/), vSAN information (/vsantraced/), technical support data (scratch partition), or virtual machine swap files.

The virtual machines have already been moved to a new datastore using Storage vMotion. Permit's run into what other files and folders remain on the VMFS datastorage:

system files on vmfs: logdir, sdd.sf? dbsData and naa…

As you can see, there are logdir (a directory with logs), sdd.sf (a directory with the description of SCSI devices), dbsData (a directory with the data of the distributed virtual switch) and naa… (VMFS metadata) folders remained.

In my case, ESXi host logs  are still located in the VMFS datastore (Scratch Location). Check out if the datastore is specified as a location of logs in the ESXi host settings. Go to Manage -> Settings -> Avant-garde System Settings. Find ScratchConfig.CurrentScratchLocation and Syslog.global.logDir and if your VMFS datastore is specified in information technology, alter the path to the logs directory.

ScratchConfig.CurrentScratchLocation and Syslog.global.logDir

Restart the ESXi host or restart the Syslog Server service on the host.

restart syslog on esxi

Allow'due south effort to unmount the datastore from the ESXi host again. Get to Manage -> Storage -> Storage Device. Find your LUN in the listing, select it and click Detaches the selected device from the host.

Detaches the selected LUN device from the vmware esxi host

In my case the error occurred once more:
Disassemble SCSI LUN The resource is in use.

Quite for a long time I was trying to find out who uses this datastore and decided that the easiest way in my example was to delete the partition table of VMFS datastore (of course, you should do it very carefully and make sure that y'all are removing the correct datastore).

  1. Connect over SSH to any ESXi host that has VMFS shop mounted;
  2. Re-create the ID of your datastore in the vSphere interface, and check on the ESXi host, which device and path to the VMFS store information technology matches: esxcfg-scsidevs -c | grep naa.6001438005df0dee0000700004be0000
    naa.6001438005df0dee0000700004be0000 Direct-Access /vmfs/devices/disks/naa. 6001438005df0dee0000700004be0000 512000MB NMP HP Fibre Channel Disk (naa.6001438005df0dee0000700004be0000)
                  esxcfg-scsidevs -thou | grep naa.6001438005df0dee0000700004be0000            
    naa.6001438005df0dee0000700004be0000:1 /vmfs/devices/disks/naa.6001438005df0dee0000700004be0000:one 570e5298-08f4c74e-ca3a-b4b52f5e2b38 0 MSA2000_LUN1
  3. Let'south see how much infinite is busy on the VMFS datastore (information technology'south nearly empty): df -h | grep MSA2000_LUN1
    VMFS-5 499.8G 1.4G 498.3G 0% /vmfs/volumes/MSA2000_LUN1
                  esxcfg-scsidevs             
  4. So we accept made sure that the datastore name and the store ID match the LUN that we want to remove;
  5. Now let'south get check data well-nigh segmentation table on your datastore: partedUtil getptbl /vmfs/devices/disks/naa.6001438005df0dee0000700004be0000
    gpt 65270 255 63 1048576000              ane              2048 1048575966 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
  6. In this instance, the LUN has a single partition with the VMFS file system;
  7. Delete the VMFS partitioning with the ID 1 from this disk (LUN). Please, exist very attentive!!!partedUtil delete /vmfs/devices/disks/naa.6001438005df0dee0000700004be0000 ane partedUtil delete vmfs partition

After deleting the segmentation, you can unmount the LUN in vSphere – Unmount Datastore. The 'datastore is in use' mistake won't not appear again.

unmount datastore on vmware esxi

Select the ESXi hosts to unmount the datastore from.

select esxi host to unmount datastore

Or you lot can brand Disassemble from the listing of connected storage devices on the ESXi host. The connection land will then change to Detached.

detach lun on esxi host

After that you lot can remove the VMFS store (Delete Datastore) and information technology will disappear from vSphere.

Delete Datastore on vmware esxi host

robeysudishild.blogspot.com

Source: http://woshub.com/vmfs-datastore-the-resource-is-in-use/

Post a Comment for "Vmware Iscsi an Error Occurred Please Try Again"