The state data was not saved following a power loss.
Explanation
On startup, the node was unable to read its state
data. When this happens, it expects to be automatically added back
into a cluster. However, if it has not joined a cluster in 60 sec,
it raises this node error. This is a critical node error, and user
action is required before the node can become a candidate to join
a cluster.
User response
Follow troubleshooting procedures to correct connectivity
issues between the cluster nodes and the quorum devices.
- Manual intervention is required once the node reports this error.
- Attempt to reestablish the cluster using other nodes. This may
involve fixing hardware issues on other nodes or fixing connectivity
issues between nodes.
- If you are able to reestablish the cluster, remove
the cluster data from the node showing 578 so it goes to candidate
state, it will then be automatically added back to the cluster.
- To remove the cluster data from the node, either go to the service
assistant, select the radio button for the node with a 578, click Manage
System, then choose Remove System Data.
- Or use the CLI to satask leavecluster.
If the node does not automatically add back to the cluster,
note the name and I/O group of the node, then delete the node from
the cluster configuration (if this has not already happened) and then
add the node back to the cluster using the same name and I/O group.
- If all nodes have either node error 578 or 550, follow the cluster
recovery procedures.
- Attempt to determine what caused the nodes to shut down.
Possible Cause—FRUs or other: