Skip to main content
NetApp Knowledge Base

CONTAP-95894: Replacement internal NVMe drive getting duplicate clustershell ID after replacement

  1. Last updated
  2. Save as PDF
Views:
3
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Issue

Replacing a broken internal NVMe drive might cause a duplicate disk names error.
The new disk still shows as broken, as well as "unassigned" from cluster CLI outputs.
Example:
node::*> storage disk show -disk 1.0.15 -fields container-type,container-name,serial-number,model,type
disk container-type container-name model serial-number type
------ -------------- -------------- ---------------- -------------- -------
1.0.15 unassigned - X4010S172B1T9NTE 12121212121212121 SSD-NVM
Partition Size Type Name Owner
------------------------- ------- ------------- ----------------- -----------------
1.0.15.P1 882.4GB broken - node-01
1.0.15.P2 - unknown - node-02
1.0.15.P3 23.39GB broken - node-01

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.