Skip to main content
NetApp Knowledge Base

"Entering FM state:5" due to misconfigured bootarg.storageencryption.support

  1. Last updated
  2. Save as PDF
Views:
678
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • AFF Models
  • FAS Models
  • ONTAP 9
  • FIPS or SED Drives

Issue

  • After hardware maintenance, node reports the following:

[localhost:disk.encryptNoSupport:ALERT]: Detected FIPS-certified encrypting drive 0n.4, but FIPS drives are not supported on this node. 48 of 48 disks checked are FIPS-certified.

or

Dec 01 14:34:15 [localhost:disk.encryptNoSupport:error]: Detected FIPS-certified encrypting disk 0b.00.3, but bootarg.storageencryption.support indicates that FIPS disks should not be present. 24 of 24 disks checked are FIPS disks.
 

  • The node continues to produce the following errors at waiting for giveback:
Waiting for giveback...(Press Ctrl-C to abort wait)Entering FM state:5 because mbFound:0 local in headswap:0
Entering FM state:5 because mbFound:0 local in headswap:0
Entering FM state:5 because mbFound:0 local in headswap:0
Entering FM state:5 because mbFound:0 local in headswap:0
Entering FM state:5 because mbFound:0 local in headswap:0
 
  • The cluster reports the following:
Cluster1::> storage failover show
Takeover
Node           Partner        Possible State Description
-------------- -------------- -------- -------------------------------------
Cluster1-01    Cluster1-02    -        Kernel loaded
Cluster1-02    Cluster1-01    false    In takeover
2 entries were displayed.
 

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.