Procedure to Change SCSI Controller from LS ILogic SAS to VMware Paravirtual for WSFC VMs with RDM Disks
search cancel

Procedure to Change SCSI Controller from LS ILogic SAS to VMware Paravirtual for WSFC VMs with RDM Disks

book

Article ID: 433896

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

This article provides the correct procedure and validation steps for migrating the SCSI controller type from LSI Logic SAS to VMware Paravirtual SCSI (PVSCSI) on Windows Server Failover Cluster (WSFC) virtual machines using Raw Device Mapping (RDM) disks.

Environment

VMware vSphere ESXi 8.0

Resolution

  1. Confirm application and cluster downtime, and ensure all in-guest services are properly shut down.
  2. Power off all WSFC nodes/VMs.
  3. Edit the virtual machine settings and change the SCSI controller associated with the RDM disks from LSI Logic SAS to VMware Paravirtual (PVSCSI) on each node (ensure configuration consistency across all nodes as per the WSFC guideline on vSphere).
  4. Power on the first node, followed by the remaining node(s).
  5. Log in to the guest OS and verify the controller change via:
                     Device Manager → Storage Controllers, and confirm that VMware Paravirtual SCSI is listed. Reference below:

Note: Remember that on configuring the boot disk/vmdk to use a PVSCSI controller, should VMware Tools be uninstalled, the VM will fail to boot successfully as it no longer has the required driver installed. Please install or reinstall the VMware Tools. Verify that the installation/reinstallation process includes "Paravirtual SCSI" as part of the installation suite if boot disk controller is being changed.

Read more on, Configuring disks to use VMware Paravirtual SCSI (PVSCSI) controllers.

There is a common point of confusion: even after migrating disks to a PVSCSI controller, the ddb.adapterType value in the RDM vmdk's may still display lsilogic. This behavior is expected and by design, as the ddb.adapterType setting does not reflect the active controller type for PVSCSI and must remain lsilogic for compatibility (for example, to avoid issues such as Storage vMotion failures). See more,  Adjusting the virtual SCSI adapter type in a VMDK file

 

Powered by Wolken Software