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

Unable to claim the LUN back after unmasking it (1015252)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 22426Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Running a rescan after unmasking the masked path fails

In the VMkernel log files, you see an entry similar to:

Path vmhba34:C0:T1:L0 is claimed by plugin MASK_PATH, but current claimrule number 65535 indicates that it should be claimed by plugin NMP

Note: This log entry indicates that path (L0) is still claimed by MASK_PATH although there are no more MASK_PATHs for that LUN.

Resolution

To resolve this issue, you must remove the MASK_PATH claim rule, reload the path claiming rules from the configuration file and then unclaim each path to the masked device.

To unmask the paths:

List the current claim rules that are configured on the host:

ESXi 5.x: # esxcli storage core claimrule list
ESXi/ESX 4.x: # esxcli corestorage claimrule list

Run this command to remove the MASK_PATH claim rule:

ESXi 5.x: # esxcli storage core claimrule remove --rule claim_rule_number
ESXi/ESX 4.x: # esxcli corestorage claimrule delete --rule claim_rule_number

Where claim_rule_number is the MASK_PATH rule number that you created.

Run this command to reload the path claiming rules from the configuration file into the VMkernel:

ESXi 5.x: # esxcli storage core claimrule load
ESXi/ESX 4.x: # esxcli corestorage claimrule load

Run this command to verify that the claim rule was deleted correctly:

ESXi 5.x: # esxcli storage core claimrule list
ESXi/ESX 4.x: # esxcli corestorage claimrule list

Run this command to unclaim each path to the masked device:

ESXi 5.x: # esxcli storage core claiming unclaim -t location -A vmhba0 -C 0 -T 0 -L 2
ESXi/ESX 4.x: # esxcli corestorage claiming unclaim -t location -A vmhba0 -C 0 -T 0 -L 2

This ensures that all paths to the device are unclaimed successfully before running the claim.

Note: With ESXi/ESX 4.x, the esxcli corestorage claiming unclaim --type location vmhba1 command to unclaim paths might result in issues if the unclaim for one of the paths times out. VMware recommends that you use the esxcli corestorage claiming unclaim --type plugin --plugin MASK_PATH to unclaim paths.

Perform a rescan for the changes to take effect. Previously masked LUNs are now accessible by the ESXi/ESX host.

To rescan ESXi/ESX 4.x hosts, run the command:

esxcfg-rescan -A

This command rescans all HBAs.

For ESXi 5.x:

esxcli storage core claimrule run

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
ESX 环境中的 HP Automatic Server Recovery (ASR) (1010842)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.0

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant