How to upgrade and re-initialize FAS25xx, FAS22xx, and All-Flash FAS

platforms to use the Advanced Drive Partitioning feature in clustered

Data ONTAP 8.3

https://kb.netapp.com/Legacy/ONTAP/Clustered_Data_ONTAP_8/How_to_upgrade_and_re-initialize_F…
Updated: Mon, 15 Apr 2024 12:06:26 GMT

Applies to
• Clustered Data ONTAP 8.3
• FAS2000 series

Description

This article describes the procedure to be followed to upgrade the boot images on FAS25xx, FAS22xx, and All-

'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 1
techniques herein is a customers responsibility and depends on the customers ability to evaluate and integrate them into the customers operational
environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this
document.'
 Flash FAS (AFF) platforms from clustered Data ONTAP 8.2.x to Data ONTAP 8.3 and re-initialize the controllers
to use the Advanced Drive Partitioning feature in Data ONTAP 8.3.

Warning: The procedure described in this article is disruptive and erases all the data from the system. Do not
perform it if the system has data that still needs to be backed up. Backup or evacuate data off the system
prior to performing the procedure listed in this article.

Root-data partitioning for HDDs, which is one of the use cases of Advanced Drive Partitioning, is not available on
FAS8xxx, FAS62xx, and FAS32xx series controllers. Advanced Drive Partitioning is not supported for
MetroCluster configurations in Data ONTAP 8.3. For more details on supported FAS platforms for Data ONTAP
8.3, see the NetApp Hardware Universe.

Clustered Data ONTAP 8.2 systems consume three dedicated drives for the root aggregate. Root aggregates
are RAID-DP with one data disk, one parity disk, and one diagonal parity disk.

Clustered Data ONTAP 8.3 introduces the Advanced Drive Partitioning feature for FAS25xx, FAS22xx, and AFF
platforms. Using this feature, physical drives are partitioned into root and data partitions. The root partitions are
smaller partitions used to provision root aggregates, while the larger data partitions are used for provisioning
data aggregates.

Note: Upgrading the supported FAS systems to Data ONTAP 8.3 will not enable the Advanced Drive Partitioning
feature. To take advantage of this new feature, system disks have to be reinitialized.

Procedure

Perform the following steps to upgrade the entry-level and AFF platforms to enable the Advanced Drive
Partitioning feature in Data ONTAP 8.3.

Caution: If your entry-level FAS or AFF system shipped from the factory with Data ONTAP 8.3 or later, do
NOT perform this procedure. Advanced Drive Partitioning will already be configured on the system.

Before you begin, obtain the desired Data ONTAP software images from the NetApp Support Site.

1. Power on the controllers. If the controllers are running clustered Data ONTAP 8.2.x images and are factory
fresh, then they will boot into a default cluster setup wizard:
Welcome to the cluster setup wizard.

You can enter the following commands at any time:

"help" or "?" - if you want to have a question clarified,
"back" - if you want to change previously answered questions, and
"exit" or "quit" - if you want to quit the cluster setup wizard.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 2
 Any changes you made before quitting will be saved.

You can return to cluster setup at any time by typing "cluster setup".
To accept a default or omit a question, do not enter a value.

Do you want to create a new cluster or join an existing cluster? {create,

join}:
2. Press Ctrl+C to exit the cluster setup wizard.

3. Log into the controllers using cluster administrator credentials.

Note: For factory-fresh raw controllers, the "admin" password is left blank. The password for the cluster
administrator is set during cluster configuration.
Sat Nov 22 03:24:21 UTC 2014
login: admin
******************************************************
* This is a serial console session. Output from this *
* session is mirrored on the SP console session. *
******************************************************
NodeA::>
4. Verify the existing Data ONTAP images running on the controllers:
NodeA::> system node image show
Is Is Install
Node Image Default Current Version Date
-------- ------- ------- ------- -------------------------
-------------------
localhost
image1 true true 8.2.2RC1 6/4/2014
10:31:10
image2 false false 8.2.2RC1 6/4/2014
10:31:34
2 entries were displayed.

5. Ensure that storage failover (HA) is disabled on the node.

NodeA::> storage failover modify –enabled false

6. Reboot Controller A. Carefully monitor the boot process and press Ctrl+C to display the boot menu:
NodeA::> system node reboot -node localhost
Warning: Are you sure you want to reboot the node? {y|n}: y
login: Terminated
.
Uptime: 12h50m0s
Rebooting...
Terminated
.
Uptime: 1m22s

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 3
 System rebooting...
