Hey Checkyourlogs Fans,

When migrating a Storage Spaces Direct (S2D) Cluster from Windows Server 2019 to Windows Server 2022 with a fresh OS rebuild, a common issue arises during cluster validation. Specifically, unsupported miniport drivers, such as IaRNVME, can disrupt S2D functionality. For optimal performance and compatibility, Windows Server 2022 prefers the storenvme native driver for NVMe buses in S2D clusters. This blog post will guide you through identifying and resolving this issue.

The Problem

During the cluster validation process, you might encounter errors indicating that specific NVMe drives are using unsupported drivers. Upon inspection in Device Manager, instead of seeing the expected Standard NVM Express Controller, you’ll notice entries like Intel(R) SSD DC P4500/4600/4501/4601/4608 Series for the storage controllers — one entry per disk. These entries indicate the presence of built-in vendor-specific drivers (e.g., IaRNVME) rather than the preferred storenvme native driver.

A screenshot of a computer Description automatically generated

This incompatibility can cause S2D to fail to initialize correctly, jeopardizing the cluster’s performance and reliability.

Yellow lines with black text Description automatically generated

The Solution

Fortunately, resolving this issue is straightforward. By reverting the NVMe drives to use the storenvme native driver, you can restore S2D compatibility. Follow these steps:

Step 1: Open Device Manager

  1. Log into one of the cluster nodes.
  2. Open Device Manager (type devmgmt.msc in the Run dialog or search bar).

Step 2: Locate the Problematic Drivers

  1. Expand the Storage controllers section.
  2. Look for entries labeled Intel(R) SSD DC P4500/4600/4501/4601/4608 Series or similar.
  3. Verify that these entries correspond to the disks used in your S2D configuration.

Step 3: Uninstall the Vendor Drivers

  1. Right-click on one of the problematic Intel(R) drivers.
  2. Select Uninstall device.

A screenshot of a computer Description automatically generated

  1. In the uninstallation dialog, check the box for Delete the driver software for this device.
  2. Click Uninstall to proceed.
  3. Repeat this process for each NVMe disk listed under Storage controllers.

A screenshot of a computer Description automatically generated

Step 4: Rescan in Device Manager

  1. Once all problematic drivers have been uninstalled, click the Action menu in Device Manager.
  2. Select Scan for hardware changes.

  1. The system will automatically detect the NVMe drives and revert them to the native Standard NVM Express Controller driver.

A screenshot of a computer program Description automatically generated

Step 5: Verify the Fix

  1. Confirm that all NVMe drives are listed under Standard NVM Express Controller in Device Manager.
  2. Re-run the cluster validation to ensure no remaining issues with the S2D configuration.

Conclusion

Unsupported vendor-specific NVMe drivers can disrupt Storage Spaces Direct functionality during a migration to Windows Server 2022. By uninstalling these drivers and reverting to the native storenvme driver, you can ensure that S2D operates as intended, leveraging the full performance and reliability of your NVMe storage.

This straightforward fix highlights the importance of validating and standardizing driver configurations during any OS migration or cluster rebuild. If you encounter similar issues, this guide should help you get back on track efficiently.

 

Thanks,

 

Dave