Dell PowerVault MD3260 CLI Guide - Page 84

Collecting Physical Disk Data, Diagnosing A RAID Controller Module, Recovery Operations

Page 84 highlights

Collecting Physical Disk Data To gather information about all the physical disks in a storage array, run the save allPhysicalDisks command. This command collects sense data from all the physical disks in a storage array and saves the data to a file. The sense data consists of statistical information maintained by each of the physical disks in the storage array. Diagnosing A RAID Controller Module The diagnose controller command's testID parameter takes the following options, which you can use to verify that a RAID controller module is functioning correctly: • 1- Reads the test • 2- Performs a data loop-back test • 3- Writes the test The read test initiates a read command as it would be sent over an I/O data path. The read test compares data with a known, specific data pattern, checking for data integrity and errors. If the read command is unsuccessful or the data compared is not correct, the RAID controller module is considered to be in error and is placed offline. Run the data loopback test only on RAID controller modules that have connections between the RAID controller module and the physical disks. The test passes data through each RAID controller module physical disk-side channel out onto the loop and back again. Enough data is transferred to determine error conditions on the channel. If the test fails on any channel, this status is saved so that it can be returned if all other tests pass. The write test initiates a write command as it would be sent over an I/O data path to the diagnostics region on a specified physical disk. This diagnostics region is then read and compared to a specific data pattern. If the write fails or the data compared is not correct, the RAID controller module is considered to be in error, and it is failed and placed offline. For best results, run all three tests at initial installation. Also, run the tests any time you make changes to the storage array or to components connected to the storage array (such as hubs, switches, and host adapters). A custom data pattern file called diagnosticsDataPattern.dpf is included on the Utility directory of the installation CD. You can modify this file, but the file must have the following properties to work correctly for the tests: • The file values must be entered in hexadecimal format (00 to FF) with only one space between the values. • The file must be no larger than 64 bytes in size. Smaller files can be used, but larger files can cause an error. The test results contain a generic, overall status message and a set of specific test results. Each test result contains the following information: • Test (read/write/data loopback) • Port (read/write) • Level (internal/external) • Status (pass/fail) Events are written to the MEL when diagnostics are started and when testing is completed. These events help you to evaluate whether diagnostics testing was successful or failed and the reason for the failure. Recovery Operations Recovery operations involve replacing failed RAID controller modules and physical disks, restoring data, and restoring the storage array to operation. 84

  • 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

Collecting Physical Disk Data
To gather information about all the physical disks in a storage array, run the
save allPhysicalDisks
command. This
command collects sense data from all the physical disks in a storage array and saves the data to a file. The sense data
consists of statistical information maintained by each of the physical disks in the storage array.
Diagnosing A RAID Controller Module
The
diagnose controller
command’s testID parameter takes the following options, which you can use to verify
that a RAID controller module is functioning correctly:
1
— Reads the test
2
— Performs a data loop-back test
3
— Writes the test
The read test initiates a
read
command as it would be sent over an I/O data path. The read test compares data with a
known, specific data pattern, checking for data integrity and errors. If the
read
command is unsuccessful or the data
compared is not correct, the RAID controller module is considered to be in error and is placed offline.
Run the data loopback test only on RAID controller modules that have connections between the RAID controller module
and the physical disks. The test passes data through each RAID controller module physical disk-side channel out onto
the loop and back again. Enough data is transferred to determine error conditions on the channel. If the test fails on any
channel, this status is saved so that it can be returned if all other tests pass.
The write test initiates a
write
command as it would be sent over an I/O data path to the diagnostics region on a
specified physical disk. This diagnostics region is then read and compared to a specific data pattern. If the write fails or
the data compared is not correct, the RAID controller module is considered to be in error, and it is failed and placed
offline.
For best results, run all three tests at initial installation. Also, run the tests any time you make changes to the storage
array or to components connected to the storage array (such as hubs, switches, and host adapters).
A custom data pattern file called
diagnosticsDataPattern.dpf
is included on the
Utility
directory of the installation CD.
You can modify this file, but the file must have the following properties to work correctly for the tests:
The file values must be entered in hexadecimal format (00 to FF) with only one space between the values.
The file must be no larger than 64 bytes in size. Smaller files can be used, but larger files can cause an error.
The test results contain a generic, overall status message and a set of specific test results. Each test result contains the
following information:
Test (read/write/data loopback)
Port (read/write)
Level (internal/external)
Status (pass/fail)
Events are written to the MEL when diagnostics are started and when testing is completed. These events help you to
evaluate whether diagnostics testing was successful or failed and the reason for the failure.
Recovery Operations
Recovery operations involve replacing failed RAID controller modules and physical disks, restoring data, and restoring
the storage array to operation.
84