BIOS version: 9.1.1

7. From the boot menu, select the boot option (7) – Install new software first:
Please choose one of the following:
(1) Normal Boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 7

8. Type "y" after the warning message for a disruptive upgrade procedure:
This procedure is not supported for Non-Disruptive Upgrade on an HA pair.
The software will be installed to the alternate image, from which the node
is
not currently running. Do you want to continue? {y|n} y
9. Select a network interface that is connected to the network and has access to the externally located web
(HTTP) server. Type "y" at the reboot prompt:
In order to download the package, a temporary network interface needs to be
configured.

Select the network port you want to use for the download (for example,
'e0a')
e0i

The node needs to reboot for this setting to take effect. Reboot now? {y|n}
(selecting yes will return you automatically to this install wizard) y

Rebooting...
Here are the permissions on /mroot directory:
drwxr-xr-x 3 root wheel 512 Apr 29 22:24 /mroot
/mroot directory doesn't exist or is it not writeable... aborting coverage
dump
Terminated
.
Uptime: 22m5s
System rebooting...
The node will reboot.

10. Configure IP address, netmask and gateway details for the selected interface:
In order to download the package, a temporary network interface needs to be

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 4
 configured.

Enter the IP address for port e0i: 192.168.100.24

Enter the netmask for port e0i: 255.255.255.0
Enter IP address of default gateway: 192.168.100.1
11. Enter the web server (HTTP) where the Data ONTAP 8.3 image is saved.
Input the username and password of the web server (if configured):
What is the URL for the package? http://<<webserver IP or FQDN>>/image.tgz
What is the user name on "<<webserver>>", if any?

Note: It is assumed that clustered Data ONTAP images are already downloaded from NetApp Support and
placed on a local Web server for upgrade. If DNS is not configured, use the IP address of the Web server
instead.

12. The installation will begin once the network link and route to the web server is established:
Checking network link... success.
Checking route to host "<<webserver>>"... success.
Attempting to reach <<webserver>>... success.
Looking up URL "http:// <<webserver IP or FQDN>>/image.tgz"... success.

Downloading package... success.

Checking package contents... success.
Extracting install script from package... success.
Invoking script (validation phase).
INSTALL running in check-only mode: the image will be validated only
Mode of operation is INSTALL
Current image is image2
Alternate image is image1
Using device /dev/da0 for install

13. Verify that installation was successfully completed by looking for the "Installation complete"
message at the end of the output messages:
Syncing device...
Extracting to /cfcard/x86_64/freebsd/image2...
x CHECKSUM
x VERSION
x COMPAT.TXT
x BUILD
x metadata.xml
x INSTALL
x netapp_sufficiency_lif_checker
x cap.xml
x platform.ko
x kernel
x fw.tgz
x platfs2g.img

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 5
 Installed MD5 checksums pass
Installing diagnostic and firmware files
Firmware MD5 checksums pass
Installation complete.
The controller will reboot automatically and will set the new image for Data ONTAP 8.3 as the current and
default image upon reboot.
The system will load the default node setup wizard after the boot is complete.
Welcome to node setup.

You can enter the following commands at any time:

"help" or "?" - if you want to have a question clarified,
"back" - if you want to change previously answered questions, and
"exit" or "quit" - if you want to quit the setup wizard.
Any changes you made before quitting will be saved.

To accept a default or omit a question, do not enter a value.

This system will send event messages and weekly reports to NetApp Technical
Support.
To disable this feature, enter "autosupport modify -support disable" within
24
hours.
Enabling AutoSupport can significantly speed problem determination and
resolution should a problem occur on your system.
For further information on AutoSupport, see:
http://support.netapp.com/autosupport/

Type yes to confirm and continue {YES}:

14. Exit the node setup wizard by pressing Ctrl+C:
Exiting the node setup wizard. Any changes you made have been saved.

Warning: You have exited the node setup wizard before completing all
of the tasks. The node is not configured. You can complete node setup by
typing
"node setup" in the command line interface.

Sat Nov 22 04:00:21 UTC 2014

login: admin
******************************************************
* This is a serial console session. Output from this *
* session is mirrored on the SP console session. *
******************************************************
::>

15. Follow Steps 1 through 14 on <NodeB> of the HA pair to upgrade the Data ONTAP images to 8.3.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 6
 16. Verify Data ONTAP 8.3 is set as default and current image on both the nodes in an HA pair.
