A host is removed from or fails to be added to a cluster or host pool because that the host is power cycled while HA is being enabled on that cluster or while that host is being added to the host pool or cluster.
If the host is removed from a cluster while HA is being enabled on the cluster, disable and then re-enable HA. The host will show up again in the cluster.
If the host fails to be added, check the cluster or host pool for information about the host. If the host information shows up, delete the host and then re-add it. If the host information does not show up, re-add the host.
To recover an HA cluster the CVM server:
Reinstall CVM and CVK, and then log in to CVM.
Make sure all hosts in the original cluster are operating correctly.
Create an empty cluster and enable HA.
Add any of the hosts in the original cluster to the new empty cluster. In the dialog box that opens, choose to restore the HA configuration of the original cluster or to restore the shared file system of the host.
In the dialog box for adding hosts, add all hosts in the host list to CVM by entering the username and password of their root user accounts in order.
To recover the host:
Reinstall CVM and CVK on the host, and then assign it the same IP address and host name as the original CVM server.
Make sure the remaining hosts in the cluster are operating correctly.
Log in to CVM, and then create an empty cluster with HA enabled.
Add any of the hosts other than the CVM server to the empty cluster. In the dialog box that opens, choose to restore the HA configuration of the original cluster or to restore the shared file system of the host.
In the dialog box for adding hosts, add all hosts in the host list to CVM by entering the username and password of their root user accounts in order.
Check the cluster for the CVM server. If the server is in the cluster, delete it from and then re-add it to the cluster. If the server is not in the cluster, add the server to the cluster.
This issue might occur if the host restarts, shuts down, or loses its connectivity while HA is being enabled or disabled on the cluster.
If the host can be recovered in a short interval, enable or disable HA again on the cluster after the host is recovered.
If the host cannot be recovered in a short interval, remove the host from the cluster, enable or disable HA again on the cluster.
This prompt is displayed if the system cannot start up because of a corrupt file system. File system corruption typically occurs if unexpected power-off, hardware damage, or forced shutdown has occurred.
To resolve this issue with a minimal data loss:
Press F for an automatic recovery.
Restart the host.
If the issue persists, press M for a manual recovery.
Enter the password of the root user, and then execute the fsck -y disk-or-partition command (fsck -y /dev/sda1 for example) to check for file system errors.
Restart the host.
This prompt is displayed if the system cannot start up because of a disk or disk partition recognition failure. This issue typically occurs when the disk is damaged or is absent.
To resolve this issue:
Press S to skip mounting.
Check for disk errors after the host starts up.
Delete information about the unrecognized disk or partitions (if any) from the /etc/fstab directory. Alternatively, add the nobootwait string in the mounting option, "UUID=2f943256-c904-45f7-9ad1-f3a79e7d70f3 /opt/mds/disk/1 ext4 nobootwait,defaults 0 2" for example.
Restart the host by executing the reboot command from the CLI of the host.
When I edit the IQN of a host, the system displays "You cannot Edit the configuration file of iSCSI because iSCSI is being used (Error code: 5029).".
This issue typically occurs if the host and the shared storage fail to communicate because of link failure. When an administrator deletes a shared storage pool from CVM, the host cannot delete the shared storage pool. As a result, the shared storage pool is deleted on CVM, but the session between the host and the storage pool still exists.
To resolve this issue:
Log in to the host through SSH.
Execute the iscsiadm -m session command to verify that the session between the host and the storage pool exists. If the session does not exist, contact the technical support.
Delete the folder named the IQN of the host from directory /etc/iscsi/nodes.
Delete the folder named the IP address of the corresponding storage server from directory /etc/iscsi/send_targets.
The system stops executing scheduled tasks (including scheduled snapshot tasks, backup tasks, and DRX tasks) after I edit the system time of the management host.
This issue occurs because the new system time of the management host is different from the time of the tomcat or casserver daemon.
To resolve this issue:
Log in to the management host through SSH.
Execute the service tomcat8 restart command to restart the tomcat daemon.
The CVM system becomes unavailable after you execute this command. Before executing this command, stop all tasks in the system. Do not perform any operation in the system after you execute this command.
Execute the service casserver restart command to restart the casserver daemon.
The "Domain not found: no domain with matching uuid 06753ef3-7ead-42b1-9b7b-f7b09f53c8ec" error message is displayed when a port profile is edited.
This issue occurs if a port profile has been applied to a VM that is in the database of CAS, but that VM does not exist on the host.
To resolve this issue, delete the VM (most likely in unknown state) from CAS, and then edit the port profile.