Skip to main content
NetApp Knowledge Base

Disk Inventory Mismatch and Failed-Unsupported Disks on Single node

  1. Last updated
  2. Save as PDF
Views:
101
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

  ↵

Applies to

  • FAS and AFF systems
  • ONTAP 9.7
  • Disk Qualification Package (DQP)  file is not installed

Issue

  • The node reports multiple cf.disk.inventory.mismatch errors.
Source:：svc_queue_thread
Event：cf.disk.invent.mismatchalt: Status of some of the disks has changed or the node (***) is missing 12 disks (detailed logs have been throttled).
Description：This message occurs when one of the nodes in a high-availability (HA) pair reports that multiple disks in the disk inventory do not match what the partner node reported. This only occurs when sufficient mismatches have occurred to throttle the specific disk inventory mismatch message. 
The issue might be due to one of following reasons: (1) One node can see disks that the other node cannot. (2) Ownership of multiple disks has changed. (3) Multiple disks have been failed or unfailed. (4) Multiple disks have been inserted or removed.
Operation：Rescan the disks on both nodes in the HA pair to determine the latest ownership by using the "storage disk refresh-ownership" command. If the inventory mismatch is not resolved, remove and replace any failed disks. If there are no failed disks, check the cabling for loose connections or a bad cable on the node where the disks are not included in the inventory.
  • Disks on port 0b of the node are displayed as Failed-Unsupported.
  00.6 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XH01)
  00.7 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VKTA)
  SHJSG2030000039.0:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.8 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3YEW0)
  SHJSG2030000039.1:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.9 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VJL5)
  SHJSG2030000039.2:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.10: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XH40)
  SHJSG2030000039.3:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.11: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XH3A)
  SHJSG2030000039.4:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.12: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3YDM0)
  SHJSG2030000039.5:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.13: NETAPP   X343_TA15E1T8A10 NA00 1713.5GB 520B/sect (1130A0P1F4UR)
  SHJSG2030000039.6:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.14: NETAPP   X343_TA15E1T8A10 NA01 1713.5GB 520B/sect (Z1C0A04JF4VR)　　
  SHJSG2030000039.7:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.15: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VKDK)　
  SHJSG2030000039.8:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.16: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VKMB)
  SHJSG2030000039.9:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.17: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XGP7)
  SHJSG2030000039.10:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.18: NETAPP   X343_SSKBE1T8A10 NA04 1713.5GB 520B/sect (WBN6TNQ5)
  SHJSG2030000039.11:                                  0.0GB 0B/sect (Failed-Unsupported)
  00.19: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VK2G)
  
  • The same disks are correctly recognized and operational on the partner node.

00.6 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XH01)
00.7 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VKTA)
SHJSG2030000039.0: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60L0A0RTF9XC)
00.8 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3YEW0)
SHJSG2030000039.1: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60L0A0RSF9XC)
00.9 : NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VJL5)
SHJSG2030000039.2: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60L0A0T6F9XC)
00.10: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XH40)
SHJSG2030000039.3: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60L0A0SYF9XC)
00.11: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XH3A)
SHJSG2030000039.4: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60M0A0WEF9XC)
00.12: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3YDM0)
SHJSG2030000039.5: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60L0A0SEF9XC)
00.13: NETAPP   X343_TA15E1T8A10 NA00 1713.5GB 520B/sect (1130A0P1F4UR)
SHJSG2030000039.6: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60L0A0SLF9XC)
00.14: NETAPP   X343_TA15E1T8A10 NA01 1713.5GB 520B/sect (Z1C0A04JF4VR)
SHJSG2030000039.7: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60M0A0W7F9XC)
00.15: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VKDK)
SHJSG2030000039.8: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60M0A0W6F9XC)
00.16: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VKMB)
SHJSG2030000039.9: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60M0A0YQF9XC)
00.17: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3XGP7)
SHJSG2030000039.10: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60M0A0WFF9XC)
00.18: NETAPP   X343_SSKBE1T8A10 NA04 1713.5GB 520B/sect (WBN6TNQ5)
SHJSG2030000039.11: NETAPP   X336_TTCRE04TA07 NA03 3807.8GB 520B/sect (60M0A0WCF9XC)
00.19: NETAPP   X343_SSKBE1T8A10 NA02 1713.5GB 520B/sect (WBN3VK2G)

  • Disk and Module failures may be seen during boot

Mar 15 15:44:07 [Node-06:scsi.cmd.pastTimeToLive:error]: Unknown device 5a.33.99: request failed after try #1: cdb 0x12.
Mar 15 15:45:25 [Node-06:scsi.cmd.excessiveVictim:error]: device 5a.31.23: excessive victim abort: delta time 99386: retry CDB 0x28:00000008:0008: victim retry count 100: retry count 0: timeout retry count 0: path retry count 0: adapter status 0x5: target status 0x0: sense data SCSI:no sense -  (0x0 - 0x0 0x0 ).
Mar 15 15:45:46 [Node-06:scsi.cmd.pastTimeToLive:error]: Disk device 5a.31.0: request failed after try #1: cdb 0x28:00000008:0008.

  • This can pause an ANDU due to the failed giveback

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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 techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.