Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

The disk device enters All-Paths-Down (APD) after the volume was OFFLINE with LSI RAID use "megaraid_sas" (67590)

Last Updated: 5/8/2019Categories: InformationalTotal Views: 3945Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The volume shows OFFLINE in LSI RAID adapter,the ESXi disk device shows as All-Paths-Down (APD) while using the driver "megaraid_sas".

The host appears as "not-responding" in vCenter as the All-Paths-Down (APD) situation.

vmkernel.log shows entries similar to
2019-01-31T18:08:49.937Z cpu8:32927)WARNING: NMP: nmpCompleteRetryForPath:352: Retry cmd 0x28 (0x43b7b8340980) to dev "naa.600605b00cbc8cc020b70ac9d53e0eb1" failed on path "vmhba3:C2:T1:L0" H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article discusses a All-Paths-Down (APD) situation while volume was OFFLINE in LSI RAID adapter, and provides the solution for this scenario.

Cause

In some configuration, if there is LSI RAID volume used in ESXi. For example,the local datastore or RAID0 in vSAN enviroment

When the volume goes OFFLINE for some reason, such as disk fault etc, the HBA driver "megaraid_sas" only sends the SCSI sense code "NO_CONNECT" to ESXi. For example, the ESXi received following SCSI sense code "H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0"The SCSI sense code "H:0x1" mean "NO_CONNECT".

As there was no Permanent Device Loss (PDL), the disk device enters All-Paths-Down (APD).

ESXi only checks ASC/ASCQ and if it happens to be 0x25/0x0 or 0x68/0x0, it marks device as Permanent Device Loss (PDL). Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x (2004684)

Resolution

It is recommend to use "lsi_mr3". Many LSI HBA/RAID adapter support both "megaraid_sas" and "lsi_mr3". The dirver "lsi_mr3" was more perfect at this scenario. The PDL SCSI sense code will detected while use the "lsi_mr3".

Workaround

If some LSI RAID adapter were only support "megaraid_sas" in the HCL(Hardware Compatibility List). It's recommend to detach the APD disk device to isolated the APD deviced.

# esxcli storage core device set --state=off -d NAA_ID

For more details, refer to How to unmount a LUN or detach a datastore device from ESXi hosts (2004605)

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:

Related Versions:

Take Our Survey

Support Assistant