When attempting to add a Raw Device Mapping (RDM) to the VMs, the Target LUN list appears empty.
search cancel

When attempting to add a Raw Device Mapping (RDM) to the VMs, the Target LUN list appears empty.

book

Article ID: 435880

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • After migrating two VMs participating in a Microsoft cluster service between clusters, the RDM LUNs cannot be re-added to the primary VM.
  • Although the LUNs are visible as "Connected" in the ESXi storage device list, the "Target LUN" selection dialog remains empty during the "Add New RDM Disk" wizard.
  • This issue also occurs if the shared RDM is still actively attached to a secondary cluster node that is currently powered ON, as the ESXi host places a strict lock on the .vmdk pointer file.

Environment

VMware ESXi 8.x

Cause

  • The migration of clustered virtual machines with Raw Device Mappings was performed without following mandatory shared storage migration procedures, resulting in stale locks or incorrect device registration.
  • The environment may be incorrectly utilizing the 'Multi-writer' sharing flag for a Windows Server Failover Cluster (WSFC). The Multi-writer flag bypasses standard file-locking mechanisms, is unsupported for WSFC per KB 313230 and contributes to UI attachment failures.

Resolution

To restore the shared RDM configuration, perform the following steps:

  1. Ensure the RDM pointer file is completely removed from all secondary cluster nodes.

    • Note: If the secondary VM is actively running production and the RDM cannot be removed, a maintenance window is required to power off the secondary node. This releases the file lock, allowing the vSphere UI to select the existing pointer file. Ensure the 'Multi-writer' flag is removed (set to No Sharing) before powering the nodes back on.

  2. Perform a Rescan Storage and Rescan Adapter on all ESXi hosts within the cluster to refresh LUN availability and clear stale metadata/locks.

  3. Right-click the Primary VM > Edit Settings > Add New Device > RDM Disk.

  4. Select the desired Target LUN (now visible) and complete the wizard.

  5. On the Secondary VM, select Add New Device > Existing Hard Disk.

  6. Navigate to the Primary VM's datastore directory and select the .vmdk RDM pointer file created in Step 3.

Additional Information

Migrating virtual machines with Raw Device Mappings (RDMs) from one vSphere Cluster to another