Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 12 results
    • I/O timeout on NVMe drive triggers a node panic
      https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/I_O_timeout_on_NVMe_drive_triggers_a_node_panic
      2020-05-30T15:01:29.908585Z KUL01-SFCL01-H610S1-06 kernel: [3319602.993359] nvme nvme7: I/O 251 QID 5 timeout, aborting 2020-05-30T15:01:29.908599Z KUL01-SFCL01-H610S1-06 kernel: [3319602.993368] nvme...2020-05-30T15:01:29.908585Z KUL01-SFCL01-H610S1-06 kernel: [3319602.993359] nvme nvme7: I/O 251 QID 5 timeout, aborting 2020-05-30T15:01:29.908599Z KUL01-SFCL01-H610S1-06 kernel: [3319602.993368] nvme nvme7: I/O 808 QID 5 timeout, aborting 2020-05-30T15:01:29.908601Z KUL01-SFCL01-H610S1-06 kernel: [3319602.993374] nvme nvme7: I/O 76 QID 8 timeout, aborting 2020-05-30T15:01:29.908602Z KUL01-SFCL01-H610S1-06 kernel: [3319602.993377] nvme nvme7: I/O 79 QID 8 timeout, aborting
    • ONTAP Tools for VMware vSphere: NVMe/TCP datastores not listed in datastores report
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/ONTAP_Tools_for_VMware_vSphere%3A_NVMe_TCP_datastores_not_listed_in_datastores_report
      In the OTV datastore report page, one or more NVMe/TCP datastores are missing from the list. The datastores are visible and accessible from within vSphere. The storage system backing the datastores is...In the OTV datastore report page, one or more NVMe/TCP datastores are missing from the list. The datastores are visible and accessible from within vSphere. The storage system backing the datastores is fully discovered in the OTV Storage Systems menu. To review this, SSH to the cluster and run the command vserver nvme namespace show -instance. Note the command output may be verbose depending on the number of namespaces in the environment.
    • NVMe I/O timeouts and SCSI errors in NS224 shelf
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/NVMeof_I_O_timeouts_and_SCSI_errors
      Latency issues in Consistency Points and SCSI errors detected from Virtual Machines hosts. Thu Dec 03 20:51:03 CET [node_name: intr: nvmeof.timeout:notice]: Timeout on subnqn nqn.2014-08.org.nvmexpres...Latency issues in Consistency Points and SCSI errors detected from Virtual Machines hosts. Thu Dec 03 20:51:03 CET [node_name: intr: nvmeof.timeout:notice]: Timeout on subnqn nqn.2014-08.org.nvmexpress.discovery, controller ID 5, qpair ID 0, sequence number 45417. Thu Dec 03 20:51:03 CET [node_name: intr: nvmeof.rdma.disconnect.status:notice]: NVMe-oF disconnect on subnqn nqn.2014-08.org.nvmexpress.discovery, controller ID 5, qpair ID 0.
    • How to convert vNVRAM disk driver from SCSI to vNVME
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/How_to_convert_vNVRAM_disk_driver_from_SCSI_to_vNVME
      Applies to NetApp ONTAP 9.5P2 and higher From version 9.5P10 ONTAP select uses a vNVME driver for vNVRAM. Using NVME over SCSI driver reduces the processing overhead This will be default configuration...Applies to NetApp ONTAP 9.5P2 and higher From version 9.5P10 ONTAP select uses a vNVME driver for vNVRAM. Using NVME over SCSI driver reduces the processing overhead This will be default configuration for new ONTAP Select installations on ONTAP 9.5P2 and higher Any select cluster upgraded from pre 9.5 will continue to use the SCSI driver For the clusters which are upgraded to 9.5 a manual procedure is required to use the vNVME controller for vNVRAM disk
    • E-Series installation NVMe LUN not visible
      https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_installation_NVMe_LUN_not_visible
      Applies to E-Series EF300 E-Series EF600 NVMe over Fibre channel (FC) Nonvolatile memory express (NVMe) Issue New storage installation and new host setup with NVMe drive type, a NVMe provisioned names...Applies to E-Series EF300 E-Series EF600 NVMe over Fibre channel (FC) Nonvolatile memory express (NVMe) Issue New storage installation and new host setup with NVMe drive type, a NVMe provisioned namespace is not visible to Host Setup documentation and setup poster is followed
    • Does ONTAP tools for VMware vSphere v10 support NVMe protocol?
      https://kb.netapp.com/data-mgmt/OTV/Does_ONTAP_tools_for_VMware_vSphere_v10_support_NVMe_protocol%3F
      Applies to ONTAP tools for VMware v10.x NetApp Storage Replication Adapter (SRA) VMware Site Recovery Manager (SRM) Answer At this time, NVMe support is not integrated within ONTAP tools for VMware vS...Applies to ONTAP tools for VMware v10.x NetApp Storage Replication Adapter (SRA) VMware Site Recovery Manager (SRM) Answer At this time, NVMe support is not integrated within ONTAP tools for VMware vSphere (OTV) v10.x When checking the Broadcom Compatibility Matrix, NetApp is not certified for NVMe with SRA: Broadcom Compatibility Guide NVMe support is on NetApp's roadmap for OTV 10 At this time, we do not have a target release date This article will be updated accordingly Additional Information
    • Writing certain file sizes fail in SAN with IO error
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Writing_certain_file_sizes_fail_in_SAN_with_IO_error
      Applies to Issue When sending specific sized (i.e 19K, 21K, 22K) payloads to write to a disk, the attempts will fail with an IO error. No error is observed within the host's event (syslog) log.
    • ESXi host does not see 4K block size SSD and NVMe datastore
      https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/ESXi_host_does_not_see_4K_block_size_SSD_and_NVMe_datastore
      Applies to NetApp E-Series EF-Series VMware ESXi 6.5 VMware ESXi 7.0 VMware ESXI 8.0 update 2 Issue Deployment using NVMe drives unable to detect LUN ESXi Datastore add unable to detect newly created ...Applies to NetApp E-Series EF-Series VMware ESXi 6.5 VMware ESXi 7.0 VMware ESXI 8.0 update 2 Issue Deployment using NVMe drives unable to detect LUN ESXi Datastore add unable to detect newly created LUN with E-Series volume configured with 4KB physical sector size (Block) Example: Storage Array Profile, Thick/Thin Volumes: Physical block size: 4,096 bytes Logical sector size: 4,096 bytes
    • RHEL host is unable to see it's provisioned NVMe namespace
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/RHEL_host_is_unable_to_see_it_s_provisioned_NVMe_namespace
      Applies to OnTap 9 RHEL 9.4 Issue When attempting to mount an NVMe namespace, the host cannot find its provisioned namespace.
    • What is the equivalent for "sas-expander-map" output to view port and path information for NVMe storage?
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_is_the_equivalent_for_sasstat_expander_map_command_for_NVMe_Over_Ethernet_to_view_port_and_path_information
      For the NS224 NVMe SSD shelves attached to AFF systems, there is no direct equivalent to show NVMe shelves and paths. The closest equivalent is to view disk path names to determine the connectivity be...For the NS224 NVMe SSD shelves attached to AFF systems, there is no direct equivalent to show NVMe shelves and paths. The closest equivalent is to view disk path names to determine the connectivity between AFF nodes and NS224 shelves. The primary path to the disk ​​​​​The node and node Ethernet storage port are listed under List of Path-Based Disk Names. Path ID maps to the Ethernet ports on the NSM100 modules in the NS224 shelf:
    • NVMe-tcp discovery fails with I/O error
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/NVMe-tcp_discovery_fails_with_I_O_error
      Applies to RHEL Ubuntu Linux/Unix based Host OS Issue NVMe discover fails with "Failed to write to /dev/nvme-fabrics: Input/output error" [root@host ~]# nvme discover --transport=tcp --traddr=ipaddres...Applies to RHEL Ubuntu Linux/Unix based Host OS Issue NVMe discover fails with "Failed to write to /dev/nvme-fabrics: Input/output error" [root@host ~]# nvme discover --transport=tcp --traddr=ipaddress --host-traddr=ipaddress Failed to write to /dev/nvme-fabrics: Input/output error