Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

What are the rules for Advanced Disk Partitioning?

Last Updated:

Applies to

  • Clustered Data ONTAP 8.3
  • ONTAP 9


The following rules are enforced automatically when Advanced Disk Partitioning for versions 1 & 2 as specified.

  • ADPv1 is only supported for HDD and ADPv2 is only supported for SSD disks.
  • Root partitions, P2 for ADPv1 or P3 for ADPv2; can only be used for the root aggregates. 
  • A RAID group cannot have more than one partition from the same disk (ADPv2).

Example:  for partitioned disk 0a.00.1, partitions 0a.00.1P1 and 0a.00.P2 can not be in the same RAID group.  They can be in different RAID groups of the same aggregate.

  • Partitioned and non-partitioned disks can be present together in the same aggregate, however, they must be in different RAID groups.
  • The only supported RAID type for aggregates containing root-data partitioned disks (ADPv1) is RAID-DP.  RAID4 is not supported.
  • The only supported RAID types for aggregates containing root-data-data partitioned disk (ADPv2) are RAID-TEC and RAID-DP.  RAID4 is not supported.
  • All Flash systems only support ADPv2.
  • For ADPv1, there must be (1) whole HDD available on each node of the HA pair.  The disk can be partitioned, but both partitions must be available as spares.
  • In default for ADPv1, owner of partitions are same as container; for ADPv2, owner of secondary data partition should be different with the root partition and primary data partition.
  • For AFF systems using ADPv2 require spares as shown

If all RAID groups are partitioned disks, with the same disk container type; (1) whole spare per HA is required.  The spare can be partitioned across the nodes.

If there is a mix of partitioned disk and non-partitioned disk RAID groups, then the requirement is (1) whole spare per node so that a spare is always available both for the partitioned RAID groups and the whole disk RAID groups.

  • ADPv1 initializes an HA pair with 24 HDD partitions; however, more partitions can be created after initialization
  • ADPv2 initializes an HA pair with 48 SSD partitions; however, more partitions can be created after initialization
  • For ADPv2, the minimum recommended same size or type to satisfy the hot spares/node requirements within ONTAP with Mixed Whole and Partitioned RAID Groups

Disk Count Number of spares required per node
1 - 100 1
101 - 400 2
401 - 600 3
601+ 4

Additional Information

  • The following example error message is reported when attempting to change the RAID type to an unsupported version:

cluster1::> aggr modify -aggregate aggr0 -raidtype raid4

Error: command failed: Failed to modify raidtype of aggregate "aggr0".
Reason: Change to raidtype RAID4 is not supported. Fields that were successfully modified: none

  • NetApp Hardware Universe contains extensive information for each supported platform on initial partition sizes for each supported disk type.
Scan to view the article on your device