Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Raw Device Mapping for local storage (1017530)

Last Updated: 5/14/2021Categories: InformationalTotal Views: 40223Language:
Chinese (Simplified)JapaneseEnglish

59 like this article

Subscribe to get an email
newsletter with new updates

59 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

When attempting to configure a local datastore as a Raw Device Mapping (RDM), you experience these symptoms:

The option to create an RDM is grayed out

You cannot add a local volume to a virtual machine as a raw device mapping

Purpose

This article provides steps to configure local datasores as RDM.

Cause

By default, local storage devices are disabled as potential RDM candidates on an ESXi host due to most existing local controllers not meeting the hardware requirements to correctly address and communicate with an RDM disk.

Resolution

To configure an RDM on local storage with ESXi hosts, both of these conditions are required:

The candidate device must support SCSI Inquiry Vital Data Product (VPD) page code 0x83, which is used to directly address and communicate with RDM devices.

For more information on SCSI sense code, see Understanding SCSI Check Conditions in VMkernel logs during rescan operations (1010244).

The candidate device must export a global serial number, which enables the ESXi host to uniquely identify the device for use as an RDM.

Note: This capability to serve as an RDM may not be possible on some local controllers and their attached storage. Contact your hardware vendor to verify if your controller supports the required conditions, and for any technical support.

If you have a suitable controller, you can configure the local device as an RDM. Configuration of a local storage device as an RDM must be done using the Command Line Interface (CLI), it cannot be done through the vSphere Client.

To configure a local device as an RDM disk:

Open an SSH session to the ESXi host.

Run this command to list the disks that are attached to the ESXi host:

ls -l /vmfs/devices/disks

From the list, identify the local device you want to configure as an RDM and copy the device name.

Note: The device name is likely be prefixed with t10. and look similar to:

t10.F405E46494C4540046F455B64787D285941707D203F45765

To configure the device as an RDM and output the RDM pointer file to your chosen destination, run this command:

vmkfstools -z /vmfs/devices/disks/diskname /vmfs/volumes/datastorename/vmfolder/vmname.vmdk

For example:

vmkfstools -z /vmfs/devices/disks/t10.F405E46494C4540046F455B64787D285941707D203F45765 /vmfs/volumes/Datastore2/localrdm1/localrdm1.vmdk

Note: The size of the newly created RDM pointer file appears to be the same size and the Raw Device it it mapped to, this is a dummy file and is not consuming any storage space.

When you have created the RDM pointer file, attach the RDM to a virtual machine using the vSphere Client:

Right click the virtual machine you want to add an RDM disk to.

Click Edit Settings.

Click Add.

Select Hard Disk.

Select Use an existing virtual disk.

Browse to the directory you saved the RDM pointer to in step 5 and select the RDM pointer file and click Next.

Select the virtual SCSI controller you want to attach the disk to and click Next.

Click Finish.

You should now see your new hard disk in the virtual machine inventory as Mapped Raw LUN.

Notes:

As this virtual machine now has an attached local disk migration, using vMotion is not possible.

If you need to remove the local RDM mapping from the virtual machine, just apply the same process you would with a shared storage RDM. In the vSphere Client: right-click the virtual machine, click Edit settings, select the RDM disk and then click delete from disk. This does not delete the data on the disk, it only deletes the RDM mapping file.

Related Information

Migrating virtual machines with Raw Device Mappings (RDMs)
Identifying Raw Device Mappings (RDMs) using the vSphere Client
Difference between Physical compatibility RDMs and Virtual compatibility RDMs

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 8.0

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant