Procedure
l Cause 1: The disk enclosure where the HyperImage is located is powered off abnormally.
1. Check whether the power cable of the disk enclosure is properly connected. Connect
the power cable again if the power cable of the disk enclosure is improperly connected.
2. Check whether the external power supply is normal. Contact the maintaining
personnel for help if the external power supply is abnormal.
3. After the power supply is recovered and the disk enclosure is powered on, the source
LUN of the invalid HyperImage and the invalid HyperImage are normal.
l Cause 2: The RAID group that owns the HyperImage is invalid.
1. Contact technical support engineers. For how to contact technical support engineers,
see 3.4 Obtaining Technical Support.
----End
5.18 Automatic Termination of HyperImages
This section describes how to handle the fault that HyperImages are automatically terminated.
Symptom
The activated HyperImage is automatically in Stop status and the system prompts Snapshot
halt due to abnormity.
Possible Causes
One of the following causes may arouse the automatic termination of a HyperImage:
l The HyperImage is faulty.
l No available LUNs exist in the resource pool.
Fault Diagnosis
You can determine the cause for the fault through the following procedure:
l Cause 1: For how to locate the HyperImage fault, see 5.17 HyperImage Fault.
l Cause 2: No available LUNs exist in the resource pool.
1. In the navigation tree, choose the Resource Pool node to view the information about
the resource pool.
2. If the valid capacity of the resource pool is 0, you can determine that no available
LUNs exist in the resource pool.
Procedure
l Cause 1: For how to locate the HyperImage fault, see 5.17 HyperImage Fault.
l Cause 2: No available LUNs exist in the resource pool.
1. Add resource LUNs to the resource pool to expand the capacity of the resource pool,
so that enough resource LUNs are available.
2. Delete the faulty HyperImage and recreate a new one.
OceanStor S2600 Storage System
Troubleshooting 5 Troubleshooting of Common Faults
Issue 03 (2010-01-28) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
5-23