Skip to main content
NetApp Knowledge Base

FAS or AFF controller fails to boot with error "Detected nonencrypting drive or non-FIPS-certified drive xx.xx.x"

Views:
1,353
Visibility:
Public
Votes:
1
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS/AFF
  • ONTAP 9

Issue

  • The impaired node has been taken over by the partner node.
  • Hardware has been replaced or maintenance was performed on the impaired node.
  • The following errors seen during the boot.

Example:

May 24 16:11:38 [localhost:disk.encryptSupportReqd:ALERT]: Detected nonencrypting drive or non-FIPS-certified drive 9c.11.0, but only FIPS-certified drives are supported on this node. 0 of 48 drives checked are FIPS-certified.

May 24 16:11:38 [localhost:diskown.errorDuringIO:error]: error 3 (disk failed) on disk 58CE38EE:206EAC68:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000 (S/N N/A) while opening disk

 

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.

 

  • Was this article helpful?