If it is necessary
to replace the hard disk drive or if
the software on the hard disk drive is corrupted, you can use the
node rescue procedure to reinstall the SAN Volume Controller software.
Similarly, if you have replaced the service controller,
you should use the node rescue procedure to ensure that the service
controller has the correct software.
Attention: If you recently replaced
both the service controller and the disk drive as part of the same
repair operation, node rescue fails.
To
provide an alternate boot device, a minimal operating system is also
available in nonvolatile memory on the service controller. If it is
necessary to replace the hard disk drive or the software on the hard
disk drive has become corrupted, the node cannot boot and the hardware
boot indicator remains on the front panel display or the boot operation
does not progress. If this occurs, use the node rescue procedure to
reinstall the SAN Volume Controller software.
Node
rescue works by booting
the operating system from the service controller and running a program
that copies all the SAN Volume Controller software
from any other node that can be
found on the fibre-channel fabric.
Attention: When
running node rescue operations, only run one node rescue operation
on the same SAN, at any one time. Wait for one node rescue operation
to complete before starting another.
Perform the following
steps to complete the node rescue:
Figure 1. Node
rescue display
The node rescue request
symbol displays on the front panel display until the node starts to
boot from the service controller. If the node rescue request symbol
displays for more than two minutes, go to the hardware boot MAP to
resolve the problem. When the node rescue starts, the service display
shows the progress or failure of the node rescue operation.
Note: If the recovered node was part of a cluster,
the node is now offline. Delete the offline node from the cluster
and then add the node back into the cluster. If node recovery was
used to recover a node that failed during a software upgrade process,
it is not possible to add the node back into the cluster until the
upgrade or downgrade process has completed. This can take up to four
hours for an eight-node cluster.