Troubleshooting storage


[TIP: ]

TIP: For additional troubleshooting information, enable console access on your Foundation base appliance using the CLI and then find the following log. To enable access, see Basic troubleshooting techniques and read the Enable console access recommendation.

  • /var/log/cinder/volume.log

See the HP 3PAR StoreServ Storage Troubleshooting Guide available from the HP Support Center web site (http://www.hp.com/go/support).


Cinder block storage volume does not attach to virtual machine instance

Symptom Possible cause and recommendation

3PAR iSCSI volume does not attach to VM instance

Incorrect compute node connectivity configuration

  1. Confirm the connectivity configuration from the targeted compute node to the 3PAR storage system iSCSI port. See HP 3PAR StoreServ Storage documents for additional information.

  2. Retry the connection.

When a cinder block storage volume does not attach to a VM instance, you see the following error in the /var/log/cinder/volume.log file in the CloudSystem Console: Error: Everything must be in the same domain to perform this operation. Objects belonging to <domain_name> domain and to <domain_name> were specified.

Multiple virtual domains are defined on the 3PAR storage system

  1. Edit the storage virtual domain to be in the same location as the compute server storage location. See HP 3PAR StoreServ Storage documents for additional information.

  2. Verify that the domains are displayed in the Domains drop-down selector on the Add block storage driver screen. See Add Block Storage Drivers.

Cinder block storage volume does not establish an SSH connection with the 3PAR storage system

Symptom Possible cause and recommendation

You see the error: 3PAR_SSH_CONNECTION_FAILURE

The base appliance is unable to establish SSH connection with the 3PAR storage system

  1. Retry the request.

  2. If the error persists, verify that SSH connections to the 3PAR storage system can be established from the base appliance, and then try the request again.

    See HP 3PAR StoreServ Storage documents for additional information.

The base appliance is unable to establish an HTTPS connection with the 3PAR storage system

  1. Retry the request.

  2. If the error persists, re-import the 3PAR SSL certificate into the base appliance, and then retry the request.

    See Managing certificates from a browser for additional information.

You see the error: 3PAR_SSH_CONNECTION_KEY_MISMATCH_FAILURE

The host key has changed


[NOTE: ]

NOTE: The host key can change when upgrading firmware, or if CloudSystem Console security is compromised.


  1. Manually verify that the correct 3PAR SSH host key is installed on the base appliance.

    See HP 3PAR StoreServ Storage documents for additional information.

Unable to associate block storage driver with 3PAR storage system

Symptom Possible cause and recommendation

When adding or editing a block storage driver, the driver is unable to be associated with the 3PAR storage system

Missing or incorrect user ID and password combination

  1. Enter a valid user ID and password for the 3PAR storage system to which you want to associate the driver.

    See also Storage System Access.

  2. If this corrects the problem the Details section is displayed on the Add Block Storage Driver screen or the block storage driver Edit screen.

Missing or invalid FQDN or IP address

  1. Enter a valid fully qualified domain name or IP address for the storage system to which you want to associate the driver.

    See also Storage System Access.

  2. If this corrects the problem the Details section is displayed on the Add Block Storage Driver screen or the block storage driver Edit screen.

Unable to delete block storage driver

Symptom Possible cause and recommendation

When trying to delete a block storage driver, you see the message: A block storage driver that has dependent volume types cannot be deleted. You must delete the following volume types before deleting the block storage driver.

The driver that you are trying to delete is associated with one or more volume types

  1. Delete the associated volume type(s), and retry the delete driver action. See Delete Volume Types.

  2. With the filters set to All statuses, verify that the volume type no longer appears in the list on the Block Storage Drivers overview screen.

Unable to delete a volume type

Symptom Possible cause and recommendation

When trying to delete a volume type you see the message: A volume type that has dependent volumes cannot be deleted. You must delete the following volumes before deleting the volume type.

The volume type that you are trying to delete is associated with one or more volumes

  1. Delete the associated volume(s), and retry the delete volume type action. See Delete Volumes.

  2. With the filters set to All statuses and All driver types, verify that the volume type no longer appears in the list on the Volume types overview screen.

Unable to edit a volume type

Symptom Possible cause and recommendation

When trying to edit a volume type, you see the message: Volume types created outside CloudSystem Console, for example using the Cloud Storage admin CLI, cannot be edited by CloudSystem Console.

The volume type that you are trying to edit was created outside of the CloudSystem Console

  1. Use the CloudSystem Console to delete the volume type. See Delete Volume Types.

  2. Use the CloudSystem Console to add the volume type. See Add Volume Types.

  3. Use the CloudSystem Console or Cloud Service Management Console to edit the volume type. See Edit Volume Types.

Volume status is mismatched between CloudSystem Console and CloudSystem Portal

Symptom Possible cause and recommendation

The current volume status that is displayed in the CloudSystem Portal is different than the status displayed in the CloudSystem Console

The volume status displayed in the CloudSystem Console refreshes only once per hour with data from the CloudSystem Portal

  1. No action is required. Always refer to the status displayed in the CloudSystem Portal for the most current volume status. The hourly refresh will update the status in the CloudSystem Console.