::> system node image show
Is Is Install
Node Image Default Current Version Date
-------- ------- ------- ------- -------------------------
-------------------
localhost
image1 true true 8.3RC2 1/19/2015
10:07:46
image2 false false 8.2.2 10/30/2014
08:32:02
2 entries were displayed.

17. Reboot NodeA and NodeB. Monitor the boot process - Press Ctrl+C when prompted to display
the boot menu:
NodeA::> system node reboot -node localhost

Warning: Are you sure you want to reboot the node? {y|n}: y

login: Terminated
.
Uptime: 12h50m0s

Rebooting...
Terminated
.
Uptime: 1d7h44m36s
System rebooting...
BIOS version: 9.1.1

18. On both the nodes, from the boot menu, select the boot option (5) – Maintenance mode boot:
Please choose one of the following:
(1) Normal Boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 5

19. Respond with 'yes' to acknowledge the warning message and confirm the Maintenance mode boot.
In a High Availability configuration, you MUST ensure that the partner node
is (and remains) down, or that takeover is manually disabled on the partner

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 7
 node, because High Availability software is not started or fully enabled in
Maintenance mode.

FAILURE TO DO SO CAN RESULT IN YOUR FILESYSTEMS BEING DESTROYED

NOTE: It is okay to use 'show/status' sub-commands such as 'disk show or

aggr status' in Maintenance mode while the partner is up Continue with
boot? yes
20. Answer with 'yes' to confirm the Maintenance mode boot:
Please answer yes or no.
Continue with boot? yes
21. Display the current disk ownership of both nodes in the HA configuration:
NodeA*> disk show
NodeB*> disk show
Local System ID: 536900452
DISK OWNER POOL SERIAL NUMBER HOME DR
HOME
------------ ------------- ----- ------------- -------------
-------------
0b.01.4 node-02(536900452) Pool0 KXGNDPSR node-02(536900452)
0b.01.14 node-02(536900452) Pool0 KXGNK4KR node-02(536900452)
0b.01.22 node-02(536900452) Pool0 KXGJYSJR node-02(536900452)
0b.01.16 node-02(536900452) Pool0 KXGMYZGR node-02(536900452)
0b.01.6 node-02(536900452) Pool0 KXGMPGKR node-02(536900452)
0b.01.10 node-02(536900452) Pool0 KXGM7DAR node-02(536900452)
0b.01.12 node-02(536900452) Pool0 KXGNGWGR node-02(536900452)
0a.01.13 node-01(536900449) Pool0 KXGM44ZR node-01(536900449)
0b.01.20 node-02(536900452) Pool0 KXGMMTLR node-02(536900452)
0b.01.8 node-02(536900452) Pool0 KXGNL10R node-02(536900452)
0b.01.18 node-02(536900452) Pool0 KXGNSW4R node-02(536900452)
0b.01.0 node-02(536900452) Pool0 KXGMNB9R node-02(536900452)
0a.01.21 node-01(536900449) Pool0 KXGNT5PR node-01(536900449)
0a.01.23 node-01(536900449) Pool0 KXGNKDLR node-01(536900449)
0a.01.11 node-01(536900449) Pool0 KXGNM71R node-01(536900449)
0a.01.3 node-01(536900449) Pool0 KXGNLX9R node-01(536900449)
0a.01.7 node-01(536900449) Pool0 KXGNM2MR node-01(536900449)
0a.01.1 node-01(536900449) Pool0 KXGNMEYR node-01(536900449)
0a.01.15 node-01(536900449) Pool0 KXGNLMLR node-01(536900449)
0a.01.9 node-01(536900449) Pool0 KXGNL72R node-01(536900449)
0a.01.5 node-01(536900449) Pool0 KXGLAA7R node-01(536900449)
0a.01.19 node-01(536900449) Pool0 KXGKEMPR node-01(536900449)
0b.01.2 node-02(536900452) Pool0 KXGNA74R node-02(536900452)
0a.01.17 node-01(536900449) Pool0 KXGNG2AR node-01(536900449)
22. Remove disk ownership from both NodeA and NodeB:

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 8
 NodeA*> disk remove_ownership
All disks will have their ownership information removed.
For high availability (HA) configurations, the partner node must be down.
Do you wish to continue? y
Volumes must be taken offline. Are all impacted volumes offline(y/n)?? y

NodeB*> disk remove_ownership

All disks will have their ownership information removed.
For high availability (HA) configurations, the partner node must be down.
Do you wish to continue? y
Volumes must be taken offline. Are all impacted volumes offline(y/n)?? y
23. Verify that there are no disks owned by NodeA or NodeB:
NodeA*> disk show
Local System ID: 536900452

disk show: No disks match option show.

NodeB*> disk show

Local System ID: 536900673

disk show: No disks match option show.

24. Halt both controllers to the LOADER prompt with the "halt" command:
NodeA*> halt
NodeB*> halt

25. This step has been removed. There is no need to set bootargs to enable ADP.
26. Run the boot_ontap command from the LOADER prompt to the boot menu on Controller A only (keep
Controller B at the LOADER prompt for now).
Carefully monitor the boot process and press Ctrl+C to display the boot menu.
Select "(4) Clean configuration and initialize all disks" from the boot menu and press Enter:
*******************************
* *
* Press Ctrl-C for Boot Menu. *
* *
*******************************
^CBoot Menu will be available.

Please choose one of the following:

(1) Normal Boot.

(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 9
 (6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 4
27. Respond with "yes" to "Zero disks, reset config and install a new file system?":
Please answer yes or no

Zero disks, reset config and install a new file system?: y

This will erase all the data on the disks, are you sure?: y

Rebooting to finish wipeconfig request.

Skipped backing up /var file system to CF.
Terminated
.
Uptime: 11m11s
System rebooting...
28. The system will stop at the LOADER prompt, again. Boot Data ONTAP by running the boot_ontap
command. The system will start the wipeconfig procedure, assign the unowned drives, and then
autopartition the drives and assign those partitions to both Controllers A and B:
LOADER-A> boot_ontap
*******************************
* *
* Press Ctrl-C for Boot Menu. *
* *
*******************************
Wipe filer procedure requested.

29. Verify that the RAID auto partition message similar to "Successfully auto-partitioned 12 of
12 disks" is displayed in the console output.
Note: Once disk zeroing is completed, Controller A will automatically come back to the LOADER prompt.
Do not boot Data ONTAP until the partner node disks have been reinitialized.

30. Once disk zeroing has started on Controller A, repeat Steps 26 to 28 on Controller B to reinitialize it.
31. After initializing procedures complete on Controller B, reboot both controllers:
LOADER-A> boot_ontap
LOADER-B> boot_ontap

Loading X86_64/freebsd/image2/kernel:0x100000/7946496 0x894100/4206472

Entry at 0xffffffff80171230
Loading X86_64/freebsd/image2/platform.ko:0x1000000/1985879 0x11e5000/
288704 0x122b7c0/272656
Starting program at 0xffffffff80171230
NetApp Data ONTAP 8.3RC1
Copyright (C) 1992-2014 NetApp.
All rights reserved.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 10
 Checking boot device filesystem
** /dev/da0s1
** Phase 1 - Read and Compare FATs
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
66 files, 1175936 free (36748 clusters)
MARK FILE SYSTEM CLEAN? yes
MARKING FILE SYSTEM CLEAN
Retry #1 of 5: /sbin/fsck_msdosfs /dev/da0s1
Retry #2 of 5: /sbin/fsck_msdosfs /dev/da0s1
Repaired boot device filesystem
*******************************
* *
* Press Ctrl-C for Boot Menu. *
* *
*******************************
32. During the boot process, the systems will display the "ROOT VOLUME NOT WORKING PROPERLY:
RECOVERY REQUIRED" emergency warning messages. By default, the systems will boot into the node
setup wizard of Data ONTAP 8.3.
Note: The systems will now boot with a newly created skeleton root volume. Based on the data stored in
the bootflash and NVRAM, the node knows its identity. As the node previously had database data in its root
volume and this volume is now empty, the system will set a recovery flag and give a warning at boot:
Nov 23 20:20:43 [localhost:mgmtgwd.rootvol.recovery.new:EMERGENCY]: A new
root volume was detected. This node is not fully operational. Contact
technical support to obtain the root volume recovery procedures.
Nov 23 20:20:43 [localhost:callhome.root.vol.recovery.reqd:EMERGENCY]: Call
home for ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED.
***********************
** SYSTEM MESSAGES **
***********************

A new root volume was detected. This node is not fully operational. Contact
support personnel for the root volume recovery procedures.
Welcome to node setup.
You can enter the following commands at any time:
"help" or "?" - if you want to have a question clarified,
"back" - if you want to change previously answered questions, and
"exit" or "quit" - if you want to quit the setup wizard.
Any changes you made before quitting will be saved.

To accept a default or omit a question, do not enter a value.

This system will send event messages and weekly reports to NetApp Technical
Support.
To disable this feature, enter "autosupport modify -support disable" within

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 11
 24
hours.
Enabling AutoSupport can significantly speed problem determination and
resolution should a problem occur on your system.
For further information on AutoSupport, see:
http://support.netapp.com/autosupport/

Type yes to confirm and continue {YES}: yes

33. Halt both nodes to reset the recovery flag. At the LOADER prompt, clear the recovery flag and run
boot_ontap:
::> system node halt -node localhost

Warning: Are you sure you want to halt node "localhost"? {y|n}: y

login: Terminated
.
Uptime: 54m32s
System halting...

LOADER-A> unsetenv bootarg.init.boot_recovery

LOADER-A> boot_ontap

LOADER-B> unsetenv bootarg.init.boot_recovery

LOADER-B> boot_ontap

Note: The nodes should boot normally without the recovery warning this time. It will take a few seconds
boot logging finishes before the login prompt is visible, while the node is synchronizing the database.
The node setup wizard is displayed upon clean boot.
34. Follow the wizard to setup node-management IP and proceed with cluster setup using the System Setup
tool or cluster setup CLI.
Welcome to node setup.

You can enter the following commands at any time:

"help" or "?" - if you want to have a question clarified,
"back" - if you want to change previously answered questions, and
"exit" or "quit" - if you want to quit the setup wizard.
Any changes you made before quitting will be saved.

To accept a default or omit a question, do not enter a value.

This system will send event messages and weekly reports to NetApp Technical
Support.
To disable this feature, enter "autosupport modify -support disable" within
24
hours.
Enabling AutoSupport can significantly speed problem determination and

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 12
 resolution should a problem occur on your system.
For further information on AutoSupport, see:
http://support.netapp.com/autosupport/

Type yes to confirm and continue {YES}: yes

35. Verify root aggregates are utilizing the Advanced Drive Partitioning feature in entry and AFF platforms:
::> aggr show -instance
Warning: Only local entries can be displayed at this time.
Aggregate: aggr0
Checksum Style: block
Number Of Disks: 10
Mirror: false
Node: localhost
Disks for First Plex: localhost:0b.01.1,
localhost:0b.01.3,
localhost:0b.01.5,
localhost:0b.01.7,
localhost:0b.01.9,
localhost:0b.01.11,
localhost:0b.01.13,
localhost:0b.01.15,
localhost:0b.01.17,
localhost:0b.01.19
Disks for Mirrored Plex: -
Partitions for First Plex: -
partitions for Mirrored Plex: -
Free Space Reallocation: off
HA Policy: cfo

-Or-
36. Run sysconfig –r from the node shell to ensure root aggregate is created from smaller root partitions
and remaining data partitions are listed as spares.

::> node run local -command sysconfig -r

Aggregate aggr0 (online, raid_dp) (block checksums)

Plex /aggr0/plex0 (online, normal, active, pool0)
RAID group /aggr0/plex0/rg0 (normal, block checksums)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used
(MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- -----
-------------- --------------
dparity 0b.01.1P2 0b 1 1 SA:B 0 SAS 10000 55176/

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 13
 113000448 55184/113016832
parity 0b.01.3P2 0b 1 3 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.5P2 0b 1 5 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.7P2 0b 1 7 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.9P2 0b 1 9 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.11P2 0b 1 11 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.13P2 0b 1 13 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.15P2 0b 1 15 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.17P2 0b 1 17 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
data 0b.01.19P2 0b 1 19 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
Pool1 spare disks (empty)
Pool0 spare disks
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used
(MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- -----
-------------- --------------
Spare disks for block checksum
spare 0b.01.21P2 0b 1 21 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
spare 0b.01.23P2 0b 1 23 SA:B 0 SAS 10000 55176/
113000448 55184/113016832
spare 0b.01.1P1 0b 1 1 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.3P1 0b 1 3 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.5P1 0b 1 5 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.7P1 0b 1 7 SA:B 0 SAS 10000 801787/

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 14
 1642060800 801795/1642077184
spare 0b.01.9P1 0b 1 9 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.11P1 0b 1 11 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.13P1 0b 1 13 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.15P1 0b 1 15 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.17P1 0b 1 17 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.19P1 0b 1 19 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.21P1 0b 1 21 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184
spare 0b.01.23P1 0b 1 23 SA:B 0 SAS 10000 801787/
1642060800 801795/1642077184

Additional Information

Add your text here.

© 2023 NetApp.No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical,
including photocopying, recording, taping, or storage in an electronic retrieval system—without prior written permission of the copyright owner. For more
information, see Legal Notices. 15