Troubleshooting ThinkSystem DE Series storage devices
Use this information to troubleshoot issues with ThinkSystem
DE Series storage devices.
Mirror consistency group degraded
The age of the recovery point on the secondary side of an asynchronous mirror consistency group has exceeded the recovery point alert setting.
Mirror consistency group orphaned
A delete mirror consistency group operation was performed while there was a connection problem between this storage array and the remote storage array. As a result, the mirror consistency group was not completely deleted leaving one of the mirror consistency group orphaned on this storage array.
Mirror consistency group role conflict
A mirror consistency group holds the same role (primary or secondary) on both this (local) storage array and the remote storage array. This problem typically occurs when a role change operation was attempted while there was a connection problem between this storage array and the remote storage array. As a result, the role of the mirror consistency group was forced to primary or secondary on only one side. When the connection was re-established between the two storage arrays, the forced promotion resulted in both sides holding the same role.
Mirror consistency group - synchronization paused
A mirror consistency group's synchronization has been paused. This problem typically occurs when there are any communication problems between the local and remote storage array or problems with the secondary volumes, or when the controller that owns one of the mirrored volumes within the affected asynchronous mirror consistency group is in an offline (non-optimal) state.
Mirrored pair failed
This problem can occur in the following situations: (1) There is an underlying problem with the primary volume in an asynchronous mirrored pair or one or more of the repository volumes comprising its reserved capacity or (2) There is an integrity error on a repository volume associated with the reserved capacity.
Asynchronous mirrored pair orphaned
A remove mirrored pair operation was performed while there was a connection problem between this storage array and the remote storage array. As a result, the mirrored pair was not completely removed leaving one of the mirrored pair volumes orphaned on this storage array.
Mirrored pair - recovery point lost
The synchronization recovery point for at least one mirrored pair within an asynchronous mirror consistency group has been lost.
Controller degraded to preserve offline volume data
A volume with write caching enabled was placed offline because the volume's associated disk pool or volume group is missing drives. The volume's preferred controller is being held in a degraded state to preserve the data in write cache.
Controller diagnostics failed
A controller-initiated diagnostic detected a failed on-board I/O controller on one of the controllers in the storage array.
Controller drive channel degraded
A drive channel status was set to degraded because of excessive I/O errors or because it was manually set to degraded as instructed by a Technical Support Engineer for diagnostic or other support reasons.
Controller offline
A controller was either manually placed offline or automatically placed offline after failing a diagnostic test.
Controller reboots detected
The storage array is experiencing excessive controller reboots. Please contact your Technical Support Engineer using the steps below to resolve this problem.
Controller submodel not supported
The submodel identification number associated with one of the storage array's controller was either not set at the factory or is not supported.
Recovery procedure not available
The details and recovery procedure for this problem are not provided. If the problem is hardware-related, you can go to Hardware to potentially help diagnose the problem. Please contact your Technical Support Engineer using the steps below to resolve this problem.
Degraded drive path
A drive channel is experiencing intermittent errors along the path to one or more drives.
Drawer type incorrect
A drawer installed in the storage array is not the correct type of drawer for the drive shelf.
Drive bay limited exceeded
The storage array has exceeded the allowed number of drive bays. This problem typically occurs when you add an additional drive shelf after you already have the maximum number of drive bays allowed.
Impending drive failure – waiting for hot spare drive
A drive is reporting internal errors that could cause the drive to fail. The storage array has attempted to automatically copy the drive's contents as a safety precaution, but was unable to as there are currently no eligible standby hot spare drives to spare for the affected drive.
Impending drive failure - unable to copy drive to pool
A drive is reporting internal errors that could cause the drive to fail. The storage array has attempted to automatically copy the drive's contents as a safety precaution, but was unable to as there is either not enough free capacity in the pool or temporarily removing the drive from the pool would cause the pool to contain less than the minimum of 11 drives.
Drive security key creation failed
The storage array was unable to create a security key as the storage array's client certificate does not match any of the existing users on the key management server.
Drive security key mismatch
The security key used by the Drive Security feature is not consistent between the storage array's controllers. This problem occurs when a controller replacement has occurred and the storage array is unable to correct the inconsistency between the controllers.
Solid state disk (SSD) – end of life
An SSD drive is reporting that it has reached the end of its usable life which could cause the drive to fail. If the drive fails, any associated volumes, disk pools and volume groups will become degraded and may lose data.
Drive incompatible
A drive was physically replaced with a drive of the wrong type or a drive with a smaller capacity than the original.
Host multipath driver incorrect
The storage array has determined that a host's multipath driver is not operating as expected given the host's selected host operating system type.
Host redundancy lost
A Host is unable to communicate with one of the storage array's controllers.
IOM (ESM) removed
An IOM has either been removed from the drive shelf or is present but is being reported as removed because it is not seated correctly.
IOM (ESM) uncertified
The storage array currently contains a drive shelf that has one or more uncertified IOMs. This can be caused by one of the following conditions: (1) You added or replaced an entire drive shelf that has one or more uncertified IOMs, or (2) You replaced an IOM with an uncertified one.
SAS loop – improper connection (miswire)
There is a loop in one of the storage array's drive channels resulting in one or more component's drive channel ports being discovered more than once.
Pool capacity – critical threshold exceeded
A pool's capacity has exceeded the critical alert threshold. This problem is the result of either the pool's capacity being allocated beyond the critical alert threshold or the pool's free capacity being temporarily reduced by drive failures.
Pool capacity – full
All of the pool's capacity (free and preservation) has been used. This problem typically occurs when the pool's free capacity has been temporarily reduced by drive failures.
Pool capacity – early threshold exceeded
A pool's capacity has exceeded the early alert threshold. This problem is the result of either the pool's capacity being allocated beyond the early alert threshold or the pool's free capacity being temporarily reduced by drive failures.
Pool preservation capacity in use
One or more drives in a pool have failed. Because there is no more free capacity in the pool, the pool's preservation capacity has been used to reconstruct the failed drive's contents.
Synchronous mirroring – primary volume conflict
Both volumes in the mirror relationship are currently in the primary role. This problem occurs when the secondary volume in the mirrored pair is promoted to the primary role while there is a connection problem between the local and remote storage arrays.
Synchronous mirroring – secondary volume conflict
Both volumes in the mirror relationship are currently in the secondary role. This problem occurs when the primary volume in the mirrored pair is demoted to the secondary role while there is a connection problem between the local and remote storage arrays.
Synchronous mirroring – missing reserved capacity
The drives associated with the synchronous mirroring reserved capacity are no longer accessible. This problem is caused by the removal of all of the associated pool or volume group's drives or a loss of power to one or more drive shelves.
Synchronous mirroring – data unsynchronized
The secondary volume in the mirrored pair is no longer synchronized with the primary volume. This problem occurs when data written to the primary volume is unable to be mirrored to the secondary volume due to a communication problem with the remote storage array, or a failed synchronous mirroring reserved capacity volume.
SFP failed
A Small Form-factor Pluggable (SFP) transceiver on the controller shelf has failed, is inserted incorrectly, or the protocol type and/or maximum transmission speed do not match what is supported.
Shelf ID conflict
Two or more shelves are using the same shelf identification number.
Snapshot image purged
A snapshot image was purged. This problem occurs when reserved capacity for the associated snapshot group becomes full and the policy for the group is to purge the oldest snapshot images, or when the amount of data written to the source volume in an online copy operation exceeds the copy operation's reserved capacity.
Snapshot volume failed
A snapshot volume has failed because there is either a problem with one or more of the individual repository volumes comprising its reserved capacity or there is an integrity error that cannot be corrected.
Maximum temperature exceeded
The maximum operating temperature of the shelf has been exceeded. Either a fan has failed, an obstruction is blocking the air flow, or the temperature of the room is too high.
Nominal temperature exceeded
The nominal operating temperature of the shelf has been exceeded. Either a fan has failed, an obstruction is blocking the air flow, or the temperature of the room is too high.
Shelf shutdown due to over-temperature
The maximum temperature of the shelf has been exceeded. Either a fan has failed, an obstruction is blocking the airflow, or the temperature of the room is too high.
Unable to update remote mirror
The storage array's world-wide identifier has changed and the storage array was unable to notify a mirroed pair's remote storage array of the change.
Unreadable sectors log full
The unreadable sectors log has been filled to its maximum capacity. Until you clear some of the unreadable sectors, any newly detected ones will not be logged.
Volume copy operation failed
A volume copy operation has failed. This problem occurs when the amount of data written to the source volume during an online volume copy exceeds the amount of capacity in the copy operation's reserved capacity, or when there is a problem with either the source or target volume.
Volume group or pool incomplete
One or more drives are missing from the storage array resulting in a volume group or pool not having enough drives to service I/O.
Volume group or pool missing
The storage array has detected that all of the drives associated with a volume group or pool are missing.
Volume - hot spare in use
One or more drives have failed, and hot spare drives have automatically taken over for the failed drives.
Volume modification failed
A volume group or pool has failed because one or more of its associated volumes had a modification operation failure.
Write performance degraded
Interrupted write logging is degrading the storage array's write performance. Please contact your Technical Support Engineer using the steps below to resolve the problem.