How to clean up the mapped RDM LUNs in the guest operating system and ESX server

Cleaning up the mapped RDM LUNs in the guest operating system

The following steps must be done in the guest operating system.


  1. From the vCenter navigation pane, select the Virtual Machine in which the RDM mapping is done.
  2. Right-click the virtual machine and turn off your guest operating system.
  3. Right-click the virtual machine and select Edit settings.

    The virtual machine properties dialog box appears.

  4. In the virtual machine properties dialog box, select the Hardware tab.

    You will find the entire RDM mapped entry as Mapped RAW LUN for every RDM entry.

  5. Select the RDM mapped entry and click Remove.

    The Removal Options appears in the right pane.

  6. In the Removal Options, select Remove from virtual machine and delete files from disk.
  7. Click OK.

    All the RDM mapped entries are removed from the guest operating system.

    After you remove RDM LUN entries from the guest operating system, you need to remove them from the ESX server.

Cleaning up the mapped RDM LUNs in the ESX server

The following steps must be done only by the ESX server administrator for a complete cleaning up of all RDM LUN entries in the ESX server.

Before you begin

Turn off your virtual machine before working on the virtual machine directory.


  1. Go to the virtual machine directory.
  2. Change to the directory cd /vmfs/volumes/ Data store path.


    # ls -l
    total 1024
    drwxr-xr-t 1 root root 1540 Apr 19 23:54 4bc702de-fa7ec190-992b-001a6496f353
    lrwxr-xr-x 1 root root   35 May 11 07:56 local_storage (1) -> 4bc702de-fa7ec190-992b-001a6496f353

    All the files and directories are listed here.

  3. Select the appropriate data store in which the virtual machines resides.
  4. Change the directory to data store.

    The virtual machine directory is displayed here.

  5. Change the directory to virtual machine in which you want to clean up RDM LUN mapping.

    All the files are listed in the virtual machine directory.

  6. Delete all vmdk files, which have SMVI string embedded. Alternatively, you can also identify the vmdk file using LUN name.

    Alternatively, you can also identify the vmdk file using LUN name.


    If you have a vmdk file of the LUN name as rdm1, delete only rhel4u8-141-232_SMVI_vol_esx3u5_rdm1-rdmp.vmdk and rhel4u8-141-232_SMVI_vol_esx3u5_rdm1.vmdk files.


    Delete vmlnx5U4-197-23_SMVI_10.72.197.93_C4koV4XzK2HT_22-rdmp.vmdk and vmlnx5U4-197-23_SMVI_10.72.197.93_C4koV4XzK2HT_22.vmdk vmlnx5U4-197-23_SMVI_10.72.197.93_C4koV4YG4NuD_53-rdmp.vmdk files.

  7. Remove the vmdk file entries from the virtual machine configuration file (vmx) as well.

    The following is an example of removing vmdk file entries from the vmx file.






    Name of the virtual machine


    Indicates that this vmdk file is created by SnapManager for Virtual Infrastructure server


    Name of the volume where the LUN is created


    Name of the LUN


    Signifies that this is physically compatible RDM LUN


    Virtual Machine Disk File

    [root@ rhel4u8-141-232]# vi rhel4u8-141-232.vmx
    scsi3:1.fileName = "rhel4u8-141-232_SMVI__vol_esx3u5_rdm1.vmdk"
    scsi3:1.mode = "independent-persistent"
    scsi3:1.ctkEnabled = "FALSE"
    scsi3:1.deviceType = "scsi-hardDisk"
    scsi3:1.present = "TRUE"
    scsi3:1.redo = ""
  8. Delete the entries as specified in the preceding example, including quotes and commas except for the scsi3:1.present entry, which you should change to FALSE from TRUE.
  9. Save and quit the file.
  10. Turn on the virtual machine.

About Alex Hunt

Hi All I am Manish Kumar Jha aka Alex Hunt. I am currently working in VMware Software India Pvt Ltd as Operations System Engineer (vCloud Air Operations). I have around 5 Years of IT experience and have exposure on VMware vSphere, vCloud Director, RHEL and modern data center technologies like Cisco UCS and Cisco Nexus 1000v and NSX. If you find any post informational to you please press like and share it across social media and leave your comments if you want to discuss further on any post. Disclaimer: All the information on this website is published in good faith and for general information purpose only. I don’t make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this blog is strictly at your own risk. The Views and opinions published on this blog are my own and not the opinions of my employer or any of the vendors of the product discussed.
This entry was posted in Linux/CentOS, Vmware. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s