Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/E-Series_data_assurance_mismatch_reported_after_dynamic_volume_capacity_expansion
      Traditional RAID volume capacity expansion. E-Series storage array might report a combination of the below events during an expansion of a traditional RAID volume capacity. This may occur during the i...Traditional RAID volume capacity expansion. E-Series storage array might report a combination of the below events during an expansion of a traditional RAID volume capacity. This may occur during the immediate availability format of the newly expanded capacity. Event ID: 2062 Event Description: Data assurance mismatch detected - probable cause is data on drive Event Description: Unreadable sector(s) detected data loss occurred Event Description: Overflow in unreadable sector database
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E_Series_reboot_with_Panic_Reason__rebootReason_0x42e8001_rebootReasonExtra_0x0_while_performing_volume_expansion
      Thread 53 (Thread 0x7ff5b2506c00 (LWP 3209)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007ff5b23f753e in futex (val3=0, uaddr2=0x0, timeout=<optimized out>, val=0, futex_...Thread 53 (Thread 0x7ff5b2506c00 (LWP 3209)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007ff5b23f753e in futex (val3=0, uaddr2=0x0, timeout=<optimized out>, val=0, futex_op=128, uaddr=0x24b2b2370) at vkiSync.c:150 #2 _vkiCSemTake (semId=9851052912, tickTimeout=1250) at vkiSync.c:568 #3 0x00007ff59a721d5c in ras::RemotePeerManager::sendRemoteMessage (this=0x145c05670, response=0x7ff5b2505a80, target=0x145e998b0, targetId=10, msg=<optimized out>, msgLength=<optimized…
    • https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/FAQ__E_Series_ARVM_Mirror_Repositories_and_Initial_Sync
      Before each LBA region on the Secondary Mirror Volume is updated with data from the primary, the LBA is first copied into the Secondary Mirror Repository. If any errors occur during a sync, the snapsh...Before each LBA region on the Secondary Mirror Volume is updated with data from the primary, the LBA is first copied into the Secondary Mirror Repository. If any errors occur during a sync, the snapshot image can be used to 'roll-back' the Secondary Mirror Volume to the state in which it was, before the sync began. The increase capacity is achieved by using the free capacity that is available on the volume group of the standard volume or the snapshot repository volume.