Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Aggregate_offline_with_disk_missing_in_single_node_Cloud_Volumes_ONTAP_in_AWS
      12/9/2021 15:48:15 Your_AWS_node-01 ALERT sk.panic: Panic String: aggr aggr1: raid volfsm, fatal disk error in RAID group with no parity disk.. In this example, we can see only 5 disks for aggr1, alth...12/9/2021 15:48:15 Your_AWS_node-01 ALERT sk.panic: Panic String: aggr aggr1: raid volfsm, fatal disk error in RAID group with no parity disk.. In this example, we can see only 5 disks for aggr1, although we know from previous AutoSupports that there should be 6 disks in the aggregate: We can see in this example that disk NET-1.6 is missing when comparing the current disk show output to previous AutoSupports.
    • https://kb.netapp.com/Legacy/NetApp_HCI/OS/Can_a_single_compute_node_cluster_be_upgraded_with_HCC
      Hybrid Cloud Control (HCC) Cluster with single compute node Firmware (FW) upgrade using HCC No, you need at least 2 compute nodes in the cluster Workaround: install FW bundle manually Prerequisites fo...Hybrid Cloud Control (HCC) Cluster with single compute node Firmware (FW) upgrade using HCC No, you need at least 2 compute nodes in the cluster Workaround: install FW bundle manually Prerequisites for HCI installation: "The minimum cluster for NetApp HCI is two storage and two compute nodes." HCC upgrade will fails with: "No ESXi hosts are available. Make one or more ESXi host(s) in cluster available (not in maintenance mode) to migrate virtual machines and run the health check again."
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/ONTAP_update_for_single_node_cluster_via_CLI
      Applies to Data ONTAP 8 ONTAP 9 Description Updating ONTAP from CLI in a single node cluster
    • https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/Cluster_update_After_node_reboot__Update_is_not_in_paused_state
      After rebooting the machine, system boots with new image but update process seems to be running and not finished Running cluster image show-update-progress we see the upgrade in-progress or pause-pend...After rebooting the machine, system boots with new image but update process seems to be running and not finished Running cluster image show-update-progress we see the upgrade in-progress or pause-pending but never pauses or completes: Cluster Name: MCC02 Status: in-progress Error messages when trying to resume or pause the update process: Error: command failed: Update is not in "paused" state, so it cannot be resumed. Error: command failed: There is no update in progress to be paused