Search the VMware Knowledge Base (KB)
View by Article ID

Required vSAN and ESXi configuration for controllers based on the LSI 3108 chipset (2144936)

  • 9 Ratings
Language Editions


When a VMware vSAN (formerly known as Virtual SAN) cluster is using LSI 3108-based controllers, some configurations can result in instability and errors such as:
  • Drives and/or disk groups are marked as failed or unhealthy in the vSAN User Interface:
  • In the /var/log/vmkernel.log file of the ESXi host, you see entries similar to:

    WARNING: lsi_mr3: fusionReset:2565: megaraid_sas: Hardware critical error, returning FAILED.
    megasas_hotplug_work[0]: event code 0x010b
    megasas_hotplug_work[0]: event code 0x010c
    megasas_hotplug_work[0]: event code 0x10b
    megasas_hotplug_work[0]: event code 0x10c
    ScsiCore: 1486: Power-on Reset occurred on <vSAN_DEVICE_ID>

    Note: The preceding messages may appear in any order and combination. The sequence noted is only one possible message combination.


This article details required configuration settings to ensure stability and optimal performance of vSAN when running on RAID controllers that are based on the LSI 3108 chipset. As of March 31, 2016, the controllers currently supported for vSAN for which these settings are applicable are:


Note: The values below are the default values for vSAN 6.2 in ESXI 6.0 patch ESXi600-201608001 and later. If you are running this patch or later, there is no need to change the vSAN IO timeout settings using esxcfg-advcfg. For more information about this patch, see VMware ESXi 6.0, Patch Release ESXi600-201608001 (2145663).

To prevent device-related failures when running vSAN with LSI 3108-series controllers:
  1. Ensure that all components are validated against the VMware Compatibility Guide for vSAN (VCG). For more information, see the VMware Compatibility Guide.

    • Ensure that all storage-controller drivers and firmwares are compliant per the VCG.

      Note: Controller VCG links are provided in the Purpose section of this article.

  2. Configure the vSAN IO timeout settings.

    • This is not required if you are running ESXI 6.0 patch ESXi600-201608001 or later.
    • These commands must be run on each ESXi host in the vSAN cluster.
    • These commands are effective immediately. No reboot is required.
    • These commands result in persistent changes and remains configured across reboots.

      esxcfg-advcfg -s 100000 /LSOM/diskIoTimeout

      esxcfg-advcfg -s 4 /LSOM/diskIoRetryFactor

    If the storage controller drives are both vSAN and non vSAN disks, see Considerations when using both vSAN and non-vSAN disks with the same storage controller (2129050).


  • If driver or firmware updates are required, host reboots is necessary.
  • If the vSAN cluster is using LSI 3108-series controllers, failure to implement these recommendations may result in disk-failure behavior as described in the Symptoms section.

Additional Information

For detailed information about the certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x, see Certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x (2144614).


LSI 3108

See Also

Update History

08/12/2016 - Updated the KB with note about new default values in ESXI 6.0 patch ESXi600-201608001 and later. 11/15/2016 - Added vSAN 6.5 to Products

Language Editions


Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 9 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 9 Ratings