Dell PowerVault MD3260i CLI Guide - Page 86

Reconstructing A Physical Disk, Initializing A Virtual Disk, Redistributing Virtual Disks, enclosureID

Page 86 highlights

When you initialize a physical disk, all old disk group and virtual disk information is erased, and the physical disk is returned to an unassigned state. Returning a physical disk to an unassigned state adds unconfigured capacity to a storage array. You can use this capacity to create additional disk groups and virtual disks. To initialize a physical disk, run the following command: start physicalDisk [enclosureID,slotID] initialize where, enclosureID and slotID are the identifiers for the physical disk. Reconstructing A Physical Disk If two or more physical disks in a disk group have failed, the virtual disk shows a status of Failed. All of the virtual disks in the disk group are no longer operating. To return the disk group to an Optimal status, you must replace the failed physical disks. After replacing the physical disks, reconstruct the data on physical disks. The reconstructed data is the data as it would appear on the failed physical disks. To reconstruct a physical disk, run the following command: start physicalDisk [enclosureID,slotID] reconstruct where, enclosureID and slotID are the identifiers for the physical disk. NOTE: You can use this command only when the physical disk is assigned to a RAID 1, 5, or 6 disk group. Initializing A Virtual Disk CAUTION: When you initialize a virtual disk, all data on the virtual disk and all information about the virtual disk are erased. A virtual disk is automatically initialized when you first create it. If the virtual disk starts exhibiting failures, you might be required to re-initialize the virtual disk to correct the failure condition. The initialization process cannot be cancelled once it has begun. This option cannot be used if any modification operations are in progress on the virtual disk or disk group. To initialize a virtual disk, run the following command: start virtualDisk [virtualDiskName] initialize where, virtualDiskName is the identifier for the virtual disk. Redistributing Virtual Disks Redistributing virtual disks returns the virtual disks to their preferred RAID controller module owners. The preferred RAID controller module ownership of a virtual disk or disk group is the RAID controller module of an active-active pair that is designated to own the virtual disks. The preferred owner for a virtual disk is initially designated when the virtual disk is created. If the preferred RAID controller module is being replaced or undergoing a firmware download, ownership of the virtual disks is automatically shifted to the second RAID controller module. The second RAID controller module becomes the current owner of the virtual disks. This change is considered to be a routine ownership change and is reported in the MEL. CAUTION: Ensure that a multipath driver is installed, or the virtual disks are not accessible. To redistribute virtual disks to their preferred RAID controller modules, run the following command: reset storageArray virtualDiskDistribution NOTE: You cannot run this command if all virtual disks are currently owned by their preferred RAID controller module or if the storage array does not have defined virtual disks. 86

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

When you initialize a physical disk, all old disk group and virtual disk information is erased, and the physical disk is
returned to an unassigned state. Returning a physical disk to an unassigned state adds unconfigured capacity to a
storage array. You can use this capacity to create additional disk groups and virtual disks.
To initialize a physical disk, run the following command:
start physicalDisk [enclosureID,slotID] initialize
where,
enclosureID
and
slotID
are the identifiers for the physical disk.
Reconstructing A Physical Disk
If two or more physical disks in a disk group have failed, the virtual disk shows a status of Failed. All of the virtual disks
in the disk group are no longer operating. To return the disk group to an Optimal status, you must replace the failed
physical disks. After replacing the physical disks, reconstruct the data on physical disks. The reconstructed data is the
data as it would appear on the failed physical disks.
To reconstruct a physical disk, run the following command:
start physicalDisk [enclosureID,slotID] reconstruct
where,
enclosureID
and
slotID
are the identifiers for the physical disk.
NOTE:
You can use this command only when the physical disk is assigned to a RAID 1, 5, or 6 disk group.
Initializing A Virtual Disk
CAUTION: When you initialize a virtual disk, all data on the virtual disk and all information about the virtual disk
are erased.
A virtual disk is automatically initialized when you first create it. If the virtual disk starts exhibiting failures, you might be
required to re-initialize the virtual disk to correct the failure condition.
The initialization process cannot be cancelled once it has begun. This option cannot be used if any modification
operations are in progress on the virtual disk or disk group. To initialize a virtual disk, run the following command:
start virtualDisk [virtualDiskName] initialize
where,
virtualDiskName
is the identifier for the virtual disk.
Redistributing Virtual Disks
Redistributing virtual disks returns the virtual disks to their preferred RAID controller module owners. The preferred
RAID controller module ownership of a virtual disk or disk group is the RAID controller module of an active-active pair
that is designated to own the virtual disks. The preferred owner for a virtual disk is initially designated when the virtual
disk is created. If the preferred RAID controller module is being replaced or undergoing a firmware download,
ownership of the virtual disks is automatically shifted to the second RAID controller module. The second RAID controller
module becomes the current owner of the virtual disks. This change is considered to be a routine ownership change and
is reported in the MEL.
CAUTION: Ensure that a multipath driver is installed, or the virtual disks are not accessible.
To redistribute virtual disks to their preferred RAID controller modules, run the following command:
reset storageArray virtualDiskDistribution
NOTE:
You cannot run this command if all virtual disks are currently owned by their preferred RAID controller
module or if the storage array does not have defined virtual disks.
86