Verifying that restore is completed

[On the controller node] Connect to the storage node selected in step 1 of the procedure in Restoring over SSH. You can skip this step if you have already made SSH login during the procedure in Registering drive replacement information.

Perform the operations [On the storage node] on the target one node in the subsequent steps.

$ ssh -i <passphrase-of-private-key> -o UserKnownHostsFile=/dev/null \
-o StrictHostKeyChecking=no \
hitachi_rescue_person@<IP-address-of-storage-node>

Note:

The target private key files are the ones that you obtained in step 4 of Collecting information required for restore and that do not include ".pub" in their file names. When you created the key files as shown in the execution example of step 4, key files sample_ed25519 and sample_ed25519.pub exist, and sample_ed25519 serves as a private key file.

[On the storage node] Perform chunk format operation.

$ sudo /usr/local/bin/hsds-configuration-restore-format-data

[On the controller node] Verify the execution results of the chunk format operation.

CLI: event_log_list

If you receive no response after waiting approximately 1 minute, stop the CLI command forcibly with Ctrl+C, and then retry the operation. If the problem persists, contact the Hitachi design team.

The required parameters are as follows:

--ignore_certificate_errors
--user <user-with-Security-or-Storage-or-Monitor-or-Service-role>
--host <IP-address-obtained-in-step-1-in-Restoring>

You will be prompted to enter the password after running the command. Ask the system administrator to enter the password.

If the event log with the ID and message as shown in the following is output, the chunk operation is completed.

Message Id: KARS13010-I

Message: The job has completed successfully. (Operation = DRIVE_DATA_FORMAT, Job ID = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

CAUTION:

If the chunk format operation is unsuccessful, take action as follows.

When you have not performed hardware replacement (for drives):

Contact the Hitachi design team.
When you have performed hardware replacement (for drives):

Replace all drives with the Blockage status according to step 9 of Registering drive replacement information, and then reperform step 2 of Verifying that restore is completed. If the problem persists, contact the Hitachi design team.

If event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C was output during the procedure of Restoring, perform the procedure of formatting volumes with data reduction enabled.

For details, see Formatting volumes with data reduction enabled (only when event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C is output).

[On the storage node] Perform the restoration verification function.

$ sudo /usr/local/bin/hsds-configuration-restore-checker

When the message “Cluster restoration succeeded.” is displayed, successful restoration is confirmed. Perform the next step.

CAUTION:

If any message other than the above is displayed, perform step 6 in Formatting volumes with data reduction enabled (only when event log KARS06201-E, KARS06220-C, KARS06221-C, or KARS06222-C is output) to verify whether format processing of the volumes with data reduction enabled is completed. If any message other than the above is displayed when you perform this step again after verifying completion of format processing, inform the Hitachi design team of the message contents to troubleshoot the problem. After the problem has been resolved, reperform the operation from Installing the storage software in Re-installing the storage cluster.

[On the storage node] Log out of the storage node.

$ exit