Skip to main content
NetApp Knowledge Base

Storage vMotion fails between NetApp controllers

  1. Last updated
  2. Save as PDF
Views:
330
Visibility:
Public
Votes:
0
Category:
virtual-storage-console-for-vmware-vsphere
Specialty:
virt
Last Updated:

Applies to

  • Vmware vCenter 6.5.0
  • ESXI 6.0
  • VMFS
  • ISCSI

Issue

  • Unable to perform a storage vMotion between two different VMFS datastores residing on different NetApp controllers

  • reviewing vmkernel.log file, the following SCSI command repeatedly fails during the storage vMotion:
    2020-05-14T08:20:43.114Z cpu4:19517545)ScsiDeviceIO: 2652: Cmd(0x43b640e9e380) 0x2a, CmdSN 0x1552470 from world 44236476 to dev "naa.<device_ID>" failed H:0x7 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0

  • No obvious storage array or network issues are found

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.