HP P6000 HP P6300/P6500 Enterprise Virtual Array User Guide (593079-001, June - Page 175
No Derived Unit for Virtual Disk, Target Object Is Inoperative
View all HP P6000 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 175 highlights
Table 23 Error Messages (continued) Status code value Meaning How to correct 182 Mixed Drive Types The supplied list of drives contained multiple Correct the list such that only one type drive types. of drive is used. 183 Already On An attempt to enable the OCP Locate LED No corrective action required. failed because the LED is already enabled. 184 Already Off An attempt to disable the OCP Locate LED No corrective action required. failed because the LED is already disabled. 185 Virtual Disk Info Failed This error is no longer supported. Report the error to product support. 186 This error is no longer supported. No Derived Unit for Virtual Disk Report the error to product support. 187 Invalid on DRM Mixed Configurations A data replication configuration is using an Upgrade the source and/or unsupported mix of firmware versions on the destination arrays to bring the mix into source and destination side. compliance. 188 Invalid Port Specified The supplied port number is invalid. Correct the port parameter and retry command. 189 Unknown Group Specified data replication group not found. Check the data replication group parameter and retry. 190 Target Object Is Inoperative The empty container being converted to a Heal the inoperative condition and snapshot or snapclone is inoperative. then retry the attach operation. 191 Invalid Read16 Operand A reserved opcode was passed via SCMI Report the error to product support. command. 192 Invalid Controller A SCMI command was passed with an invalid destination controller. Report the error to product support. 193 Invalid Read16 Special Page An invalid page code was requested via SCMI command. Report the error to product support. 194 Cannot Set Failsafe Cannot set Failsafe mode while the group Change asynchronous mode and retry is in asynchronous mode. operation. 195 Invalid Logical Disk Case 1: An attach operation was attempted Case 1: Retry operation using an using a non-empty container. empty container. Case 2: A mirror clone operation was Case 2: Retry operation using a mirror attempted using a virtual disk that was not clone. a mirror clone. 196 LDAD Mismatch 197 Empty Container 198 Unsupported for Active-Active Mode 199 Incompatible Redundancy 200 Unsupported Snap Tree An attach operation attempted to attach an empty container from one disk group to the target virtual disk from a different disk group. Retry the attach, using an empty container in the same disk group as the target virtual disk. An operation was attempted on an empty Retry with an non-empty virtual disk. container. A non-mirrored caching policy was requested in Active-Active mode. Select a different caching policy. A snapshot or snapclone was requested with Retry operation using a RAID type less a RAID type greater than the original virtual than or equal to the RAID type of the disk. original virtual disk. A snapshot or snapclone was requested with Retry operation using the same RAID a different RAID type different from the type as the existing snapshots or existing snapshots or snapclones. snapclones. 175