Troubleshooting pools, pairs, and volumes related to Thin Image

Pool information is not displayed.

Cause: The pool is blocked.

Solution: Recover the blocked pool (see Workflow for recovering blocked pools).

An HTI pool is blocked.

Solution: Perform Workflow for fixing errors when SIMs are reported.

For information about troubleshooting DP pools, see the Provisioning Guide for your storage system.

The HTI pool usage rate of the pool capacity or the capacity ensured for writing exceeds the threshold.

Solution: Perform Workflow for fixing errors when SIMs are reported.

For more information about the pool capacity and the capacity ensured for writing, and for information about troubleshooting DP pools, see the Provisioning Guide for your storage system.

You cannot add pool-VOLs to HTI pools.

Causes:

• You have reached the maximum amount of pool-VOLs that can be added to a pool (see Increasing pool capacity).
• Available pool management block in the V-VOL management area in the SM is insufficient.
• Pool-VOL requirements were not followed.

Solutions:

• Add pool-VOLs to another pool.
• Initialize the V-VOL management area.
• Check pool-VOL requirements.

For information about troubleshooting DP pools, see the Provisioning Guide for your storage system.

You cannot create HTI pairs.

Causes:

• You have reached the maximum amount of cache management devices.
• You have not met the prerequisites to create the pair.
• The status of the specified volume is not displayed because you are deleting the HTI pair.
• The HTI pool usage rate exceeded the threshold.
• The DP pool warning threshold is exceeded.

Solutions:

• Make sure that you have enough cache management devices to create the pairs (see Thin Image cache management device requirements).
• If cache management devices are running out, complete one of the following:
  • Delete unnecessary external volumes.
  • Delete unnecessary V-VOLs.
  • Delete the HTI pairs related to the P-VOL.
• Complete the following:
  1. Fulfill the conditions to create the pair.
  2. Create the pair.
• Execute the inqraid CCI command and verify that the volume is not used by HTI, and then try the pair creation again.
• If the HTI pool usage rate exceeded the threshold, perform the procedure in Workflow to perform when SIMs related to the pool usage rate were reported.
• If SIM code 62B000 is reported, the DP pool warning threshold might be exceeded. See the list of SIM codes in the Provisioning Guide for your storage system. From the listed solutions for SIM code 62B000, perform the applicable one.

You cannot split HTI pairs.

Cause: The pool might be full.

Solution: If SIM code 62Axxx is reported, the pool might be full. See the list of SIM codes in the Provisioning Guide for your storage system. From the listed solutions for SIM code 62Axxx, perform the applicable one.

A timeout occurs and the CCI command ends abnormally (error code EX_EWSTOT).

Cause: The consistency group contains an HTI pair whose status cannot be changed.

Solution: Resolve the error condition and perform pair tasks (see Notes on using Thin Image primary volumes as TrueCopy, ShadowImage, or Universal Replicator pair volumes and Notes on storing snapshot data).

HTI pairs are not displayed in the volume list.

Causes:

• You have not created the HTI pairs.
• The filtering function is prohibiting the displaying of the pairs.

Solutions:

• Create the HTI pairs.
• Change the settings in the Display Filter dialog box.

An error occurred while restoring the pair.

Cause: A volume is blocked because a failure occurred in the data drive.

Solution:

1. Delete the blocked HTI pair (see Deleting Thin Image pairs).
2. Contact customer support.

A volume is blocked.

Causes:

• A failure occurred in at least two data drives.
• The breaker was turned off once and then the power supply switched on.

Solution: Contact customer support.

A problem occurred in the host application for monitoring the volumes.

Cause: Access to the volume is rejected.

Solution:

1. Stop the host application monitoring the volumes.
2. Split all of the pairs ("PSUS" status or an unpaired volume) (see Splitting Thin Image pairs to store snapshot data).
3. Start the monitoring application on the host and check whether the host has access to pair volumes (see How Thin Image pair status changes).

A virtual volume cannot be recognized correctly after the host server is booted/rebooted or the command for recognizing a device is performed.

Cause: Access to the volume is rejected.

Solution:

1. Stop the host application monitoring the volumes.
2. Split all of the pairs ("PSUS" status or an unpaired volume) (see Splitting Thin Image pairs to store snapshot data).
3. Reboot the host server or run a command that causes the system to recognize the device.
4. Start the monitoring application on the host and check whether the host has access to pair volumes (see How Thin Image pair status changes).

The host computer attempts to access the port and an error occurs.

Cause: A port may go offline because access to a volume on another port has been rejected.

Solutions:

• Wait until the process has completed, and then retry the task.
• If a host application is installed to monitor the volume, stop the application.

HDvM - SN times out frequently.

Causes:

• HDvM - SN cannot respond to the SVP because the load is too heavy.

Solutions:

• Wait until the process has completed and then retry the task.

The pair information in the Local Replication window is not updated. The date and time in Last Updated is not updated.

Cause: HTI processing may be in progress.

Solution: The update will complete sometime after the HTI processing finishes.

After a host completes a write operation, the used pool capacity shown in the Summary section of the Pools window and in the list in the Primary Volumes tab of the selected pool do not match.

Cause: The copy processing is running.

Solution: Wait until the copy processing is completed. The used pool capacity shown in the Summary section of the Pools window and in the list in the Primary Volumes tab of the selected pool match.

For more information about viewing the used pool capacity in this section and on this tab, see Monitoring pool information.

You cannot resynchronize a suspended HTI pair ("PSUE" status).

Solution:

1. Delete the HTI pairs related to the P-VOL (see Deleting Thin Image pairs).
2. Create the HTI pair (see Creating Thin Image pairs using Device Manager - Storage Navigator).

Solution:

• Enable the automatically adding pool volumes function for the pool.
• After the pool failed to shrink, if the automatically adding pool volumes function in a parity group is disabled, disable accelerated compression of the pool to be shrunk first, and then enable accelerated compression of the pool again.
• Delete LDEVs that are not used.
• Stop the maintenance work.
• Delete pools that are not used.
• Delete V-VOLs that are not used.
• Delete all HTI pairs that contain P-VOLs of unnecessary HTI pairs.