Caution:Risk of data loss -, in most cases, are recoverable. Do not delete missing virtual disks without confirming that the are no longer required, because they will be permanently removed from the configuration. For more information, see Recovering Missing Virtual Disks.
A missing virtual disk is a placeholder node displayed in the Logical View, indicating that the has detected inaccessible physical disks associated with a virtual disk. Typically, this
problem is the result of removing physical disks associated with a or when a loss of power to one or more expansion enclosures has occurred.
Missing virtual disks are only displayed in the Logical View if they are or . In addition, one of the following conditions must exist:
The virtual disk has an existing and physical disks associated with the virtual disk are no longer accessible.
The virtual disk is participating in a as either a or , and physical disks associated with the virtual disk are no longer accessible.
The virtual disk is a and physical disks associated with the virtual disk are no longer accessible. The Recovery Guru has a special recovery procedure for this case. Two Mirror Repository Virtual Disks are created together on the same disk group when the is activated, and one is used for each in the storage array. If physical disks associated with the disk group are no longer accessible, then both Mirror Repository Virtual Disks
are missing, and all Remote Virtual Disk Mirrors are in an .
The virtual disk is a with associated , and physical disks associated with the virtual disk are no longer accessible.
The virtual disk is a , and physical disks associated with the virtual disk are no longer accessible.
The virtual disk is a or in a , and physical disks associated with the virtual disk are no longer accessible.
If missing virtual disks are detected by the storage array, a Missing Virtual Disks group is created in the Logical View of the . Each missing virtual disk is shown, identified by its and virtual disk type. Missing virtual disks are identified as being one of the following:
Standard virtual disk
Source virtual disk
Snapshot repository virtual disk
Primary virtual disk
Secondary virtual disk
Mirror repository virtual disk
The Defined Mappings pane of the updates a virtual disk's properties when it is detected as being a missing virtual disk.
Missing Virtual Disk Examples
The following examples are the typical display changes that occur in the Array Management Window when missing virtual disks are detected by the storage array.
Example 1
A standard virtual disk has no associated virtual disks and no defined virtual disk-to-LUN mapping.
Display details:
The virtual disk is removed from the Logical View.
A missing virtual disk is not displayed in the Logical View.
There is no change to the Defined Mappings pane of the Mappings View.
Menu options available:
None
Example 2
A standard virtual disk has no associated virtual disks but has a defined virtual disk-to-LUN mapping.
The standard virtual disk is displayed as missing.
Display details:
In the Logical View, the Missing Virtual Disks group is created with the missing standard virtual disk displayed under it.
Defined Mappings pane in the Mappings View is updated:
Standard Virtual Disk Name is replaced with the World Wide Name.
Standard Virtual Disk Capacity is replaced with "Unknown."
Standard Virtual Disk Type is changed to "Missing."
Menu options available:
Delete
Example 3
A source virtual disk with an associated virtual disk (snapshot) has defined virtual disk-to-LUN mappings. The snapshot repository virtual disk exists on the same disk group.
The source virtual disk and snapshot repository virtual disk are displayed as missing.
Display details:
In the Logical View, the Missing Virtual Disks group is created, with the missing base and snapshot repository virtual disks displayed under it.
The associated snapshot virtual disk is displayed as a child node of the source virtual disk.
Defined Mappings pane in the Mappings View is updated:
Source Virtual Disk Name is replaced with the World Wide Name.
Source Virtual Disk Capacity is replaced with "Unknown."
Source Virtual Disk Type is changed to "Missing."
Snapshot Virtual Disk Type is changed to "Unavailable."
Menu options available:
Delete
View Associated Elements (right-mouse pop-up menu only)
Go to Repository/Snapshot Virtual Disk (right-mouse pop-up menu only)
Properties
Example 4
A source virtual disk with an associated virtual disk (snapshot) has defined virtual disk-to-LUN mappings. The snapshot repository virtual disk exists on a different disk group.
Only the source virtual disk is displayed as missing.
Display details:
In the Logical View, the Missing Virtual Disks group is created, with the missing source virtual disk displayed under it.
The associated snapshot virtual disk is displayed as a child node of the source virtual disk.
Defined Mappings pane in the Mappings View is updated:
Source Virtual Disk Name is replaced with the World Wide Name.
Source Virtual Disk Capacity is replaced with "Unknown."
Source Virtual Disk Type is changed to "Missing."
Snapshot Virtual Disk Type is changed to "Unavailable."
Menu options available:
Delete
View Associated Elements (right-mouse pop-up menu only)
Example 5
A source virtual disk with an associated virtual disk (snapshot) has defined virtual disk-to-LUN mappings. The snapshot repository virtual disk exists on a different disk group.
Only the snapshot repository virtual disk is displayed as missing.
Display details:
In the Logical View, the Missing Virtual Disks group is created with the missing snapshot repository virtual disk displayed under it.
There is no change to the Defined Mappings pane of the Mappings View.
Menu options available:
View Associated Elements (right-mouse pop-up menu only)
Go To Snapshot Virtual Disk (right-mouse pop-up menu only)
Example 6
A standard virtual disk is participating in a Remote Virtual Disk Mirror as a primary virtual disk.
The primary virtual disk is displayed as missing.
Display details:
In the Logical View, the Missing Virtual Disks group is created with the missing primary virtual disk displayed under it.
The associated secondary virtual disk is displayed as a child node of the primary virtual disk. In the following example, the associated secondary virtual disk is named "Accounting."
Defined Mappings pane in the Mappings View is updated:
Standard Virtual Disk Name is replaced with the World Wide Name.
Standard Virtual Disk Capacity is replaced with "Unknown."
Standard Virtual Disk Type is changed to "Missing."
Menu options available:
Delete
View Associated Elements (for the remote secondary virtual disk only)
Properties (for the remote secondary virtual disk only)
Example 7
A standard virtual disk is participating in a Remote Virtual Disk Mirror as a secondary virtual disk.
The secondary virtual disk is displayed as missing.
Display details:
In the Logical View, the Missing Virtual Disks group is created with the missing secondary virtual disk displayed under it.
Defined Mappings pane in the Mappings View is updated:
Standard Virtual Disk Name is replaced with the World Wide Name.
Standard Virtual Disk Capacity is replaced with "Unknown."
Standard Virtual Disk Type is changed to "Missing."
Menu options available:
Delete
Example 8
Mirror relationships exist on this storage array. The Mirror Repository Virtual Disks exist on a different disk group than any of the virtual disks participating in mirror relationships.
Only the Mirror Repository Virtual Disks are displayed as missing. Two
mirror repository virtual disks are always shown, one for each RAID controller module, because when the Remote Virtual Disk Mirroring Premium Feature is activated, two Mirror Repository Virtual Disks are placed together on the same disk group.
Display details:
In the Logical View, the Missing Virtual Disks group is created with the missing Mirror Repository Virtual Disks displayed under it.
Menu options available:
Delete (right-mouse pop-up menu only)
Recovering Missing Virtual Disks
If missing virtual disks are detected because physical disks have accidentally been removed or are detected as missing due to a loss of power to the expansion enclosures, recovery of these virtual disks is possible
by performing one of the following actions:
Reinserting the physical disks back into the expansion enclosure.
Ensuring that the expansion enclosure's power supplies are properly connected to an operating power source, and have an status.
If the missing virtual disks are no longer required, they can be deleted permanently from the configuration. For more information, see Deleting a Missing Virtual Disk.