2.To find the unique identifier of the LUN housing the datastore to
be removed, run this command:
This command generates a list of VMFS datastore volumes and their related
unique identifiers. Make a note of the unique identifier (NAA_ID) for the datastore you want to unmount as this will be used later
If the VMFS filesystem you are attempting to unmount has active I/O or has not
fulfilled the prerequisites to unmount the VMFS datastore, you see an error in
the VMkernel logs similar to:
VC: 637: unmounting opened volume ('4e414917-a8d75514-6bae-0019b9f1ecf4'
'LUN01') is not allowed.
VC: 802: Unmount VMFS volume f530 28 2 4e414917a8d7551419006bae f4ecf19b
4 1 0 0 0 0 0 : Busy
4.To verify that the datastore has been unmounted, run the command:
esxcli storage filesystem list
The output is similar to:
----------------------------------- ------- ------ -----------
VMFS-5 140660178944 94577360896
VMFS-3 146028888064 7968129024
VMFS-3 146028888064 121057050624
4e414917-a8d75514-6bae-0019b9f1ecf4 false VMFS-unknown
version 0 0
Note that theMountedfield is set tofalse,
theTypefield is set toVMFS-unknown version,
and that noMount Pointexists.
The unmounted state of the VMFS datastore persists across reboots. This is the
default behavior. If you need to unmount a datastore temporarily, you can do so
by appending the--no-persistflag to theunmountcommand.
5.To detach the device/LUN, run the command:
esxcli storage core device set --state=off -dNAA_ID
6.To verify that the device is offline, run the command:
esxcli storage core device list -dNAA_ID
The output, which shows that theStatusof the disk isoff, is similar to:
Display Name: NETAPP Fibre Channel Disk
Has Settable Display Name: true
Device Type: Direct-Access
Multipath Plugin: NMP
SCSI Level: 4
Is Pseudo: false Status: off
Is RDM Capable: true
Is Local: false
Is Removable: false
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Thin Provisioning Status: yes
VAAI Status: unknown
Running thepartedUtil getptblcommand on the device shows that the device is not found.
Error: Could not stat device
/vmfs/devices/disks/naa.60a98000572d54724a34655733506751 - No such file or
Unable to get device /vmfs/devices/disks/naa.60a98000572d54724a34655733506751
7.If the device is to be permanently decommissioned, it is now
possible to unpresent the LUN from the SAN. For more information, contact your
storage team, storage administrator, or storage array vendor.
8.To rescan all devices on the ESXi host, run the command:
The devices are automatically removed from the Storage Adapters.
rescan must be run on all hosts that had visibility to the removed LUN.
the device is detached, it stays in an unmounted state even if the device is
re-presented (that is, the detached state is persistent). To bring the device
back online, the device must be attached. To do this via the command line, run
esxcli storage core device set --state=on -dNAA_ID
9.If the device is to be permanently decommissioned from an ESXi
host, (that is, the LUN has been or will be destroyed), remove the NAA entries
from the host configuration by running these commands:
a.To list the permanently detached devices:
esxcli storage core device detached list
The output is similar to:
b.To permanently remove the device configuration information from
The reference to the device configuration is permanently removed from the ESXi
Note:If the device is detached but still presented (step 7 was
skipped), the command above fails to permanently remove the device from the
system, and the device is automatically re-attached. You must complete step 7
for the device to be permanently removed.