No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-73013 I/O Delay of the Storage Disk Is Too Long

ALM-73013 I/O Delay of the Storage Disk Is Too Long


The system reads and saves the I/O delay of the local disk every 5 seconds and calculates the average I/O delay every five minutes. This alarm is generated if the average is obtained for more than 30 times and the average of more than 15 times is greater than the I/O delay threshold that the user set.


Alarm ID

Alarm Severity

Auto Clear







Fault Location Info

host_id: specifies the ID of the host for which the alarm is generated.

disk_name: specifies the name of the abnormal disk.

Additional Info

  • error_info: provides alarm exception information.
  • host_id: specifies the ID of the host for which the alarm is generated.
  • hostname: specifies the name of the host for which the alarm is generated.
  • HostIP: specifies the IP address of the host for which the alarm is generated.

Impact on the System

  • The usage of the CPU for handling disk I/O read and write is too high.
  • The service processing speed of the CPU is slow down.

Possible Causes

  • The system responds slowly to disk I/O read and write operations due to hardware failures.
  • No RAID group is created, or the RAID card driver is abnormal.


  1. Log in to the FusionSphere OpenStack web client.

    For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode).

  2. On the Summary page, obtain the management IP address of the host in the OM IP Address column based on the host ID or host name in the alarm additional information.
  3. Use PuTTY to log in to the host for which the alarm is generated using the management IP address of the host.

    The default user name is fsp. The default password is Huawei@CLOUD8.

    The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

  4. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password of user root is Huawei@CLOUD8!.

  5. Run the following command to disable user logout upon system timeout:


  6. Run the following command to import environment variables:

    source set_env

    Information similar to the following is displayed:

      please choose environment variable which you want to import: 
      (1) openstack environment variable (keystone v3) 
      (2) cps environment variable 
      (3) openstack environment variable legacy (keystone v2) 
      (4) openstack environment variable of cloud_admin (keystone v3) 
      please choose:[1|2|3|4] 

  7. Enter 1 to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

    Default account format: DCname_admin; default password: FusionSphere123.

  8. Use the SMART tool to check whether the hardware is normal.

    1. Obtain the disk name, the value of ${DIVICE}, in alarm details.
    2. Run the smartctl -i /dev/${DIVICE} command to query whether the hardware supports the SMART tool.
      • If "SMART support is: Enabled" is displayed, the SMART tool is supported. In this case, go to c.
      • If "SMART support is: Disabled" or "SMART support is: Unavailable" is displayed, the SMART tool is not supported.

        In this case, it is the RAID card that does not support the SMART tool, and you need to obtain the check tool of the target vendor.

    3. Trigger the SMART self-check. Run the smartctl -t long /dev/${DEVICE} command to perform hardware detection on the background. This process takes a long time.
    4. Run the smartctl -l selftest /dev/${DEVICE} command to query the detection result. The results are listed in descending order according to the time.

    • If Completed is displayed in the Status column, there is no major problem in the disk.
    • If an error is reported and the disk responds slowly for multiple times, contact the disk vendor or replace the disk.

  9. Contact technical support for assistance.

Related Information


Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 48305

Downloads: 33

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next