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

Storage Center systems with Front End SAS connectivity show lun capacity 0MB (67032)

Last Updated: 2/10/2019Categories: TroubleshootingTotal Views: 7571Language:
Chinese (Simplified)JapaneseEnglish

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

[root@vmserver3:~] esxcfg-scsidevs -c
Device UID Device Type Console Device Size Multipath PluginDisplay Name
naa.6000d310041df2000000000000000005 Direct-Access /vmfs/devices/disks/naa.6000d310041df2000000000000000005 0MB NMP VMFS5
naa.6000d310041df2000000000000000007 Direct-Access /vmfs/devices/disks/naa.6000d310041df2000000000000000007 0MB NMP VMFS02
naa.6000d310041df2000000000000000009 Direct-Access /vmfs/devices/disks/naa.6000d310041df2000000000000000009 0MB NMP VMFS41
naa.6000d310041df200000000000000000a Direct-Access /vmfs/devices/disks/naa.6000d310041df200000000000000000a 1048576MB NMP VMFS6
naa.6000d310041df200000000000000000b Direct-Access /vmfs/devices/disks/naa.6000d310041df200000000000000000b 0MB NMP VMFS7

### Devices are visible but size is shown as 0MB

sas.5d0946606ea42c00-sas.5000d310041df21e-naa.6000d310041df200000000000000000b:
Runtime Name: vmhba4:C0:T1:L7
Device: naa.6000d310041df200000000000000000b
Device Display Name: VMFS7
Group State: standby
Array Priority: 0
Storage Array Type Path Config: {TPG_id=61470,TPG_state=STBY,RTP_id=30,RTP_health=UP}
Path Selection Policy Path Config: {current path; rank: 0}

### Standby Path is used for the current path

naa.6000d310041df200000000000000000b : VMFS7
vmhba4:C0:T1:L7 LUN:7 state:standby sas Adapter: 5d0946606ea42c00 Target: 5000d310041df21e

naa.6000d310041df200000000000000000c : VMLOG01
vmhba4:C0:T1:L8 LUN:8 state:active sas Adapter: 5d0946606ea42c00 Target: 5000d310041df21e

### In NMP path list host shows only one path for the device

2019-01-25T21:59:54.421Z cpu7:66233)WARNING: NMP: nmpCompleteRetryForPath:387: Logical device "naa.6000d310041df200000000000000000b": awaiting fast path state update before retrying failed command again...
2019-01-25T21:59:55.421Z cpu17:65820)WARNING: NMP: nmp_RegisterDeviceEvents:923: Could not register events 0x180 on device "naa.6000d310041df200000000000000000b", Status: Not found. Event Registration will be retried on next path eval.
2019-01-25T21:59:55.421Z cpu14:66417)WARNING: NMP: nmpDeviceAttemptFailover:640: Retry world failover device "naa.6000d310041df200000000000000000b" - issuing command 0x439d80fff3c0
2019-01-25T21:59:55.421Z cpu14:66417)WARNING: NMP: nmp_SelectPathAndIssueCommand:4633: PSP selected path "vmhba4:C0:T1:L7" in a bad state (standby) on device "naa.6000d310041df200000000000000000b".
2019-01-25T21:59:55.421Z cpu14:66417)WARNING: NMP: nmpCompleteRetryForPath:357: Retry cmd 0x12 (0x439d80fff3c0) to dev "naa.6000d310041df200000000000000000b" failed on path "vmhba4:C0:T1:L7" H:0x1 D:0x0 P:0x0 Invalid sense data: 0x0 0x0

### vmkernel logs shows clearly that NMP is trying to access device on standby path

Purpose

In the Dell EMC Storage Compatibility Matrix, the 6.5 VMWare ESXi version is tested / supported with SAS front end connectivity. SAS driver "lsi-msgpt3" Version 12 and SCOS Versions 7.2.x and 7.3.x were included in this tested and supported solution. However, upgrades to VMWare ESXi 6.5 U1, 6.5 U2, and 6.7 automatically install updated lsi-msgpt3 SAS drivers, such as Version 16. Without manual intervention of configuring a module parameter on the driver, lsi-msgpt3 versions greater than 12 do not work properly (e.g., rebooting host sees LUN capacity of 0 bytes, lose access to SAS Front End volumes upon controller failover, PSOD kernel dumps) with ESXi 6.5 and SCOS.

Cause

Storage Center systems with Front End SAS connectivity have been officially tested and supported to work with ESXi version 6.7 .f you are encountering issues with ESXi 6.5 and SCOS 7.2 / 7.3, then the best practice setting is to modify the module parameter  for all versions of the lsi-msgpt3 SAS driver. It is a requirement for any version greater than 12.

Impact / Risks

Host is unable to mount the datastores after reboot

Resolution

List out the module parameter values

esxcli system module parameters list -m lsi_msgpt3

Modify the issue_scsi_cmd_to_bringup_drive module parameter

esxcli system module parameters set -p issue_scsi_cmd_to_bringup_drive=0 -m lsi_msgpt3

Validate that the module parameter value has been modified with the list command in Step 1

Reboot the ESXi host for the changed value to take effect.

Related Information

https://www.dell.com/support/article/us/en/04/sln313031/sc-storage-customer-notification-driver-compatibility-with-front-end-sas-connectivity?lang=en

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant