Search

Error: Failed to add disks to aggregate "aggr_name". Reason: entry doesn't exist
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Error__Failed_to_add_disks_to_aggregate_aggr_name_Reason__entry_doesn_t_exist
Adding drives to an existing aggregate return an error: ::> storage aggregate add-disks -aggregate aggr_name -diskcount 2 -simulate true Error: Failed to add disks to aggregate "aggr_name". Reason: en...Adding drives to an existing aggregate return an error: ::> storage aggregate add-disks -aggregate aggr_name -diskcount 2 -simulate true Error: Failed to add disks to aggregate "aggr_name". Reason: entry doesn't exist. >>> data 0b.00.16P2 0b 0 8 SA:B 0 SSD N/A 425785/872008704 425793/872025088 >>> data 0b.00.16P1 0b 0 8 SA:A 0 SSD N/A 425785/872008704 425793/872025088 >>> data 0b.00.17P1 0b 0 9 SA:A 0 SSD N/A 425785/872008704 425793/872025088
How does NetApp ensure the integrity of data on returned disks?
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_does_NetApp_ensure_the_integrity_of_data_on_returned_disks
Disk Drives While handling Return Merchandise Authorization (RMA) disks: NetApp has established procedures for the management of Hard Disk Drives returned through the RMA process from the point of shi...Disk Drives While handling Return Merchandise Authorization (RMA) disks: NetApp has established procedures for the management of Hard Disk Drives returned through the RMA process from the point of shipment through testing, overwriting, and final disposition. At no point in this process do any NetApp or NetApp-contracted personnel access customer data residing on a returned drive. For more information regarding this process, refer to the Hard Disk Drive RMA & Data Overwriting Process page.
How long does it approximately take for disk zeroing?
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_long_does_it_approximately_take_for_disk_zeroing
Applies to Disk Drives Answer Disk zeroing time varies according to the disk manufacturers; however, the following table is a guideline for the estimated disk zeroing time: Estimated Disk Zeroing Time...Applies to Disk Drives Answer Disk zeroing time varies according to the disk manufacturers; however, the following table is a guideline for the estimated disk zeroing time: Estimated Disk Zeroing Time Capacity Type Estimated Zeroing Time (hrs) 1.6TB 3.8TB 7.6TB 15.3TB 30.6TB 300GB 15k rpm 450GB 10k rpm 600GB 1.2TB 1.8TB SATA/ NL-SAS 7.2k rpm Note: These times are guidelines and will vary based on the load of the storage system. The fast-zeroing was introduced in ONTAP 9.4. Additional Information
X477A-R6 disk drive mislabeled as part number: X4477A-R6 on physical disk label
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/X477A_R6_disk_drive_mislabeled_as_part_number__X4477A_R6_on_physical_disk_label
Disk drive with part number: X477A-R6 Part number mismatch might be seen on the physical label of few drives. Disk is seen with part number X4477A-R6 instead of X477A-R6. ONTAP recognizes these drives...Disk drive with part number: X477A-R6 Part number mismatch might be seen on the physical label of few drives. Disk is seen with part number X4477A-R6 instead of X477A-R6. ONTAP recognizes these drives correctly and the drives are fully operational. This is only a labeling error and the quantity of the mislabeled disks released is unknown. Here is a potential list of affected disk drives: Drive Part Number Model Number HDD, 4.0TB, 7.2K, SAS HDD,4.0TB,7.2K,SAS HDD,4.0TB,7.2K,NL-SAS
When should a drive be failed (rebuild) versus letting it fail gracefully (sick disk copy)?
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/When_should_a_drive_be_failed_rebuild_versus_letting_it_fail_gracefully_sick_disk_copy
Are errors in the system log because of a bad disk? Should a drive be failed manually or let it fail gracefully?
How do disk firmware updates run on AltaVault
https://kb.netapp.com/Legacy/AltaVault/How_do_disk_firmware_updates_run_on_AltaVault
In AltaVault releases starting March 1st 2017, a firmware NA01 will be applied to the 4TB drive in AltaVault 400 and 6TB drive in AltaVault 800 when the system boots new releases. When a disk with fir...In AltaVault releases starting March 1st 2017, a firmware NA01 will be applied to the 4TB drive in AltaVault 400 and 6TB drive in AltaVault 800 when the system boots new releases. When a disk with firmware NA01 is inserted into an AltaVault appliance that has NA00 in the system OS image, the disk inserted will remain at firmware NA01. The AltaVault Installation Guide for Physical Appliance for each release documents the steps to configure and connect to the service processor .
System is at high risk of unexpected behavior if dynamically qualified drives are detected
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/System_is_at_high_risk_of_unexpected_behavior_if_dynamically_qualified_drives_are_detected
In certain scenarios resources like Hardware Universe or the disk fw download page will show a current version of ONTAP as supported with a drive type however the following symptoms could be seen: Dri...In certain scenarios resources like Hardware Universe or the disk fw download page will show a current version of ONTAP as supported with a drive type however the following symptoms could be seen: Drives not being partitioned appropriately and used as spares to replace failing data drive partitions Drives marked as "dynamically qualified: yes" when reviewed via the (7-mode or nodeshell) storage show disk or (cluster) storage disk show -error-type qualfail commands.
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
OCUM reports weekly on Sunday a high disk utilization on root aggregate and shm.threshold.highIOLatency errors in one node
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/OCUM_reports_weekly_on_Sunday_a_high_disk_utilization_on_root_aggregate_and_shm.threshold.highIOLatency_errors_in_one_node
The drive is the data one in a 3 RAID-DP root aggregate Sun Apr 12 00:18:18 CEST [node_name: disk_latency_monitor: shm.threshold.highIOLatency:error]: Disk 0a.00.8 exceeds the average IO latency thres...The drive is the data one in a 3 RAID-DP root aggregate Sun Apr 12 00:18:18 CEST [node_name: disk_latency_monitor: shm.threshold.highIOLatency:error]: Disk 0a.00.8 exceeds the average IO latency threshold and will be recommended for failure. Wed Apr 22 18:21:48 CEST [node_name: disk_latency_monitor: shm.threshold.ioLatency:debug]: Disk 0a.00.8 has exceeded the expected IO latency in the current window with average latency of 182 msecs and average utilization of 28 percent.
How to assign a disk to a system while in HA takeover
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_assign_a_disk_to_a_system_while_in_HA_takeover
Applies to ONTAP 9 Description The article describes how to properly assign a disk to a node while it has been taken over by its partner
AFF and FAS series Disk amber LED ON with no fault observed
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/AFF_and_FAS_series_Disk_amber_LED_ON_with_no_fault_observed
Applies to All disk drive models Drives that have failed, or are about to fail Issue Amber LED on for disk drive with no immediate fault observed May also occur following a reboot (Takeover / Giveback...Applies to All disk drive models Drives that have failed, or are about to fail Issue Amber LED on for disk drive with no immediate fault observed May also occur following a reboot (Takeover / Giveback)