When running a storage vMotion task on a powered on virtual machine, you experience these symptoms:
The storage vMotion task fails while trying to change the pointer file to another datastore.
Multi-writer enabled (Oracle RAC Server) where multi-writer is supported and the SCSI bus sharing is set to Physical
When performing a Storage vMotion on a physical-mode RDM to relocate the pointer (RDM mapping) file to a different datastore, the operation may fail with an error similar to the following:
“A fatal internal error occurred. Failed to start SvMotion. Error during disk setup.”
VMware vCenter 8.x
VMware ESXi 8.x
With physical mode RDM, the VM is directly accessing the LUN, bypassing VMFS disk handling. There is nothing vCenter can “relocate”, so disk setup fails immediately before performing the actual Storage vMotion
Reference:
Migrating virtual machines with Raw Device Mappings (RDMs)
Migrating virtual machines with Raw Device Mappings