IBM Storwize V7000 Troubleshooting And Maintenance Manual page 165

Possible Cause—FRUs or other:
v None
578 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.
1. Manual intervention is required once the node
reports this error.
2. Attempt to reestablish the cluster using other nodes.
This may involve fixing hardware issues on other
nodes or fixing connectivity issues between nodes.
3. 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.
a. 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.
b. 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.
4. If all nodes have either node error 578 or 550,
follow the cluster recovery procedures.
5. Attempt to determine what caused the nodes to
shut down.
Possible Cause—FRUs or other:
v None
650 The canister battery is not supported
Explanation: The canister battery shows product data
that indicates it cannot be used with the code version
of the canister.
User response: This is resolved by either obtaining a
battery which is supported by the system's code level,
or the canister's code level is updated to a level which
supports the battery.
1. Remove the canister and its lid and check the FRU
part number of the new battery matches that of the
replaced battery. Obtain the correct FRU part if it
does not.
2. If the canister has just been replaced, check the code
level of the partner node canister and use the
service assistant to upgrade this canister's code level
to the same level.
Possible cause—FRUs or other cause
v canister battery
651 The canister battery is missing
Explanation: The canister battery cannot be detected.
User response:
1. Use the remove and replace procedures to remove
the node canister and its lid.
2. Use the remove and replace procedures to install a
battery.
3. If there is a battery present ensure it is fully
inserted. Replace the canister.
4. If this error persists, use the remove and replace
procedures to replace the battery.
Possible cause—FRUs or other cause
v canister battery
652 The canister battery has failed
Explanation: The canister battery has failed. The
battery may be showing an error state, it may have
reached the end of life, or it may have failed to charge.
Data
Number indicators with failure reasons
v 1—battery reports a failure
v 2—end of life
v 3—failure to charge
User response:
1. Use the remove and replace procedures to replace
the battery.
Possible cause—FRUs or other cause
v canister battery
653 The canister battery's temperature is too
low
Explanation: The canister battery's temperature is
below its minimum operating temperature.
User response:
v Wait for the battery to warm up, the error will clear
when its minimum working temperature is reached.
Chapter 9. Event reporting
578 • 653
147