Integration Guides › Message Reference Guide › Controller Recovery GUI Messages

Controller Recovery GUI Messages

The following recovery stages can be displayed in the Details section of the Controller Recovery GUI during the process of recovering from a controller failure:

• Waiting for servers with controller volume streams to connect. List of connected servers have connected. Waiting on list of disconnected servers to connect. Timeout in X seconds.|
• Waiting for servers with remaining controller volume streams to connect. List of connected servers have connected. Waiting on list of disconnected servers to connect. Timeout in X seconds.|
• Mounting controller volumes with X of Y servers connected.
• Performing file system check on controller boot volume.
• Performing file system check on controller metadata volume.
• Performing file system check on controller impex volume.
• Repairing file system errors on controller boot volume.
• Repairing file system errors on controller metadata volume.
• Starting grid controller on server name.

The following messages can be displayed in the Messages section of the Controller Recovery GUI during the process of recovering from a controller failure:

• Unable to mount controller boot volume. Servers list of servers with boot volume streams did not connect. Bring these servers back online and the grid controller should recover on its own. If the grid controller does not recover, contact technical support.
• Unable to mount controller meta volume. Servers list of servers with metadata volume streams did not connect. Bring these servers back online and the grid controller should recover on its own. If the grid controller does not recover, contact technical support.
• Unable to mount controller impex volume. Servers list of servers with impex volume streams did not connect. Bring these servers back online and the grid controller should recover on its own. If the grid controller does not recover, contact technical support.
• File system errors detected on controller boot volume. Backing up the volume in preparation for a file system repair.
• File system errors detected on controller metadata volume. Backing up the volume in preparation for a file system repair.
• Aborting start of grid controller because file system errors were detected on the following controller volumes: list of bad controller volumes
• Failed to start grid controller on server . see server's system log for details. If there is another secondary controller server, the grid controller may be started on that server. If this problem persists, contact technical support.