Skip to main content
NetApp Knowledge Base

Volumes and VMs briefly not accessible during a takeover

Last Updated:

Applies to

  • ONTAP 9
  • Volume
  • SVM
  • VMware


  • During an upgrade and takeover, some volumes are briefly not available and some VMs are unavailable for 1-5 seconds
  • Error when powering on VM:

File system specific implementation of OpenFile[file] failed

Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/vol1/virtual1.vmdk' or one of the snapshot disks it depends on. 110 (Connection timed out) Module Disk power on failed.

Cannot open the disk '/vmfs/volumes/vol1/virtual1.vmdk' or one of the snapshot disks it depends on. 110 (Connection timed out)

  • The issue is not present on all volumes and VMs
  • VMware logs are not showing signs of disconnection or All-Paths-Down (APD)

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.