Skip to main content
NetApp Knowledge Base

After storage rebooting source volume is no longer accessible

  1. Last updated
  2. Save as PDF
Views:
154
Visibility:
Public
Votes:
0
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

  • NetApp E-Series
  • SANtricity OS 11.80.1GA or earlier 
  • Offline Volume Copy
  • E-Series Platforms: EF300 and EF600 
    • The volume copy issue only affects volumes using BlockSizeProxy, which means these volumes are created with blockSize=512 and the volumes come from a volume group/DDP comprised of 4K NVMe drives.

volume block size.png

NOTE: Only an FC-type system can select Volume Block Size via GUI. If the host interface type is iSCSI, the default value is 512 and only creating volume via CLI can set blockSize=4K.

Issue

After storage reboot without clearing an existing OFFLINE copy pair, the following issues can be triggered:

1.  Volume Copy operation fails to start due to I/O error. 

  • MEL (Major Event Log): A:5/25/24, 5:45:46 AM (05:45:46) 2719 6600 Volume copy or import operation failed - Volume vol11 <--CRITICAL
  • DQ (trace buffer log): 05/25/24-05:45:45.060 CopyProxy 0000c002 failing volume copy - Background copy I/O error - 0x208

 2. One or both volumes in Copy Pair relation are inaccessible to the host, such as SAN boot failure from VMware hosts. 

 3.  If the start volume copy is from the target volume to the source volume, controller(s) go to lockdown with limited use of SYMbol due to the following assertion. 

05/27/24-07:20:54 (raidSched1): PANIC: Assertion failed: file /u/symsm/ccm_wa/symbios/RAIDCore-5207.1.7/m4_874_debian-5207.1.7/images/m4_e30_874_3000-08.74.02.00/eos/Application/RAIDLib/evfVolume.h, line 2520
2024-05-27 07:20:58.197667
Assertion failed: file /u/symsm/ccm_wa/symbios/RAIDCore-5207.1.7/m4_874_debian-5207.1.7/images/m4_e30_874_3000-08.74.02.00/eos/Application/RAIDLib/evfVolume.h, line 2520

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.