Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 9 results
    • Disk X316_HARIH06TA07 failing impacts system performance
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Disk_X316_HARIH06TA07_failing_impacts_system_performance
      [node01: disk_latency_monitor: shm.threshold.ioLatency:debug]: Disk 9a.02.4 has exceeded the expected IO latency in the current window with average latency of 72 msecs and average utilization of 85 pe...[node01: disk_latency_monitor: shm.threshold.ioLatency:debug]: Disk 9a.02.4 has exceeded the expected IO latency in the current window with average latency of 72 msecs and average utilization of 85 percent. [node01: disk_latency_monitor: shm.threshold.ioLatency:debug]: Disk 9a.02.4 has exceeded the expected IO latency in the current window with average latency of 120 msecs and average utilization of 92 percent.
    • How to check disk health on Altavault
      https://kb.netapp.com/Legacy/AltaVault/How_to_check_disk_health_on_Altavault
      Applies to Altavault Description How to check disk health on Altavault
    • FlexArray controller reboot after disk failure on E-Series back-end
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FlexArray_controller_reboot_after_disk_failure_on_E-Series_back-end
      Applies to FlexArray/V-Series E-Series ONTAP 9 Issue FAS controller reboots after disk failure on E-Series back-end.
    • What caused the plex to fail and how was the disk replaced?
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/What_caused_the_plex_to_fail_and_how_was_the_disk_replaced
      8/11/2022 19:00:02 node-02 ERROR diskown.errorDuringIO: error 3 (disk failed) on disk 0b.26 (S/N disk1) while reading entire disk ownership area 8/11/2022 18:55:13 node-01 ERROR raid.config.filesystem...8/11/2022 19:00:02 node-02 ERROR diskown.errorDuringIO: error 3 (disk failed) on disk 0b.26 (S/N disk1) while reading entire disk ownership area 8/11/2022 18:55:13 node-01 ERROR raid.config.filesystem.disk.failed: File system Disk /aggr1/plex1/rg0/0d.30 S/N [disk1] UID [disk1] failed. Disk 0d.30 S/N [disk1] UID [disk1] was unfailed, and is now being reassimilated
    • SANtricity host performance degradation due to marginal drive
      https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/SANtricity_host_performance_degradation_due_to_marginal_drive
      The major event log (MEL) found in Support bundle and AutoSupport reports the following event: Timeout on drive side of controller. A:8/7/22, 6:51:31 AM (06:51:31) 9300 100d Timeout on drive side of c...The major event log (MEL) found in Support bundle and AutoSupport reports the following event: Timeout on drive side of controller. A:8/7/22, 6:51:31 AM (06:51:31) 9300 100d Timeout on drive side of controller - Shelf 99, Bay 2 A:8/7/22, 6:51:27 AM (06:51:27) 9299 100d Timeout on drive side of controller - Shelf 99, Bay 2 A:8/7/22, 6:51:24 AM (06:51:24) 9298 100d Timeout on drive side of controller - Shelf 99, Bay 2
    • Aggregate degraded as one disk is offline due to a failure
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Aggregate_degraded_as_one_disk_is_offline_due_to_a_failure
      [node_name: config_thread: raid.disk.assign.offline_ref:debug]: aggregate /data_aggregate/plex0/rg0/0a.01.1 assigned as an offline reference storage for /data_aggregate/plex0/rg0/0a.01.5. [node_name: ...[node_name: config_thread: raid.disk.assign.offline_ref:debug]: aggregate /data_aggregate/plex0/rg0/0a.01.1 assigned as an offline reference storage for /data_aggregate/plex0/rg0/0a.01.5. [node_name: config_thread: raid.disk.assign.offline_ref:debug]: aggregate /data_aggregate/plex0/rg0/0a.01.3 assigned as an offline reference storage for /data_aggregate/plex0/rg0/0a.01.5.
    • The failure rate for disks with odd numbers in the same shelf is high
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/The_failure_rate_for_disks_with_odd_numbers_in_the_same_shelf_is_high
      Sat Oct 26 18:47:30 +0900 [node2: disk_server_1: shm.threshold.consecutiveTimeouts:error]: shm: Disk 0a.10.1 has exceeded the threshold of 11 consecutive timeouts; the system will fail the disk if pos...Sat Oct 26 18:47:30 +0900 [node2: disk_server_1: shm.threshold.consecutiveTimeouts:error]: shm: Disk 0a.10.1 has exceeded the threshold of 11 consecutive timeouts; the system will fail the disk if possible. Sat Nov 09 19:13:17 +0900 [node2: disk_server_1: shm.threshold.consecutiveTimeouts:error]: shm: Disk 0a.10.9 has exceeded the threshold of 11 consecutive timeouts; the system will fail the disk if possible.
    • Disk detected in sysconfig-a but FAILED in sysconfig-r after replacement
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Disk_detected_in_sysconfig-a_but_FAILED_in_sysconfig-r_after_replacement
      Disk Qualification Package (DQP) Disk failed and replaced. Listed in sysconfig -a output. The replaced disk is listed as spare and not replaced in the RAID group. RAID group /aggr4/plex0/rg0 (normal, ...Disk Qualification Package (DQP) Disk failed and replaced. Listed in sysconfig -a output. The replaced disk is listed as spare and not replaced in the RAID group. RAID group /aggr4/plex0/rg0 (normal, block checksums) RAID group /aggr4/plex0/rg1 (degraded, block checksums) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) data FAILED N/A 7486157/ - Disk Qualification Package Details: Package Date: Unable to load any package (Package version not supported)
    • HA Group Notification (FILESYSTEM DISK FAILED Shelf XX, Bay YY, Model ...) ERROR
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/HA_Group_Notification_FILESYSTEM_DISK_FAILED_Shelf_XX_Bay_YY_Model_ERROR
      AutoSupport reports a failed disk: HA Group Notification (FILESYSTEM DISK FAILED Shelf XX, Bay YY, Model ...) ERROR. This is caused by faulty disk.