Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 15 results
    • Does ONTAP allow mixing of drive sizes in a RAID group?
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Does_Data_ONTAP_allow_mixing_of_drive_sizes_in_a_RAID_group
      When adding larger drives to an existing RAID group of smaller drives, the larger drives will be right sized to match the usable capacity of the smaller drives. Adding a 10TB NL-SAS drive to an existi...When adding larger drives to an existing RAID group of smaller drives, the larger drives will be right sized to match the usable capacity of the smaller drives. Adding a 10TB NL-SAS drive to an existing RAID group of 4TB drives results in usable capacity of 3.63TB on the 10TB drive. If the right sized drive has partitions, follow How to replace a file system partition with a spare partition to move to a partition on a spare that is the correct size
    • Why RAID parity inconsistencies are reported
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Why_RAID_parity_inconsistencies_are_reported
      Applies to ONTAP 9 Clustered Data ONTAP 8 Data ONTAP 8 Issue RAID parity inconsistencies are reported Sun Sep 12 02:07:23 IST [raid.rg.scrub.pi:error]: Inconsistent parity on RAID group /aggr1/plex0/r...Applies to ONTAP 9 Clustered Data ONTAP 8 Data ONTAP 8 Issue RAID parity inconsistencies are reported Sun Sep 12 02:07:23 IST [raid.rg.scrub.pi:error]: Inconsistent parity on RAID group /aggr1/plex0/rg0, stripe #10000.
    • A raid group in aggregate is degraded but not offline
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/A_raid_group_in_aggregate_is_degraded_but_not_offline
      RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- parity switch2:8.217L2 1c 20 7 FC:B 1 S...RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- parity switch2:8.217L2 1c 20 7 FC:B 1 SSD N/A 915465/1874872832 915715/1875385008 data switch4:8.217L3 1a 20 6 FC:A 1 SSD N/A 915465/1874872832 915715/1875385008 (offline)
    • Why are new plexes named plex2, plex5.. Why not plex 1 or 0?
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/Why_are_new_plexes_named_plex2_plex5_Why_not_plex_1_or_0
      ​ Applies to ONTAP 9 NetApp ONTAP Select NetApp SyncMirror Answer This is by design. The only requirement is that two plexes have different names. By default, we will get plex0 and plex1. They k...​ Applies to ONTAP 9 NetApp ONTAP Select NetApp SyncMirror Answer This is by design. The only requirement is that two plexes have different names. By default, we will get plex0 and plex1. They keep incrementing when plexes are destroyed and then re-created. Additional Information
    • NVRAM purpose during ONTAP outage
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/NVRAM_purpose_during_ONTAP_outage
      This data is checked for and when found, is replayed to the local memory buffer and immediately re-processed through the WAFL and RAID layers and written to disk during the next CP. Since all write da...This data is checked for and when found, is replayed to the local memory buffer and immediately re-processed through the WAFL and RAID layers and written to disk during the next CP. Since all write data for one node is also stored in the partner controller’s NVRAM, when the takeover occurs and the downed node boots virtually, all the writes that had been acknowledged are available for it to replay to its memory buffer and process through WAFL and RAID layers and then written to disk.
    • How to stop coredump.findcore.nocore from spamming EMS
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_stop_coredump.findcore.nocore_from_spamming_EMS
      Sun May 03 10:45:51 -0600 [CLUSTER: coredump_manager: ems.engine.suppressed:debug]: Event 'coredump.findcore.nocore' suppressed 7 times in last 722 seconds. Sun May 03 10:45:51 -0600 [CLUSTER: coredum...Sun May 03 10:45:51 -0600 [CLUSTER: coredump_manager: ems.engine.suppressed:debug]: Event 'coredump.findcore.nocore' suppressed 7 times in last 722 seconds. Sun May 03 10:45:51 -0600 [CLUSTER: coredump_manager: coredump.findcore.nocore:debug]: No unsaved cores could be found Sun May 03 10:57:53 -0600 [CLUSTER: coredump_manager: ems.engine.suppressed:debug]: Event 'coredump.findcore.nocore' suppressed 7 times in last 722 seconds.
    • What sparing criteria does the 'Low number of spare disks' healthcheck use?
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_sparing_criteria_does_the_Low_number_of_spare_disks_healthcheck_use
      The default value for the raid.disktype.enable option is off, which allows the mixing of disk types. What this means is that the following disk types are considered to be equivalent for the purposes o...The default value for the raid.disktype.enable option is off, which allows the mixing of disk types. What this means is that the following disk types are considered to be equivalent for the purposes of creating and adding to aggregates, and spare management: With the option raid.disktype.enable on or raid.mix.hdd.disktype off, they disable the mixing of supported drive types. For SSDs, the requirements are: 1 full spare SSD OR 1 spare partition for each partition in use on that node
    • ONTAP Deploy VM hung with Error "Probing EDD"
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/ONTAP_Deploy_VM_hung_with_Error_Probing_EDD
      Applies to ONTAP Select Deploy VM 2.7 Issue When you reboot a previously working ONTAPdeploy VM the boot screen hangs at a message Probing EDD (edd=off to disable)… ok . Multiple reboots of the VM han...Applies to ONTAP Select Deploy VM 2.7 Issue When you reboot a previously working ONTAPdeploy VM the boot screen hangs at a message Probing EDD (edd=off to disable)… ok . Multiple reboots of the VM hang at the same position.
    • How ONTAP Select capacity license is being calculated with partitions and non-zero raid configuration
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/How_ONTAP_Select_capacity_license_is_being_calculated_with_partitions_and_non-zero_raid_configuration
      Use license show-status -license select command to review information about the current capacity license usage The sum of partitions usable-size (excluding the parity partitions) is the capacity licen...Use license show-status -license select command to review information about the current capacity license usage The sum of partitions usable-size (excluding the parity partitions) is the capacity license that is being presented in license show-status command. In the above example, we have 2 parity disks & 5 data disks of 700GB, which is 3.5TB and therefore the license is calculated as: Currently using 3.5TB.
    • After added new shelf unable to add all disks to aggregate
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/After_added_new_shelf_unable_to_add_all_disks_to_aggregate
      Applies to ONTAP 9 Advanced Disk Partitioning (ADP) AFF A700 Issue After adding new shelf with 12 disks, only a few disks can be added to expand aggregate.
    • Protection relationship for FlexGroup fails: not enough space on valid aggregates
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Protection_relationship_for_FlexGroup_fails__not_enough_space_on_valid_aggregates
      Applies to ONTAP 9.4 and later SnapMirror NetApp ONTAP FlexGroup (FG) NetApp ONTAP System Manager Issue SnapMirror protect failed because of an unexpected internal error. Error: Failed to create FlexG...Applies to ONTAP 9.4 and later SnapMirror NetApp ONTAP FlexGroup (FG) NetApp ONTAP System Manager Issue SnapMirror protect failed because of an unexpected internal error. Error: Failed to create FlexGroup "svm1:fg1_dest". (Cannot create FlexGroup "fg1_dest" in Vserver "svm1" because there is not enough space on valid aggregates. The maximum number of constituents that can be added is x.)