"Entering FM state:5" after boot device replacement due to misconfigured bootarg.pegasus.nvmeof.storage_ports

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 833

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: hw

Last Updated:

Applies to

NS224 Shelves
ONTAP 9

Issue

After following the boot device replacement procedure for an AFF model, the node returns to a waiting for giveback state; however, the following message is seen continuously on the console.

After following the boot device replacement procedure for an AFF model, ONTAP fails to boot. The following message is seen continuously on the console:

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 Waiting for giveback...(Press Ctrl-C to abort wait) Waiting for giveback...(Press Ctrl-C to abort wait)Entering FM state:5 because mbFound:0 local in headswap:0 This node was previously declared dead. Pausing to check HA partner status ... lock was released, continuing boot ... WARNING: 0 disks found! WARNING: there do not appear to be any disks attached to the system. No root volume found. Rebooting... (press ctrl-c during boot to break reboot loop)

The command "disk show -v" produces the following:

*> disk show -v Local System ID: ******** disk show: No disks attached to system. *>

The command "storage port show" shows that the port status is disabled:

*> storage port show Port Type Speed(Gb/s) State Status VLAN ID Is Dedicated? --------------------------------------------------------------------------- e0c ENET 100 Gb/s disabled online 0 false e0d ENET 100 Gb/s disabled online 0 false e5a ENET 100 Gb/s disabled online 0 false e5b ENET 100 Gb/s disabled online 0 false

Entering FM state:5 because mbFound:0 local in headswap:0

Reviewing the output of storage failover show from the clustershell shows the state description as "Kernel loaded":

Takeover Node Partner Possible State Description -------------- -------------- -------- ------------------------------------- cluster1-01 cluster1-02 true Connected to cluster1-02 cluster1-02 cluster1-01 true Kernel loaded 2 entries were displayed.