$ INFO: Message entries in this catalog file correspond to the
$       sharp defines in the catalog.h header file.
$
$       Developers defining messages in catalog.h should also
$       make an entry in this file of the ASCII message.
$
$       All entries in this file starting with a DOLLAR SIGN/SPACE
$       are comments.
$
$       The default message set is set 1 (ENGLISH)

$ English Catalog

$set 101


$ #define DEVIO_OPEN_FAIL 1
1 SysDevOpen failed, errno=%d(%s)\n

$ #define DEVIO_IOCTL_FAIL 2
2 DevCommand failed, errno=%d(%s)\n

$ #define DEVIO_CLOSE_FAIL 3
3 DevClose failed, errno=%d(%s)\n

$ #define MEM_ALLOC_FAIL 4
4 Unable to allocate memory.\n

$ #define PARAMETER_CORRUPT 5
5 The parameter %s in the parameter file is missing\nor corrupt. Using default.\n

$ #define IDENT_OPENDIR_FAIL 6
6 BuildArrayList could not open %s directory.\n

$ #define AMP_PARM_FILE_ERROR 7
7 Parameter file error, using default poll interval.\n

$ #define AMP_WARN_NO_DEVICES 8
8 No RAID devices found to check.\n

$ #define IDENT_TABLE_OVERFLOW 9
9 Found more controllers than specified by\nparameter %s. Will only keep track of first %d controllers.\n

$ #define NOTIFY_OPENLOG_FAIL 10
10 Could not open message log %s.\n

$ #define NOTIFY_CRTFILE_FAIL 11
11 Unable to create a temporary file for the notify script.\n

$ #define NOTIFY_READEVENT_FAIL 12
12 Error reading message log.\n

$ #define NOTIFY_INVALID_PARAM 13
13 Corrupt argument list - Usage: putplog {event file}\n

$ #define NOTIFY_APPENDEVENT_FAIL 14
14 Could not append to message log.\n

$ #define NOTIFY_OPENEVENT_FAIL 15
15 Could not open message log %s.\n

$ #define EXPANDPATH_HOME_UNDEF 16
16 No definition for parameter %s - aborting.\n

$ #define APL_PARM_FILE_ERROR 17
17 Parameter file error, parity check aborted.\n

$ #define APL_WARN_USE_DEFAULT 18
18 Parameter error getting parity check time.\nUsing default value.\n

$ #define SYS_LANGUAGE_ERR 19
19 Parameter file error retrieving LANGUAGE parameter.\nDefaulting to ENGLISH.\n

$ #define SYS_LANGUAGE_RANGE 20
20 Unknown value for LANGUAGE parameter.\nDefaulting to ENGLISH.\n

$ #define SYS_CATALOG_ERR 21
21 Could not open LANGUAGE catalog.\nUsing default messages.\n

$ #define PARITY_OK 22
22 OK   \n

$ #define PARITY_INCONSISTENT 23
23 Inconsistent parity repaired blocks %d-%d (%d blocks).\n

$ #define PARITY_RAID0_ABORT 24
24 ABORTED - RAID 0 LUN\n

$ #define PARITY_LUN_DEGRADED 25
25 ABORTED - Degraded LUN\n

$ #define PARITY_CONTROLLER_SCAN 26
26 ABORTED - Controller Parity Scan Enabled\n

$ #define PARITY_NO_RAID 27
27 No RAID devices found.\n

$ #define PARITY_SCANNING 28
28 \nScanning %s:

$ #define PARITY_INVALID_RAID 29
29 Invalid RAID device: %s\n

$ #define NOTIFY_SCRIPT_MISSING 30
30 The notification script %s is missing or not accessible.\nEVENT HAS BEEN LOST.\n

$ #define MAKELUN_32 31
31 Invalid RAID level: %d\n

$ #define MAKELUN_33 32
32 Cannot delete LUNs (-D) until controller is defined (-c).\n

$ #define MAKELUN_34 33
33 Deleting LUN %d.\n

$ #define MAKELUN_35 34
34 Press Control C to abort.\n

$ #define MAKELUN_36 35
35 Deleting all existing LUNs.\n

$ #define MAKELUN_37 36
36 LUN %d already exists.\n

$ #define MAKELUN_38 37
37 Duplicate LUN: %d\n

$ #define MAKELUN_39 38
38 -s (LUN sizes) is a required argument.\n

$ #define MAKELUN_40 39
39 Drive group conflicts with existing group used by LUN %d.\n

$ #define MAKELUN_41 40
40 Drive group already has RAID %d LUNs defined; cannot create RAID %d.\n

$ #define MAKELUN_42 41
41 Using RAID %d to match LUNs on existing drive group.\n

$ #define MAKELUN_43 42
42 Unable to determine available capacity for drive group.\n

$ #define MAKELUN_44 43
43 Capacity available in drive group:  %lu blocks  (%lu MB).\n

$ #define MAKELUN_45 44
44 Even number of disks required for RAID 1.\n

$ #define MAKELUN_46 45
45 Unsupported RAID level %d\n

$ #define MAKELUN_47 46
46 Not enough capacity in drive group for new LUN.\n    %ld MB available   %ld MB requested.\n

$ #define MAKELUN_48 47
47 LUNs found on %s.\n

$ #define MAKELUN_49 48
48   LUN %d    RAID %d    %ld MB\n

$ #define MAKELUN_50 49
49 No existing LUNs were found on %s.\n

$ #define MAKELUN_52 50
50 Missing or bad argument following option %s.\n

$ #define MAKELUN_53 51
51 Invalid drive number (%d); first digit must be 1-%d, second must be 0-%d.\n

$ #define MAKELUN_54 52
52 Drive %d is non-existent.\n

$ #define MAKELUN_55 53
53 Drive %d is failed. Use Recovery Application to restore, then retry raidutil.\n

$ #define MAKELUN_56 54
54 Drive %d has status 0x%02X. Use Recovery Application to restore, then retry raidutil.\n

$ #define MAKELUN_57 55
55 Too many disks specified in list following -g (limit: 30).\n

$ #define MAKELUN_58 56
56 Illegal value following the -D option.\nMust be existing LUN number or "all".\n

$ #define MAKELUN_59 57
57 Too many numbers follow -n (LUN numbers).\n

$ #define MAKELUN_60 58
58 Too many values follow -s (LUN sizes).\n

$ #define MAKELUN_61 59
59 No valid numbers follow -s (LUN sizes expected).\n

$ #define MAKELUN_62 60
60 Can only give one value after -S when creating equal size LUNs.\n

$ #define MAKELUN_63 61
61 Percent values following -s total more than 100.\n

$ #define MAKELUN_64 62
62 %s Failed:

$ #define MAKELUN_65 63
63 ** Check Condition **\n

$ #define MAKELUN_66 64
64 Unknown Failure, return value = %d, errno = %d -- %s\n

$ #define MAKELUN_68 65
65 Attempted to create LUN which already exists.

$ #define MAKELUN_69 66
66 Invalid Segment Size

$ #define MAKELUN_70 67
67 Invalid RAID level

$ #define MAKELUN_71 68
68 Drives are not the same as those used by other LUNs on these drives.

$ #define MAKELUN_72 69
69 RAID level mismatch: A LUN already exists on the specified drive\ngroup which has a different RAID level than what you were attempting to create.\nRAID levels must match.

$ #define MAKELUN_73 70
70 Drive already owned by another LUN.

$ #define MAKELUN_74 71
71 Drive type doesn't match other drives in the LUN.

$ #define MAKELUN_75 72
72 Drive cannot be included in rank because rank is full.

$ #define MAKELUN_76 73
73 Ranks have different number of drives defined.

$ #define MAKELUN_77 74
74 Multiple drives on same channel within same rank.

$ #define MAKELUN_78 75
75 Mirrored drives on the same channel.

$ #define MAKELUN_79 76
76 No capacity available for LUN; additional LUN cannot be defined.

$ #define MAKELUN_80 77
77 Support for TTD/CIOP not the same for all drives in LUN.

$ #define MAKELUN_81 78
78 Error in creating LUN.\n

$ #define MAKELUN_82 79
79 ASC = %02X,  ASCQ = %02X\n

$ #define MAKELUN_83 80
80 Not enough capacity in drive group to create %ld LUNs.\n

$ #define MAKELUN_84 81
81 \nRegistering new logical unit %d with system.\n

$ #define MAKELUN_85 82
82 Formatting logical unit %d  RAID %d   %ld MB \n

$ #define MAKELUN_86 83
83 The maximum number of LUNs exist; cannot create another one.\n

$ #define MAKELUN_87 84
84 User-specified LUN number %d already exists.\n

$ #define MAKELUN_88 85
85 SENSE Data:\n

$ #define MAKELUN_89 86
86 Sense Key: %02x\n

$ #define MAKELUN_90 87
87 \nraidutil program failed.\n

$ #define MAKELUN_91 88
88 \nraidutil program successful.\n

$ #define MAKELUN_92 89
89 Creating temporary RAID 0 LUN to check NVSRAM parameters.\n

$ #define MAKELUN_93 90
90 Cannot find a drive to use for temporary LUN.\n

$ #define MAKELUN_94 91
91 Using drive %d for temporary LUN.\n

$ #define MAKELUN_95 92
92 NVSRAM option will be changed:  Internal bus 10 MB/sec --> 5 MB/sec\n

$ #define MAKELUN_96 93
93 NVSRAM option will be changed:  Removing 2 Gigabyte LUN limit.\n

$ #define MAKELUN_97 94
94 Error in changing NVSRAM options.\n

$ #define MAKELUN_98 95
95 NVSRAM option change successful.\n

$ #define MAKELUN_99 96
96 Deleting temporary LUN.\n

$ #define MAKELUN_100 97
97 \nCan't open device %s status = %x.  Aborting\n \n

$ #define MAKELUN_101 98
98 Warning:  opened device for non-exclusive access.\n

$ #define MAKELUN_102 99
99 Creating LUN %d\n

$ #define MAKELUN_103 100
100 ***  Error reading Array Physical Page (Mode sense page 2A)  ***\n

$ #define MAKELUN_104 101
101 \n \nInvalid name.  Aborting\n \n

$ #define MAKELUN_105 102
102 No RAID controller specified.\n

$ #define RM_TWOHEX 103
103 %02x

$ #define RM_SPACE 104
104  

$ #define RM_RETURN 105
105 \n

$ #define MAKELUN_109 106
106 Device not found: %s\n

$ #define MAKELUN_110 107
107 \nVendor ID         %s

$ #define MAKELUN_111 108
108 \nProductID         %s

$ #define MAKELUN_112 109
109 \nProduct Revision  %s

$ #define MAKELUN_113 110
110 \nBoot Level        %s

$ #define MAKELUN_114 111
111 \nBoot Level Date   %s

$ #define MAKELUN_115 112
112 Illegal %s following -%s argument.\n

$ #define CREATE_RD_DEV_FAIL 113
113 Could not create RDAC node(%s), errno=%d(%s)\n

$ #define CREATE_RD_DIR_FAIL 114
114 Could not create RDAC directory(%s), errno=%d(%s)\n

$ #define STAT_RD_FAIL 115
115 Could not stat RDAC node(%s), errno=%d(%s)\n

$ #define FIND_MODNUM_FAIL 116
116 Could not find the module number of the\nassociated RAID module(%s).\n

$ #define NO_RESTART_DAEMON 117
117 The RDAC Resolution Daemon is unable to launch the restart daemon.\nYou are running without redundant controller protection!\n

$ #define INVALID_RDAC_MSG 118
118 The RDAC Resolution Daemon has received an invalid\nMessage code - %x\n

$ #define NO_PAGE2C_FOR_FAILOVER 119
119 The RDAC Resolution Daemon is unable to retrieve the\nredundant Controller page from device: %s,\nin order to perform a failover.\n

$ #define FAILOVER_FAILED 120
120 The RDAC Resolution Daemon is unable to go to active/passive\nmode on RAID Module %s with device: %s active.\n

$ #define NO_RDAC_SCAN 121
121 The RDAC Resolution Daemon is unable to scan for array devices.\n

$ #define ARRAY_UNOPENABLE 122
122 The RDAC Resolution Daemon is unable to open the array device %s.\n

$ #define NO_RDAC_NODE_DOUBLE 123
123 The RDAC Resolution Daemon is unable to create the RDAC array\ndevice for controllers: %x, %x; Targets: %x, %x; and LUN: %x. Call your Customer Support Representative.\n

$ #define NO_RDAC_NODE_SINGLE 124
124 The RDAC Resolution Daemon is unable to create the RDAC array\ndevice for controller: %x; Target: %x; and LUN: %x\n

$ #define RDAC_NOT_RECOGNIZED 125
125 The RDAC Resolution Daemon does not recognize the errored RDAC\npair: Rdev - %x, Ndev[0] - %x, Ndev[1] - %x\n

$ #define NO_PAGE2B 126
126 The RDAC Resolution Daemon is unable to retrieve the Logical\narray page from device: %s\n

$ #define RDAC_DEAD 127
127 The RDAC device: %s is dead and inaccessible.\n

$ #define SENSE_KEY 128
128 The Sense key is: 0x%x & ASC/ASCQ are: 0x%x/0x%x\n

$ #define DEVICE_RESERVED 129
129 The device is reserved by another initiator.\n

$ #define DEVICE_UNAVAILABLE 130
130 The device is invalid.\n

$ #define GENERAL_IO_ERR 131
131 A general I/O error occurred.\n

$ #define FCN_STATUS 132
132 The function status is: 0x%x\n

$ #define NO_PAGE2C 133
133 The RDAC Resolution Daemon is unable to retrieve the redundant\nController page from device: %s\n

$ #define EVENT_AEN_3F00_CAUSE 134
134 The target operating conditions have changed.

$ #define EVENT_INFO_ACTION 135
135 Information only. No action required. If desired, select Help >> Contents at the top of the screen. Select the Index button, and then select the ASC/ASCQ Error Codes topic for further details.

$ #define EVENT_AEN_3F80_CAUSE 136
136 A drive failed because it experienced a write failure.

$ #define EVENT_AEN_0C00_CAUSE 137
137 Data could not be written to media due to an unrecoverable memory, battery or drive error. Data loss may have occurred.

$ #define EVENT_AEN_3F81_CAUSE 138
138 A drive failed because the RAID controller could not reassign a sector or restore data after the reassignment failed.

$ #define EVENT_AEN_2980_CAUSE 139
139 A new RAID controller has been replaced or newly added.

$ #define EVENT_AEN_3F82_CAUSE 140
140 A drive is still failed because the controller could not format it or restore it (for example, an error occurred on another drive required for reconstruction).

$ #define EVENT_AEN_2981_CAUSE 141
141 The RAID controller has created a default logical unit (LUN). There is now an accessible LUN that did not exist previously.

$ #define EVENT_AEN_3F83_CAUSE 142
142 The drive may still be usable, but an error occurred while reading from it to reconstruct data for a different drive.

$ #define SEE_RMDOC_ACTION 143
143 See your documentation for instructions on how to resolve this problem.

$ #define EVENT_AEN_3F85_CAUSE 144
144 The drive failed on power-up because the RAID controller could not get a response from it.

$ #define EVENT_AEN_3F01_CAUSE 145
145 The RAID controller successfully downloaded new microcode to the specified drive.

$ #define EVENT_AEN_3F86_CAUSE 146
146 The drive failed during a logical unit format.

$ #define EVENT_AEN_3F02_CAUSE 147
147 The operating definition has changed.

$ #define EVENT_AEN_3F88_CAUSE 148
148 The drive failed because of a deferred error reported by the drive.

$ #define EVENT_AEN_3F03_CAUSE 149
149 The inquiry data has changed.

$ #define EVENT_AEN_3F89_CAUSE 150
150 The drive failed on power-up because the RAID controller set the drive state to "Wrong drive removed/replaced".

$ #define EVENT_AEN_3F84_CAUSE 151
151 The drive failed because of a hardware component diagnostics failure.

$ #define EVENT_AEN_3F90_CAUSE 152
152 The drive was placed in Warning because the RAID controller detected an unrecovered read or write error.

$ #define EVENT_AEN_3F87_CAUSE 153
153 The drive was manually failed by a user.

$ #define EVENT_AEN_3F91_CAUSE 154
154 The drive was placed in Warning because the drive reported a deferred error.

$ #define EVENT_AEN_3F8A_CAUSE 155
155 The drive failed because of a failure in reconstructing parity.

$ #define EVENT_AEN_3FC0_CAUSE 156
156 The RAID controller cannot access a drive because either (1) there is a communication problem due to a faulty connection between the controller and the drives or (2) due to a problem with the controller itself.

$ #define EVENT_AEN_3F8B_CAUSE 157
157 The drive's capacity is not large enough to support all of the logical units that must be reconstructed on it.

$ #define EVENT_AEN_3FC2_CAUSE 158
158 A drive that was at the location [x,y] indicated is no longer at this position.

$ #define EVENT_AEN_3FC7_CAUSE 160
160 (1) A subsystem component other than a drive or controller has failed or is not installed (for example, fan, power supply, battery) or (2) An over-temperature condition has occurred (some RAID modules contain a temperature sensor).

$ #define EVENT_AEN_3F8C_CAUSE 161
161 The drive's block size (sector size) does not match the other drives that comprise the logical unit.

$ #define EVENT_AEN_3FC8_CAUSE 162
162 AC power has been lost and the RAID Module is operating on a UPS (standby power).

$ #define EVENT_AC_POWER_LOST_ACTION 163
163 Stop all writes to the RAID Module now! Then, repair the AC power problem.

$ #define EVENT_AEN_3FC9_CAUSE 164
164 The UPS has indicated that the depletion of its standby power source is imminent.

$ #define EVENT_AEN_3F8D_CAUSE 165
165 The RAID controller was not able to store or access internal configuration information on the drive.

$ #define EVENT_AEN_3FCA_CAUSE 166
166 The UPS battery power is low. The power in the UPS may be lost at any time.

$ #define EVENT_AEN_3FCA_ACTION 167
167 Stop all writes to the RAID Module now! Then, repair the AC power problem and correct the low battery situation with the UPS.

$ #define EVENT_AEN_3FCB_CAUSE 168
168 Normal AC power has been restored.

$ #define EVENT_AEN_3F92_CAUSE 169
169 During power-up, the drive was placed in Warning by the RAID controller.

$ #define EVENT_AEN_3FE0_CAUSE 170
170 A drive or drives has failed and the RAID controller has set the logical unit(s) status to "Dead".

$ #define EVENT_AEN_3FAX_CAUSE 171
171 The drive was placed in Warning because it failed an assurance test.

$ #define EVENT_AEN_3FE2_CAUSE 172
172 Mode parameters for drives in a logical unit do not match. The RAID controller has set the logical unit(s) status to "Dead".

$ #define CALL_CUSTOMER_REP_ACTION 173
173 Check the online help topic, ASC/ASCQ Error Codes, for details. If needed, contact a Customer Support Representative.

$ #define EVENT_AEN_3FE3_CAUSE 174
174 A verification of a drive channel has failed (two or more drives are in different locations than they were originally). The RAID controller has set the logical unit(s) status to "Dead".

$ #define EVENT_AEN_3FE3_ACTION 175
175 Check your drives to make sure they are in the proper locations.

$ #define EVENT_AEN_3FE4_CAUSE 176
176 A verification of a drive SCSI ID has failed. The RAID controller has set the logical unit(s) status to "Dead".

$ #define EVENT_AEN_3FB0_B1_B2_CAUSE 177
177 Excessive media error rate (3FB0), seek rate (3FB1), or grown defects (3FB2) on the drive.

$ #define EVENT_AEN_3FE5_CAUSE 178
178 A wrong drive was replaced. The RAID controller has set the logical unit(s) status to "Dead".

$ #define EVENT_AEN_3FB1_3FB7_CAUSE 179
179 Software was unable to: 1. Access drive (3FB3), 2. Read drive's capacity (3FB4), 3. Read drive's inquiry data (3FB5), 4. Sense drive's format mode page (3FB6), or 5. Sense drive's rigid disk geometry mode page (3FB7).

$ #define EVENT_AEN_3FE6_CAUSE 180
180 The RAID controller could not access two or more drives in a logical unit. The RAID controller has set the logical unit(s) status to "Dead".

$ #define EVENT_AEN_3FE6_ACTION 181
181 Check the drive's connection, power supply, etc.

$ #define EVENT_AEN_3FF0_CAUSE 182
182 There is a problem with the NVSRAM on the RAID controller.

$ #define EVENT_AEN_3FF0_3FF2_ACTION 183
183 Turn off the RAID Module and turn it back on.

$ #define EVENT_AEN_8702_CAUSE 184
184 The controller firmware file was not properly downloaded to the drives, perhaps because all drives are failed (due to a power glitch on the drives) or a software error.

$ #define EVENT_AEN_8702_ACTION 185
185 If all drives are failed, turn off and on the RAID Module and then try to download the firmware again. If that doesn't succeed or all of the drives are not failed, check for a corrupt firmware file.

$ #define EVENT_AEN_8704_CAUSE 186
186 An upload of the latest version of firmware failed. The RAID controller has been forced to use an older version of firmware.

$ #define EVENT_AEN_3FB8_3FB9_CAUSE 187
187 The software was not able to create a DACSTORE (3FB8) or a DISKSTORE (3FB9) on the drive.

$ #define EVENT_AEN_8800_CAUSE 188
188 There is a command error problem with the NVSRAM on the RAID controller.

$ #define EVENT_AEN_3FBA_CAUSE 189
189 The software determined that TTD/CIOP is required, but the drives do not support it.

$ #define EVENT_AEN_880A_CAUSE 190
190 The RAID controller detected an error in the configuration of the fault region of the NVSRAM.

$ #define EVENT_AEN_3FBB_CAUSE 191
191 The start-of-day software determined that TTD/CIOP is not supported by the drive.

$ #define EVENT_AEN_9600_CAUSE 192
192 Redundant controllers are not supported by the current firmware.

$ #define EVENT_AEN_9600_ACTION 193
193 If redundant controllers are needed, upgrade your current version of firmware.

$ #define EVENT_AEN_UNKNOWN_CAUSE 194
194 Unknown

$ #define EVENT_AEN_3FC1_CAUSE 195
195 There is a communication error.

$ #define HLTH_ACTION_START_RECOVERY 196
196 Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.

$ #define HLTH_ACTIVE_CTLR_INACCESSIBLE 197
197 Lost communication with an active controller.

$ #define HLTH_PASSIVE_CTLR_INACCESSIBLE 198
198 Lost communication with a passive controller.

$ #define HLTH_BOTH_CTLRS_INACCESSIBLE 199
199 Lost communication with both controllers of the RAID Module.

$ #define HLTH_MULTI_DRIVE_FAILED_DATA_LOST 200
200 Multiple drives have failed, and their associated LUN(s) are no longer operational.

$ #define HLTH_DRIVE_FAILED_DATA_LOST 201
201 A drive has failed, and its associated LUN(s) are no longer operational.

$ #define HLTH_DRIVE_FAILED 202
202 A drive has failed (either an unassigned drive or a drive with configured LUNs). The associated LUN(s), if applicable, are still functioning.

$ #define HLTH_MULTIPLE_DRIVES_FAILED 203
203 Multiple drives have failed. Their associated LUN(s) are still functioning.

$ #define HLTH_ACTION_DRIVE_RECOVERY_NOW 204
204 Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem because another drive failure will result in loss of data.

$ #define HLTH_WARNING_DRIVES 205
205 The RAID controller has set the drive status of one or more drives to "Warning".

$ #define EVENT_AEN_3FC3_CAUSE 206
206 The destination drive channel has failed.

$ #define HLTH_WARNING_FAILED_DRIVES 207
207 Two or more warned and failed drives have been found.

$ #define HLTH_FAILED_UNIT 208
208 A logical unit was interrupted during creation or formatting.

$ #define HLTH_FAILED_HOTSPARE 209
209 A hot spare drive has failed.

$ #define SWITCH_FAILED 210
210 The RDAC Resolution Daemon is unable to switch\nownership of device: %s \n

$ #define NO_PAGE2C_BOTH 211
211 The RDAC Resolution Daemon is unable to retrieve the\nRedundant Controller page via either path.\n

$ #define LAUNCH_CONFIGAP_DESC 212
212 Create and delete logical units (LUNs) and hot spare drives.

$ #define LAUNCH_CONFIGAP_FAILED 213
213 Could not start the Configuration Application.

$ #define LAUNCH_STATUS_DESC 214
214 View message log and reconstruction status, or monitor performance.

$ #define LAUNCH_STATUS_FAILED 215
215 Could not start the Status Application.

$ #define LAUNCH_RECOVERY_DESC 216
216 Perform recovery/health check operations or start parity check/repair.

$ #define LAUNCH_RECOVERY_FAILED 217
217 Could not start the Recovery Application.

$ #define LAUNCH_PERF_DESC 218
218 Obtain RAID Module, controller, and drive performance statistics.

$ #define LAUNCH_PERF_FAILED 219
219 Could not start the Performance Advisor Application.

$ #define LAUNCH_HELP_DESC 220
220 Obtain version information.

$ #define LAUNCH_MAINT_DESC 221
221 Modify reconstruction, caching, controllers, LUN Balancing, and firmware.

$ #define LAUNCH_MAINT_FAILED 222
222 Could not start the Maintenance/Tuning Application.

$ #define HLTH_FAN_OR_SUPPLY_FAILED 223
223 A power supply or fan has failed. Note that on some RAID Modules, the fans/power supplies are located in a tray called the controller module.

$ #define HLTH_MULTI_FAN_OR_SUPPLY_FAILED 224
224 Multiple fans or power supplies have failed. Note that on some RAID Modules, the fans/power supplies are located in a tray called the controller module.

$ #define OPEN_RD_FAIL 225
225 Could not open RDAC node(%s), errno=%d(%s)\n

$ #define NO_OPEN_CLOSE 226
226 The RDAC Resolution Daemon is unable to open/close the dual paths to device: %s\n

$ #define CREATE_MODULE_DIR_FAIL 227
227 Could not create the module directory(%s), errno=%d(%s)\n

$ #define MAKE_LINK_FAIL 228
228 Could not make the link:  (%s)->(%s), errno=%d(%s)\n

$ #define RU_MCACH_232 229
229 Reading Cache page 08

$ #define RU_MCACH_233 230
230 Writing Cache page 08

$ #define RU_MCACH_234 231
231 Reading Cache Control page (2E)

$ #define RU_MCACH_235 232
232 Writing Cache Control page (2E)

$ #define RU_MINQ_236 233
233 \nFirmware Level    %s

$ #define RU_MINQ_237 234
234 \nFirmware Date     %s

$ #define RU_MINQ_238 235
235 Inquiry command

$ #define RU_MLIO_239 236
236 Deleting LUN

$ #define RU_MLIO_240 237
237 Reading Logical page (2B)

$ #define RU_MLIO_241 238
238 Reading Physical page (2A)

$ #define RU_MLSR_242 239
239 Changing reconstruction rate

$ #define RU_MLUN_243 240
240 Format logical unit

$ #define RU_MLUN_244 241
241 Successfully formatted logical unit %d at RAID %d with a capacity of %ld MB.

$ #define RU_MLUN_245 242
242 %s Failed:\n

$ #define FORK_FOR_RD__FAIL 243
243 Could not fork the process for RdacRestart, errno=%d(%s)\n

$ #define ST_LOGSET_POLL_INT_ERRMSG 244
244 The polling interval in the file rmparams exceeds 59 minutes.\nThe following screen only supports up to 59 minutes.\nTherefore, a default of 5 minutes is shown.

$ #define ST_LOGSET_POLL_INT_ERRMSG2 245
245 If you press Save\nin the next screen, rmparams will change to 5 minutes or the\nvalue you entered; otherwise, rmparams will not be changed.

$ #define ST_POLL_INT_DIFF 246
246 Polling Interval Difference

$ #define CFGSYNC_NO_UPD_TIME_STAMP 247
247 Unable to update configuration time stamp.\n

$ #define CFG_UNASSIGNED 248
248  Unassigned

$ #define CFG_FORMATTING 249
249        Formatting

$ #define CFG_RECONST 250
250 Reconstruct

$ #define CFG_DEGRADED 251
251 Degraded

$ #define CFG_DEAD 252
252 Dead

$ #define CFG_UNKNOWN 253
253 Unknown

$ #define CFG_CREATE_NEW_UNITS 254
254 Create LUNs from unassigned drives or on groups with remaining capacity.

$ #define CFG_CREATE_HOT_SPARE 255
255 Create hot spare drives from unassigned drives.

$ #define CFG_MODIFY_DRV_GRPS 256
256 Modify drive group and individual logical unit settings.

$ #define CFG_DEL_DRV_GRPS 257
257 Delete drive groups, individual LUNs within drive groups, or hot spare drives.

$ #define CFG_LIST_DRVS_IN_SEL_GRP 258
258 List individual drives in selected drive group and locate drives by flashing their lights.

$ #define CFG_FAILED_LUN_CREATION 259
259 Failed to create the following LUNs on %s: LUN %s\nbecause either:\n1) Another host has created LUNs or hot spares on the module\nusing the same drives or LUN numbers,\n2) A LUN or group is being modified, or\n3) A failure has occurred along the connection.\n \n - If another host has already used the same drives or LUN\nnumbers, refresh this application by reselecting the RAID\nModule to see the available drives. Then, recreate the LUNs.\n - If a LUN or group is being modified, wait until the\noperation has completed.\n - If a failure has occurred, run the Recovery Guru and fix\nthe problem.

$ #define CFG_PLS_CHK_STATUS 260
260 \nPlease check the Status Application for more information.

$ #define CFG_COULD_NOT_FIND_RAID_MODS 261
261 Could not find any RAID Modules.

$ #define CFG_APP_ALREADY_RUNNING 262
262 The Configuration Application is already in use. Only\none copy of the application can be opened at a time.

$ #define CFG_CREATE_FOLLOWING_UNITS 263
263 Create the following logical units\n(LUNs)?

$ #define CFG_CREATE_LUN_MB 265
265 Create logical unit %d (%ld MB)?

$ #define CFG_UNABLE_TO_CREATE1 266
266 Unable to create. The RAID Module\nhas reached the maximum number of\nlogical units it can support.

$ #define CFG_UNABLE_TO_CREATE2 267
267 Unable to create. The host system\nhas reached the maximum number of\nlogical units it can support.

$ #define CFG_LUN_CAPACITY1 268
268 LUN Capacity

$ #define CFG_DRV_SELECTION1 269
269 Drive Selection

$ #define CFG_CACHING_PARAMETERS 270
270 Caching Parameters

$ #define CFG_SEGMENT_SIZE1 271
271 Segment Size

$ #define CFG_LUN_ASSIGNMENT1 272
272 LUN Assignment

$ #define CFG_GRP_CAP_EXCEEDED 273
273 Group capacity exceeded. Please correct before continuing.

$ #define CFG_NUM_OF_DRVS_DOES_NOTMATCH 274
274 The number of selected drives does not match the\nnumber selected in the main create screen.\nPlease correct before continuing.

$ #define CFG_NUM_OF_DRVS_DOES_NOTMCH2 275
275 Number of drives selected does not match the\nnumber selected in the main create screen.

$ #define CFG_FOR_RAID3_START_WITH_CH1 276
276 For RAID 3, you must start with drive channel 1 and not\nskip any channels (for example: [1,x], [2,x], [3,x], etc.).

$ #define CFG_CANNOT_HAVE_DRVS_SAME_CH 277
277 The drive configuration is valid. However, it has two or\nmore drives on the same drive channel. If possible, for\nmaximum redundancy, each drive in a drive group/LUN\nshould be on a different channel.\n \nIMPORTANT\nYou cannot avoid this channel conflict if the number of\ndrives selected is greater than the number of channels\nin the RAID Module. \n \n--Press Cancel to return to the drive selection screen.\n--Press OK to continue.

$ #define CFG_CANNOT_USE_DRV_COMB_SEL 278
278 The drive combination selected cannot\nbe used to successfully create a LUN.

$ #define CFG_GRP_CAP_EXCEEDED2 279
279 Group Capacity Exceeded By (MB):

$ #define CFG_REM_GRP_CAP_1 280
280 Remaining Group Capacity (MB):

$ #define CFG_CTRLA_STRING 281
281 Controller A (%s)

$ #define CFG_CTRLB_STRING 282
282 Controller B (%s)

$ #define CFG_FORMAT 283
283 Format

$ #define WAITING_TO_RECONSTRUCT 284
284 Waiting to reconstruct

$ #define BLANK_SCRN_MSG1 285
285 Please select either:

$ #define BLANK_SCRN_MSG2 286
286 (1) One of the push buttons.

$ #define BLANK_SCRN_MSG3 287
287 (2) One of the options from the top menu bar.

$ #define NOT_RECONSTRUCTING 288
288 Not reconstructing

$ #define ST_MULT_DRV_FAIL 289
289 Multiple Drive Failure

$ #define ST_EXC_IDX 290
290 Exceptions: %d of %d

$ #define CFG_LUN_GT_0 291
291 LUN capacity must be greater than 0.

$ #define ST_CHAN_FAIL 292
292 Channel Failure

$ #define MT_ERR_OBTAIN_MOD_INFO1 293
293 An error occurred while obtaining\nRAID Module information.

$ #define MT_NO_LUNS_FND_ON_MOD1 294
294 The LUNs for this module cannot be accessed or\nthere are no RAID 1,3, or 5 LUNs in this module.\nReconstruction cannot occur for RAID 0 LUNs.

$ #define ST_MT_ERR_CHNG_LUN_RECON_RATE 295
295 An error occurred while trying to change\nthe LUN's Reconstruction Rate.

$ #define ST_MT_ERR_GETTING_LUN_DETAILS 296
296 An error occurred while obtaining\nLUN information.

$ #define MT_SAVE_MOD_PROF_EX 297
297 Save module profile information or exit.

$ #define MT_CH_AUTO_PARITY_SETS 298
298 Change auto parity settings.

$ #define MT_HELP 299
299 Get help on the Maintenance/Tuning Application.

$ #define MT_QUIT 300
300 Quit the Maintenance/Tuning Application.

$ #define MT_CACHE_STAT_LINE 301
301 Enable/disable write caching with and without mirroring and cache without batteries.

$ #define MT_LUN_RECON_SETS 302
302 Display and change reconstruction rate settings for logical units (LUNs).

$ #define MT_TRANSFER_LUN_OWNERSHIP 303
303 Balance ownership of LUNs for RAID Modules with active/active controller pairs.

$ #define MT_FW_UPGRADE 304
304 Perform online or offline controller firmware/NVSRAM upgrade.

$ #define MT_SAVE_CACHING_PAR 305
305 Save caching parameters.

$ #define MT_CANCEL_CHANGES 306
306 Cancel changes and leave caching parameters.

$ #define MT_CACHE_HELP 307
307 Get specific help on the caching parameters.

$ #define MT_BAL_LUNS_STAT_LINE 308
308 Balance LUNs across active/active controllers.

$ #define MT_LUN_BAL_HELP 309
309 Get specific help on the LUN Balancing screen.

$ #define MT_SAVE_LUN_BAL_SETS 310
310 Save LUN Balancing settings.

$ #define MT_CANCEL_LUN_BAL_CHANGES 311
311 Cancel changes and leave LUN Balancing.

$ #define MT_CHANGE_TO_DUALACTIVE 312
312 Change RAID Modules with active/passive controllers to active/active.

$ #define MT_SWAP_CTLR_MODE 313
313 Swap the controller modes in an active/passive controller pair.

$ #define MT_CTRLR_MODE_HELP 314
314 Get specific help on the controller mode screen.

$ #define MT_MOVE_GRPS 315
315 Move drive groups to the opposite controller.

$ #define MT_LUN_RECON_HELP 316
316 Get specific help on LUN Reconstruction.

$ #define MT_RANGE_FOR_TIME 317
317 The range for the time is 00:00 to 23:59.

$ #define MT_LUN_BALANCING 318
318 LUN Balancing

$ #define MT_CONTROLLER_MODE 319
319 Controller Mode

$ #define MT_CMODE_ST_LINE 320
320 Change controller mode to active/active or swap active/passive controllers.

$ #define MT_CACHING_PARAMETERS 321
321 Caching Parameters

$ #define MT_FW_UPGRADE_TITLE 322
322 Firmware Upgrade

$ #define MT_NO_CONTROLLER 323
323 No Controller

$ #define MT_CHNGE_CTRLR_MODE 324
324 Change Controller Mode

$ #define MT_CANNOT_SECURE_LUNS 325
325 LUNs for selected module(s) cannot be secured.\nIf possible, unmount your filesystems\nand/or reboot your system.

$ #define MT_SWAP_CTRLR_MODE 326
326 Swap Controller Mode

$ #define MT_SWAP_CTRLR_ERR 327
327 An error occurred while swapping controllers.

$ #define MT_CHNGE_CTRLR_ERR 328
328 An error occurred while changing controller mode.

$ #define MT_CTRLR_STAT1 329
329 Active (No LUNs owned)

$ #define MT_CTRLR_STAT2 330
330 None (Passive Controller)

$ #define MT_CTRLR_STAT3 331
331 None (Offline)

$ #define MT_CTRLR_STAT4 332
332 None (No Controller)

$ #define MT_BAL_LUN_ERR 333
333 An error occurred while balancing LUNs.\n

$ #define MT_BAL_LUNS_CNFRM_MESS 334
334 The logical units (LUNs) are about to be balanced\nacross the active/active controllers in the RAID Module(s)\nyou selected.\n \nOK to proceed?

$ #define MT_MUST_HAVE_DUAL_ACTIVE_CTRLRS 335
335 Module must have an active/active controller pair to perform LUN Balancing.

$ #define MT_CTRLRS_DO_NOT_OWN_LUNS 336
336 The controllers do not own any LUNs or the LUNs are\ncurrently being used by another application.

$ #define MT_LUN_BALANCING1 337
337 Logical Unit (LUN) Balancing

$ #define MT_LUN_BALANCING2 338
338 Confirm LUN Balancing

$ #define MT_HELP_TEXT_CM 339
339 Information In Controller Mode

$ #define CONFIG_TITLE 340
340 Configuration

$ #define CONFIG_DEL_FAILED 341
341 Delete Failed

$ #define CONFIG_DEL_LUN_ERR_MSG 342
342 Some or all of the selected LUNs were not deleted because either:\n \n1) an application is using the LUN,\n2) a filesystem is mounted on the LUN, \n3) the LUN is reconstructing,\n4) another host has the LUN reserved, or\n5) a LUN or group is being modified.\n \n - If another application is using the LUN, wait for the application\n
 
$ #define CONFIG_LIST_LOC_HOTSPARE 343
343 The lights of the selected drives in the \nhot spare drive group are flashing\nin a distinctive pattern.

$ #define CFG_CREATE_LUN_RAID_MB 344
344 Create logical unit %d \n(RAID Level %d, %ld MB)

$ #define CFG_COULD_NOT_DELETE_LUN 345
345 The hot spare drive could not be deleted probably because\nthere is a failed drive in the RAID Module and this hot\nspare has taken over for it.\n \nYou must replace the failed drive and wait for the hot\nspare drive to return to a Standby status before you\ncan delete it. 

$ #define RMDIALOG_STR_YES 346
346 Yes

$ #define RMDIALOG_STR_NO 347
347 No

$ #define RMDIALOG_STR_CANCEL 348
348 Cancel

$ #define RMDIALOG_STR_OK 349
349 &OK

$ #define FUNC_STAT_LOGGING_1 350
350 %s (LUN %s) called by %s failed because of a reservation conflict.

$ #define ST_DRIVE_LBL_NO_CH_ID 351
351 Drive %s

$ #define CFG_LIST_LOCATE_UNASSIGN 352
352 The lights of the selected drives in the\nunassigned drive group are flashing in a\ndistinctive pattern.

$ #define MT_BATT_MSGA1 353
353 Selecting Cache Without\nBatteries allows write caching\nto continue even when the\nbatteries are discharged com-\npletely or not fully charged.\nNormally,

$ #define MT_BATT_MSGA2 354
354  write caching is\nturned off until the batteries\nare charged. If you select this\noption without a UPS for pro-\ntection, you could lose data.

$ #define MT_BATT_MSGB1 355
355 No battery back up is detected\nfor this module. Selecting\nCache Without Batteries\n

$ #define MT_BATT_MSGB2 356
356 allows write caching even with- \nout battery back up.

$ #define MT_BATT_MSGB3 357
357 Normally,\nwrite caching is turned off if no\nbatteries are detected. If you\nselect this option without

$ #define MT_BATT_MSGB4 358
358 a\nUPS for protection, you could\nlose data.

$ #define MT_CHNGE_CTRLR_MODE_ERR 359
359 Change Controller Mode Error

$ #define MT_SAVE_CACH_PARAMS_ERR 360
360 Save Caching Parameters Error

$ #define MT_ERR_WHILE_SAVE_CACH_PARAMS 361
361 Could not save cache parameters because either:\n\n1) Another host has the LUNs reserved.\n2) A failure has occurred along the connection, or\n3) A Capacity Expansion, RAID Level Change, Segment Size Change\nor Defragmentation operation is being performed on a LUN or group.

$ #define MT_CH_AUTO_PARITY_SETS_HDR 362
362 Change Auto Parity Settings

$ #define MT_LUN_RECON_ERR_HDR 363
363 LUN Reconstruction

$ #define MT_CTRLR_NO_CACHE_SUPPORT 364
364 Controller of selected module does\nnot support caching.

$ #define MT_LUN_RECON_RATE_HDR 365
365 Logical Unit (LUN) Reconstruction Rate

$ #define MT_LUN_BALANCING_HDR 366
366 Logical Unit (LUN) Balancing

$ #define MT_CCM_CH_DB 367
367 Confirm Active/Passive Swap

$ #define MT_CCM_CH_DB_TXT 368
368 The controller mode is about to be changed\nfor controller(s) in the RAID Module(s)\nyou selected.\n \nOK to proceed?

$ #define MT_LUN_BAL_ERROR 369
369 LUN Balancing Error

$ #define ST_LOG_SETS_ERR_HDR 370
370 Log Settings Error

$ #define ST_SV_PROF_CANNOT_SEL_FIL 371
371 Cannot write to the file you selected. Save canceled.

$ #define ST_FIL_SAME_AS_LOG_FIL 372
372 File selected to be saved is the current\nlog file. Please reselect.

$ #define ST_SELECT_BEFORE_VIEW_DETAIL 373
373 You must first select a message\nbefore obtaining detailed information.

$ #define ST_OPTION_NOT_AVAIL1 374
374 This option is not available because you are not in the Message Log

$ #define ST_OPTION_NOT_AVAIL2 375
375 This option is not available because you chose the All RAID Modules selection

$ #define ST_OPTION_NOT_AVAIL3 376
376 This option is not available because you are not in the detailed information screen

$ #define HLP_MNT_TITLE_BAR 377
377 Maintenance and Tuning Help

$ #define HLP_MNT_TITLE_BAR_MIN 378
378 Maint - Help

$ #define HLP_CFG_TITLE_BAR 379
379 Configuration Help

$ #define HLP_CFG_TITLE_BAR_MIN 380
380 Config - Help

$ #define HLP_REC_TITLE_BAR 381
381 Recovery Help

$ #define HLP_REC_TITLE_BAR_MIN 382
382 Recov - Help

$ #define HLP_ST_TITLE_BAR 383
383 Status Help

$ #define HLP_ST_TITLE_BAR_MIN 384
384 Status - Help

$ #define MNT_HLP_TEXT1 385
385 Information In Caching Parameters

$ #define MNT_HLP_TEXT2 386
386 Information For All RAID Modules

$ #define MNT_HLP_TEXT3 387
387 Change The Reconstruction Rate

$ #define MNT_HLP_TEXT4 388
388 Information For A Single RAID Module

$ #define ST_CURRENT_LOG 389
389 Current Log: %s

$ #define ST_TOT_MSGS_IN_LOG_0 390
390 Total Messages in Log: 0

$ #define ST_TOT_MSGS_SELECTED_0 391
391 Total Selected: 0 of 0

$ #define ST_SAVE_CURR_MSG 392
392 Save the current message log to another file.

$ #define ST_SAVE_INFO_IN_PROF 393
393 Save the information in the module profile to a file.

$ #define ST_FUNCT_NOT_IMPL 394
394 This function has not yet been implemented.

$ #define ST_QUIT_STATUS 395
395 Quit the Status Application.

$ #define ST_COPY_TO_CLIPBOARD 396
396 Copy the contents of a detailed message to the clipboard.

$ #define ST_SELECT_ALL_MSGS 397
397 Select all the messages in the summary information or highlight the text of a detailed message.

$ #define ST_TOT_MSGS_IN_LOG_1 398
398 Total Messages in Log: %4d

$ #define ST_TOT_MSGS_SELECTED_1 399
399 Total Selected: %4d of %4d

$ #define ST_LOG_FILE_CORRUPTED 400
400 Log file is corrupted. Please open a different log file.

$ #define ST_OPEN_ANOTHER_LOG 401
401 Open another message log for viewing.

$ #define MODULE_PROF_STATUS_LINE 402
402 Receive information on the controllers, drives, and LUNs in the RAID Module.

$ #define ST_OPEN_SAVE_EXIT 403
403 Open, save, or exit.

$ #define ST_GET_HELP 404
404 Get help on the summary information screen.

$ #define ST_PL_SEL 405
405 Please select either Message Log, Health Check, Reconstruction Status

$ #define ST_OR_OTHER_OPTION 406
406 or one of the top-level menu options

$ #define ST_FLASH_LIGHTS 407
407 Flash drive lights on the RAID Module.

$ #define ST_CNTRLR_DRV_INFO 408
408 Receive information on the controllers, drives, and LUNs in the RAID Module.

$ #define ST_PERF_HLTHCHK 409
409 Performing HealthCheck...

$ #define ST_HLTHCHK_HDR_1 410
410 Health Check - Summary Information

$ #define ST_HLTHCHK_STAT_LINE 411
411 Perform an immediate health check on a RAID Module and display the results.

$ #define ST_RECON_HDR 412
412 Reconstruction Status

$ #define ST_RECON_STAT_LINE 413
413 Display the status of any logical units currently reconstructing.

$ #define ST_MSGLOG_HDR_1 414
414 Message Log - Summary Information

$ #define ST_DSPLY_MSG_LOG 415
415 Display the message log.

$ #define ST_MSGLOG_HDR_2 416
416 Message Log - Detailed Information

$ #define ST_DET_INFO_STAT_LINE 417
417 Obtain detailed information on the messages selected.

$ #define ST_SELECT_ALL_MSGS2 418
418 Select all of the messages shown.

$ #define ST_LST_DIFF_MSGS 419
419 List different types of messages.

$ #define ST_GET_HELP_ON_SUMMARY 420
420 Get specific help on the summary information screen.

$ #define ST_GET_HELP_ON_DETAIL 421
421 Get specific help on the detailed information screen.

$ #define ST_VIEW_NXT_MSG 422
422 View the next message.

$ #define ST_VIEW_PREV_MSG 423
423 View the previous message.

$ #define ST_RET_TO_SUMM_SCREEN 424
424 Return to the Summary information screen.

$ #define ST_OPTIMAL 425
425 Optimal

$ #define ST_HLTHCHK_HDR_2 426
426 Health Check - Detailed Information

$ #define ST_GET_DET_INFO_ON_EXC 427
427 Obtain detailed information on the exceptions selected.

$ #define ST_SEL_ALL_EXC 428
428 Select all of the exceptions above.

$ #define ST_STATMAIN_SCRNS 429
429 statmain_screens

$ #define ST_STATVIEW 430
430 stat_view

$ #define ST_OPTIMAL_MSG_3 431
431 Optimal(HealthCheck not done)

$ #define ST_ASC 432
432 ASC

$ #define ST_EQUAL_TO 433
433 EQUAL TO

$ #define ST_ASCQ 434
434 ASCQ

$ #define ST_AND 435
435 AND

$ #define ST_NONE 436
436 NONE

$ #define ST_ASC_FLDS_CHECK 437
437 The ASC or ASCQ fields are checked\nbut no values are specified.

$ #define ST_CHECK_HARDWARE_BUTTON 438
438 If ASC or ASCQ fields are checked, the\nHardware checkbox must also be selected.

$ #define ST_STATUS 439
439 status

$ #define ST_ERR_DURING_HC 440
440 An error occurred while performing the Health Check.\nThe RAID Module will be listed as optimal.

$ #define ST_LUNST_OPT 441
441 Optimal

$ #define ST_LUNST_DEG 442
442 Degraded

$ #define ST_LUNST_FMT 443
443 Formatting

$ #define ST_LUNST_REC 444
444 Reconstructing

$ #define ST_LUNST_DEAD 445
445 Dead

$ #define ST_LUNST_UNKNOWN 446
446 Unknown

$ #define ST_NO_MATCH_FND 447
447 No Match Found

$ #define ST_RAID_MODULE_1 448
448 RAID Module

$ #define ST_RAID_MODULE_2 449
449 RAID Module: %s\n \n

$ #define ST_AFF_COMP 450
450 Affected Component: %40s

$ #define ST_AFF_LUN 451
451 \nAffected Logical Unit: %s\n

$ #define ST_RAID_LEVEL 452
452 RAID Level: %s

$ #define ST_OPEN_LOG_LBL 453
453 Open Log

$ #define ST_OPEN_CANCEL 454
454 Selection is not a file. Open canceled.

$ #define ST_LUN_STATUS_LBL 455
455     LUN Status: %s\n

$ #define ST_PROB_CAUSE 456
456 \nProbable Cause: \n%s\n \n

$ #define ST_ACTION_TO_TAKE 457
457 Action To Take: \n%s\n

$ #define ST_RAID_MODULE_3 458
458 RAID Module:

$ #define ST_ERR_DURING_HC2 459
459 An error occurred while performing a health check.

$ #define ST_AFF_COMP_LBL 460
460 Affected Component:

$ #define ST_AFF_LUN_LBL 461
461 Affected Logical Unit:

$ #define ST_RAID_LVL_LBL 462
462 RAID Level:

$ #define ST_AFF_LUN_STATUS_LBL 463
463 LUN Status:

$ #define ST_PROB_CAUSE_LBL 464
464 Probable Cause:

$ #define COULD_NOT_CREATE_LOG_FILE 465
465 The default log file was not found. Do you want\nit to be created?

$ #define ST_ACTION_TO_TAKE2 466
466 Action To Take:

$ #define ST_MSG_IDX 467
467 Message Index: %d of %d

$ #define ST_HC_ERR_MSG1 468
468 Drive Failure

$ #define ST_HC_ERR_MSG2 469
469 Warning Drive

$ #define ST_HC_ERR_MSG3 470
470 Data Path Failure

$ #define ST_HC_ERR_MSG4 471
471 Module Component Failure

$ #define ST_HC_ERR_MSG5 472
472 Failed/Warning Drive

$ #define ST_HC_ERR_MSG6 473
473 Hot Spare Failure

$ #define ST_HC_ERR_MSG7 474
474 Unit Failure

$ #define ST_HC_ERR_MSG8 475
475 Unknown Failure

$ #define ST_DRIVE_LBL 476
476 Drive [%d,%d]

$ #define ST_CTRLR_LBL 477
477 Controller A

$ #define ST_CTRLR_LBL2 478
478 Controller B

$ #define LOGSET_ERR_MSG1 479
479 Message log filename must be specified.

$ #define LOGSET_ERR_MSG2 480
480 Message log file cannot begin with a blank.

$ #define LOGSET_ERR_MSG3 481
481 Invalid message log path specified.

$ #define LOGSET_ERR_MSG4 482
482 Log size must be specified.

$ #define LOGSET_ERR_MSG5 483
483 Log size cannot contain a character.

$ #define LOGSET_ERR_MSG6 484
484 Log size must be between 1 and 1000.

$ #define LOGSET_ERR_MSG7 485
485 Polling interval must be specified.

$ #define LOGSET_ERR_MSG8 486
486 Polling interval cannot contain a character.

$ #define LOGSET_ERR_MSG9 487
487 Polling interval must be between 1 and 59.

$ #define ST_POWER_SUPPLY 488
488 Power supply or fan

$ #define ST_RMDIALOG_HDR 489
489 Status

$ #define ST_ALL_MODULES 490
490 All RAID Modules

$ #define ST_CHKD_MODULES 491
491 Checked %2d RAID Modules\n

$ #define ST_CHKNG 492
492 Checking...

$ #define ST_OPTIMAL_MSG_2 493
493 Optimal

$ #define ST_NO_CAUSE_FND 494
494 No cause description found.

$ #define ST_NO_ACTION_FND 495
495 No action description found.

$ #define ST_HC_DONE_1 496
496 Health Check Complete; exception found on 1 RAID Module.

$ #define ST_HC_DONE_2 497
497 Health Check Complete; exceptions found on %d RAID Modules.

$ #define ST_HC_DONE_3 498
498 Health Check Complete; no exceptions on %d RAID Module(s).

$ #define ST_CHKD_1_MOD 499
499 Checked 1 RAID Module

$ #define ST_HC_DONE_4 500
500 Health Check Complete; exception found on %s.

$ #define ST_HC_DONE_5 501
501 Health Check Complete; exceptions found on %s.

$ #define ST_HC_DONE_6 502
502 Health Check Complete; no exceptions found on %s.

$ #define ST_HC_INFO_EXCEPT 503
503 Detailed Health Check information can only be obtained for exceptions.

$ #define ST_PENDING 504
504 Pending

$ #define ST_SV_LOG_AS_LBL 505
505 Save Log As

$ #define PLEASE_SEL_EITHER 506
506 Please select either:\n \n(1) One of the push buttons.\n(2) One of the options from the top menu bar.

$ #define ST_NO_LUNS_RECON 507
507 No  LUNs  reconstructing.

$ #define LOGSET_ERR_MSG10 508
508 Incorrect input value

$ #define ST_SAVE_CANCEL 509
509 Selection is not a file. Save canceled.

$ #define ST_REPLACE_FILE 510
510 The file %s\nalready exists. Replace?

$ #define ST_FILE_SAVED_OK 511
511 File successfully saved.

$ #define ST_FILE_NOT_FOR_READ 512
512 Filename was not specified for reading.

$ #define ST_FILE_NOT_EXIST 513
513 File does not exist, or cannot be accessed.

$ #define ST_HARDWARE_LBL 514
514 Hardware

$ #define ST_PARITY_LBL 515
515 Parity  

$ #define ST_GENERAL_LBL 516
516 General 

$ #define ST_OTHER_LBL 517
517 Other   

$ #define ST_MSG_LBL1 518
518  Message\n \n

$ #define ST_DATE_LBL1 519
519 Date: %s

$ #define ST_TIME_LBL1 520
520 Time: %s\n

$ #define ST_DETMSG_LOG_LBL1 521
521 RAID Module: %s\n

$ #define ST_DETMSG_LOG_LBL2 522
522 Controller: %s\n

$ #define ST_DET_MSG_ASC_LBL 523
523 ASC/ASCQ Code:  %s\n

$ #define ST_DET_MSG_AFF_LBL1 524
524 Affected Component:      -\n

$ #define ST_DET_MSG_AFF_LBL2 525
525 Affected Component:    Power supply or fan\n

$ #define ST_DET_MSG_AFF_LBL3 526
526 Affected Component:      Drive [%d,%d]\n

$ #define ST_DET_MSG_AFF_LBL4 527
527 Affected Logical Unit:     %s\n

$ #define ST_PROB_CAUSE_LBL2 528
528 \nProbable Cause: \n%s\n \n

$ #define ST_ACTION_TO_TAKE3 529
529 Action To Take: \n%s\n

$ #define ST_NONE_FND_1 530
530 None found

$ #define ST_DESCR_LBL_1 531
531 \nDescription:\n

$ #define ST_ACT__NONE 532
532 \n \nAction To Take:\nNone\n

$ #define ST_DET_MSG_AFF_LBL5 533
533 Affected Logical Unit:  %s\n

$ #define ST_DET_MSG_AFF_LBL6 534
534     Block Begin: %ld\n

$ #define ST_DET_MSG_AFF_LBL7 535
535     Block End: %ld\n \n

$ #define ST_DET_MSG_AFF_LBL8 536
536 Number of Blocks Repaired: %ld\n

$ #define ST_DET_MSG_FNT_LBL1 537
537 Date:

$ #define ST_DET_MSG_FNT_LBL2 538
538 Time:

$ #define ST_DET_MSG_FNT_LBL3 539
539 RAID Module:

$ #define ST_DET_MSG_FNT_LBL4 540
540 Controller:

$ #define ST_DET_MSG_ASC_LBL2 541
541 ASC/ASCQ Code:

$ #define ST_DET_MSG_AFF_LBL9 542
542 Affected Component:

$ #define ST_DET_MSG_DESC_LBL 543
543 Description:

$ #define ST_BLK_BEG_MSG_LBL 544
544 Block Begin:

$ #define ST_BLK_END_MSG_LBL 545
545 Block End:

$ #define ST_NUM_BAD_BLKS_LBL 546
546 Number of Blocks Repaired:

$ #define ST_NO_DESCR_FND 547
547 No description found.

$ #define ST_MSG_INDEX1 548
548 Messages: %d of %d

$ #define ST_NO_MSGS_FND_1 549
549 No messages found for this module(s) or for the type selected.

$ #define ST_ERR_RECON 550
550 An error occurred during reconstruction.

$ #define ST_LOG_SETTINGS 551
551 Change the default log, log size threshold, and polling interval.

$ #define ST_REFRESH_LOG 552
552 Refresh the message log for all message types.

$ #define ST_EDIT_MSG 553
553 Copy message to a clipboard and select all messages.

$ #define ST_OPTS_MSG 554
554 Perform various status options.

$ #define ST_CHKG_MODULES 555
555 Checking %2d modules

$ #define ST_CHKG_1_MOD 556
556 Checking 1 RAID Module

$ #define ST_STOP 557
557 &Stop

$ #define ST_OK 558
558 &OK

$ #define ST_RAID_MOD_NOT_FND 559
559 The RAID Module selected could not be found.

$ #define ST_ACT_LIGHTS 560
560 The drive lights of %s\nare flashing in a distinctive pattern.

$ #define PROF_MSG_1 561
561 Board Name:

$ #define PROF_MSG_2 562
562 Board ID:

$ #define PROF_MSG_3 563
563 Board Serial Number:

$ #define PROF_MSG_4 564
564 Product ID:

$ #define PROF_MSG_5 565
565 Product Serial Number:

$ #define PROF_MSG_6 566
566 Vendor ID:

$ #define PROF_MSG_7 567
567 Date of Manufacture:

$ #define PROF_MSG_8 568
568 Host-side ID (dec):

$ #define PROF_MSG_9 569
569 Boot Level:

$ #define PROF_MSG_10 570
570 Firmware Level:

$ #define PROF_MSG_11 571
571 Cache/Processor Size:

$ #define PROF_MSG_12 572
572 Profile for %s

$ #define PROF_MSG_13 573
573 Controllers:

$ #define PROF_MSG_14 574
574   Name          Serial Number    Mode           Logical Units

$ #define PROF_MSG_15 575
575 Active

$ #define PROF_MSG_16 576
576 Passive

$ #define PROF_MSG_17 577
577 Offline

$ #define PROF_MSG_18 578
578 Unknown

$ #define PROF_MSG_19 579
579   Number of Drives = %d

$ #define PROF_MSG_20 580
580   Detailed Controller Information for %s

$ #define PROF_MSG_21 581
581 Controller %s

$ #define PROF_MSG_22 582
582 Parameters

$ #define PROF_MSG_23 583
583 Series 3

$ #define PROF_MSG_24 584
584 No controller information available.

$ #define PROF_MSG_25 585
585 Drives:

$ #define PROF_MSG_26 586
586   Detailed Drive Information for %s

$ #define PROF_MSG_27 587
587   Location   Capacity (MB)   Status         Vendor   Product ID

$ #define PROF_MSG_34 594
594 No drive information available.

$ #define PROF_MSG_35 595
595   Detailed Drive Information for %s (continued)

$ #define PROF_MSG_36 596
596   Location   Firmware Version   Serial Number   Date Code

$ #define PROF_MSG_37 597
597 Could not open %s.

$ #define PROF_MSG_38 598
598 %s already exists, overwrite?

$ #define PROF_MSG_39 599
599 Selection is not a file.

$ #define PROF_MSG_40 600
600 No information was selected.\nPlease select items to save.

$ #define PROF_MSG_41 601
601 Controller %c %c%s%c

$ #define PROF_MSG_42 602
602 Controller %c

$ #define PROF_MSG_43 603
603 Detailed Controller Information for %s

$ #define PROF_MSG_44 604
604 Logical Unit Information for %s

$ #define PROF_MSG_45 605
605                Device  RAID  Cap.

$ #define PROF_MSG_46 606
606   LUN   Group  Name    Level (MB) Status

$ #define LIST_MSG1 607
607 The lights of the selected drives in\ndrive group %d are flashing in a\ndistinctive pattern.

$ #define LIST_MSG2 608
608 Drive List for Unassigned Drive Group

$ #define LIST_MSG3 609
609 Drive List for Hot Spare Drive Group

$ #define LIST_MSG4 610
610 Drive List for Drive Group %d

$ #define LIST_MSG5 611
611 Hot Spare

$ #define LIST_MSG6 612
612 Standby

$ #define LIST_MSG7 613
613 In Use

$ #define RESET_MSG1 614
614 The configuration was\nsuccessfully reset.

$ #define RESET_MSG2 615
615 Could not reset configuration because either:\n \n1) an application is using LUNs on the module,\n2) a filesystem is mounted on the module, or\n3) another host has LUNs reserved on the module.\n \nIf another application is using LUNs, wait for the application to\nfinish or stop the application. If there are mounted filesystems on the\nmodule, dismount them. If another host has LUNs reserved, have that\nhost release those LUNs. Afterwards, you can retry the operation.

$ #define RESET_MSG3 616
616 This option will reset your drive groups and\nlogical units back to a default configuration.\nYOU WILL LOSE ALL DATA ON\n %s.

$ #define DELTSCR_MSG1 617
617  and

$ #define CHAR_S 618
618 s

$ #define PROF_DR_GRP_INFO 619
619 Drive Group Information for %s

$ #define PROF_DR_GRP_INFO1 620
620               No.        No.     Total      Remaining

$ #define PROF_DR_GRP_INFO2 621
621               of   RAID  of      Capacity   Capacity

$ #define PROF_DR_GRP_INFO3 622
622   Group       LUNS Level Drives  (MB)       (MB)

$ #define INF 623
623 INF

$ #define EVENT_FILE_TOO_LARGE 624
624 The message log %s\nhas exceeded the specified threshold\nlevel. Use the Status Application to\neither:\n \n1. Save the log to another filename.\n(You must then delete the log contents)\n \n2. Change the default log filename.\n \n3. Increase the threshold level.

$ #define INCORRECT_NVRAM_SETTINGS 625
625 The %s NVSRAM field of controller %s(%s)\nat offset 0x%x is invalid, The value is 0x%x (the valid value should be 0x%x).\n \n

$ #define INCORRECT_NVRAM_SETTINGS_FIX_FAILURE 626
626 Could not fix the incorrect NVSRAM settings of controller %s(%s).\n

$ #define INCORRECT_NVRAM_SETTINGS_FIX_SUCCESS 627
627 The incorrect NVSRAM settings of controller %s(%s) have been fixed.\nThe new settings will not take effect until the controller is reset.\nWhile the subsystem is idle, turn the controller module off, then back on.\n \n

$ #define CORRECT_NVRAM_SETTINGS 628
628 The NVSRAM settings of controller %s(%s) are correct.\n \n

$ #define NVUTIL_ARRAYLIST_FAIL 629
629 The nvutil program cannot get the array list; nvutil failed.\n

$ #define INVALID_CTRL_NAME 630
630 Invalid controller name (%s) in nvutil command line; nvutil failed.\n

$ #define DISPLAY_NVRAM_SETTINGS 631
631 (%s)%-30s0x%02x%-20s0x%02x\n

$ #define NVUTIL_FAIL 632
632 nvutil command failed.\n \n

$ #define NVUTIL_SUCCESS 633
633 nvutil command succeeded.\n \n

$ #define NVUTIL_BAD_ARGS1 634
634 bad argument %s in nvutil command line, the form of an argument must be <offset=value>.\n

$ #define NVUTIL_BAD_ARGS2 635
635 bad argument %s in nvutil command line, the offset must be in the range 0-3f(hexadecimal integer).\n

$ #define NO_DEVICE 636
636 There are no devices (controllers) in the system; nvutil terminated.\n

$ #define NVUTIL_BAD_ARGS3 637
637  %s is an illegal value for NVSRAM setting.\n

$ #define MON_CONTROLLER_FAILURE 638
638 \nThe controller listed has detected that the alternate controller or connection has failed in %s. Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.

$ #define SC_INCORRECT_NVRAM_SETTINGS_FIX_FAILURE 639
639 \nThe attempt to fix NVSRAM settings of controller %s(%s) failed.

$ #define SC_INCORRECT_NVRAM_SETTINGS_FIX_SUCCESS 640
640 \nThe NVSRAM fix of controller %s(%s) succeeded. Please cycle the power on the module for the new settings to take effect.

$ #define SC_INCORRECT_NVRAM_SETTINGS 641
641 \nThe NVSRAM settings of controller %s(%s) are incorrect.

$ #define GET_VTOC_FAIL 642
642 Could not get VTOC, errno=%d(%s)\n

$ #define FUNC_STAT_LOGGING 643
643 %s (LUN %s) called by %s failed with status %x

$ #define PRINT_Signalrdm__USAGE 644
644 \n \nUsage: %s%s

$ #define PRINT_RDACUTIL_USAGE 645
645 \n \nUsage: %s%s%s%s%s%s%s

$ #define MODULELIST_FAIL 646
646 The %s cannot get the module list, %s failed!\n

$ #define BAD_CTRL_NAME 647
647 Invalid controller name %s.\n

$ #define BAD_MOD_NAME 648
648 Invalid module name %s.\n

$ #define SINGLE_CTRL_MODULE 649
649 There is only one good controller or no redundant controller in the module %s.\n

$ #define NO_CTRL_SPECIFIED 650
650 No controller specified.\n

$ #define BAD_MODE 651
651 %s is invalid mode.\n

$ #define INVALID_CONJUNCTION 652
652 -b valid only in conjunction with -m 2.\n

$ #define ARRAYLIST_FAIL 653
653 The %s cannot get the array list, %s failed!\n

$ #define UTIL_FAIL 654
654 \n%s failed!\n

$ #define UTIL_SUCCESS 655
655 \n%s succeeded!\n

$ #define NO_MODULE 656
656 \nThere are no modules in the system, %s terminated!\n

$ #define RDACUTIL_INFO_1 657
657 \n%s%-4s%s\n

$ #define RDACUTIL_INFO_2 658
658      %-10s%-13s%c%-22s%-10s

$ #define RDACUTIL_INFO_3 659
659 none\n

$ #define RDACUTIL_INFO_4 660
660 units:

$ #define SC_UNKNOWN_CTRL_TYPE 661
661 Warning: Controller %s (module: %s) is a model %s\ncontroller which is not compatible with this application.\n \n

$ #define SC_INCOMPATIBLE_SW_VER 662
662 The controller firmware version for controller %s (module: %s) is %s. The recommended firmware version for this application is %s or higher.\n

$ #define Signalrdm_MSG_1 663
663 Signalrdm <Signal>\n

$ #define Signalrdm_MSG_2 664
664        <Signal>::=kill_rdaemon | scan | unfail | print | kill_restart\n

$ #define BAD_DEVICE_NAME 665
665 Invalid device name:  %s. \n

$ #define SC_FAILED_ICON_NO_RECOVERY 666
666 The arraymon can't force a controller mode change after an ICON failure. If needed, call your Customer Support Representative.

$ #define RDAC_INIT_FAILURE 667
667 Error(s) occurred while initializing RDAC. You are running without redundant controller protection!\n

$ #define EVENT_AEN_3FD1_ACTION 668
668 You can enable write caching again, if you disabled it. Use the Maintenance/Tuning Application.

$ #define EVENT_AEN_3FD2_CAUSE 669
669 Synchronous transfer value differences between drives.

$ #define EVENT_AEN_3FD3_CAUSE 670
670 The software measured performance degradation.

$ #define EVENT_AEN_3FD4_CAUSE 671
671 Mode parameter differences between drives may cause performance degradation.

$ #define EVENT_AEN_3FE1_CAUSE 672
672 Multiple drives have failed.

$ #define EVENT_AEN_3FF1_CAUSE 673
673 There is a hard checksum error with the NVSRAM on the RAID controller.

$ #define EVENT_AEN_3FF2_CAUSE 674
674 The maximum write count has been exceeeded for the NVSRAM on the RAID controller.

$ #define EVENT_AEN_3FF8_CAUSE 675
675 The application software copy to the drive failed.

$ #define EVENT_AEN_40NN_CAUSE 676
676 The RAID controller has detected that one of its internal components has failed.

$ #define EVENT_AEN_5A00_5A03_CAUSE 677
677 One of the following has been detected by the RAID controller: 1. Operator request or state change input (5A00) or 2. Operator selected write permit (5A03).

$ #define EVENT_AEN_5B00_5B03_CAUSE 678
678 One of the following has been detected by the RAID controller: 1. Log exception (5B00), 2. Threshold condition met (5B01), 3. Log counter at maximum (5B02), or 4. Log list codes are all used (5B03).

$ #define EVENT_AEN_5C00_5C02_CAUSE 679
679 One of the following has been detected by the RAID controller: 1. RPL status change (5C00), 2. Spindles synchronized (5C01), or 3. Spindles not synchronized (5C02).

$ #define EVENT_AEN_8005_CAUSE 680
680 An AEN code was not loaded or an invalid AEN code was loaded by the application software.

$ #define EVENT_AEN_870B_CAUSE 681
681 The alternate controller has successfully uploaded the new firmware.

$ #define EVENT_AEN_870C_CAUSE 682
682 The RAID controller is downloading microcode to the disk.

$ #define EVENT_AEN_870D_CAUSE 683
683 The RAID controller is uploading microcode from the disk.

$ #define EVENT_AEN_8B02_CAUSE 684
684 I/O activity on the addressed logical unit(s) has been stopped. Redundant controller mode changes or logical unit ownership transfers will be, or already are in progress.

$ #define EVENT_AEN_8E01_8E03_CAUSE 685
685 The RAID controller detected inconsistent parity/data during a parity verification. The parity inconsistencies have been corrected.

$ #define EVENT_AEN_9502_CAUSE 686
686 The RAID controller detected the activation of signal(s) used to indicate that the alternate controller has been removed or replaced.

$ #define EVENT_AEN_A000_CAUSE 687
687 Write back caching is being suspended. This could be due to (1) a battery charging after a power cycle, (2) a battery failure/discharge, (3) a UPS two-minute warning, or (4) a controller not being able to mirror the cached data.

$ #define EVENT_AEN_A000_ACTION 688
688 If you power cycled the RAID Module, wait approximately 12 to 15 minutes. The caching should be enabled again. Also, check the message log for additional messages concerning batteries, UPS, or AC Power. Also, make sure that both controllers are operational.

$ #define EVENT_AEN_A100_CAUSE 689
689 Write caching with mirroring cannot be enabled because the two RAID controllers' cache sizes do not match.

$ #define EVENT_AEN_A100_ACTION 690
690 Make sure both controllers in the module have the same cache size. You also have the option of specifying write caching only instead of write cache mirroring using the Maintenance/Tuning Application.

$ #define EVENT_AEN_C000_CAUSE 691
691 The inter-controller communciation (ICON) chip has failed. A switch to active/active mode of the controllers will not be allowed.

$ #define EVENT_AEN_3FD0_CAUSE 692
692 The RAID controller has detected that its battery is no longer charged.

$ #define EVENT_AEN_3FD0_ACTION 693
693 If you have the cache without batteries option enabled, disable it (use the Maintenance/Tuning Application) unless you have back up support through a UPS. If you don't have a UPS and a power failure occurs, any user data in cache will be lost.

$ #define EVENT_AEN_3FD1_CAUSE 694
694 The RAID controller has detected that its battery is now fully charged and is capable of retaining the data in the cache if a power failure occurs.

$ #define READ_LINK_FAIL 695
695 Could not read link from %s,  errno=%d(%s)\n

$ #define RENAME_LINK_FAIL 696
696 Could not rename %s(ModuleDevName=%s) to %s, errno=%d(%s)\n

$ #define ST_LUNST_DEGRADED_HS 697
697 Degraded (Hot Spare In Use)

$ #define ST_LUNST_OPTIMAL_HS 698
698 Optimal (Hot Spare In Use)

$ #define ST_DET_MSG_AFF_LBL10 699
699 Affected Component: Disk Drive Tray\n

$ #define RDACUTIL_MSG_5 700
700        rdacutil -U <raid controller specifier>\n

$ #define PROF_MSG_47 701
701 Unresponsive

$ #define SUMMARY_REPORT_HEADER 707
707 Summary Report

$ #define MODULE_NOTREGISTERED_HEADER 780
780 RAID Module Not Recognized

$ #define MODULE_NOTREGISTERED_TEXT 781
781 %s is no longer recognized by the software. Select OK to\nexit this recovery procedure.

$ #define ONE_CONTROLLER_FAILURE_TEXT1 782
782 One of the controllers in %s has failed.\n \nStop all I/Os to the affected LUNs and,\nif applicable, unmount the filesystems.

$ #define PLACE_CONTROLLER_ONLINE_HEADER 783
783 Placing Controller Online

$ #define PLACE_CONTROLLER_ONLINE_TEXT 784
784 Placing controller online. Please wait...

$ #define RU_INVALID_LUN_NUMBER 790
790 Invalid LUN number (%d), must be 0-%d\n

$ #define DATA_PATH_SCSIOPFAIL_RETRYGURU 800
800 An array operation failed - possible hardware fault.\nStart the Recovery Guru again.

$ #define DATA_PATH_NVRAM_CHANGED 801
801 The replaced controller's NVSRAM settings have been changed.\nPower cycle the RAID Module at your earliest convenience.

$ #define DATA_PATH_NVRAM_CHANGED_HEADER 807
807 NVSRAM Settings Changed

$ #define HOTSPARE_COPY_HEADER 810
810 Copy In Progress

$ #define HOTSPARE_COPY_TEXT 811
811 Data from the hot spare drive is being copied to the new replacement drive.

$ #define NOT_CREATE_HOTSPARE_TEXT 812
812 Unable to create. The maximum number\nof hot spare drives has been created.

$ #define CREATE_HOTSPARE_HEADER 813
813 Create Hot Spares

$ #define RESET_CONFIG_CONFIRM_AGAIN 814
814 WARNING:  Because this option will destroy ALL data,\nplease verify that you really want to reset the configuration.

$ #define DELETE_CONFIRM_HEADER 815
815 Confirm Delete

$ #define DELETE_CONFIRM_HOTSPARE_TEXT 816
816 Delete hot spare drive? This will return\nthe drive to an unassigned status.

$ #define DELETE_CONFIRM_HOTSPARES_TEXT 817
817 Delete hot spare drives? This will return\nthe drives to an unassigned status.

$ #define SELECT_INFO_HEADER 818
818 Select Information

$ #define FWDL_CORRUPTED_FILE_ERROR 837
837 The firmware file(s) you have selected are either\ncorrupted or not firmware file(s).

$ #define FWDL_COMPAT_TWO_OR_MORE_ERROR 838
838 Two or more of the same\ntype of file was specified.

$ #define FWDL_COMPATABILITY_ERROR 839
839 The specified files are not\ncompatible.\n \nContinue?

$ #define FWDL_DOWNLOADABILITY_ERROR 840
840 The specified file(s) are not compatible\nwith the current firmware on the controller(s).\n \nContinue?

$ #define FWDL_FWCOMPARE_ERROR 841
841 The file (fwcompat.def) could not be found.\n \nThis file is needed for identifying\ncompatibility between various files.\nIf it is not on your system, it can be found\non the firmware distribution diskette(s).

$ #define FWDL_FILE_NOT_SPECIFIED_ERROR 842
842 Path does not exist or no files\nwere specified for downloading.

$ #define FWDL_LUNS_NOT_OPTIMAL_ERROR 843
843 It has been detected that all of the RAID\nModules have a LUN(s) in a state that\nis unacceptable for the firmware upgrade.\nAll LUNs must be Optimal before the\nupgrade can begin.\n \nSelect OK to exit Firmware Upgrade.

$ #define FWDL_OFFLINE_SWITCHOVER_ERROR 844
844 The upgrade type must be set to OFFLINE when\nattempting to upgrade the controller firmware\nfrom a pre-2.03 version to a post-2.03 version.\n \nContinue with OFFLINE upgrade?\n(All I/O's stopped)

$ #define FWDL_NO_GOOD_CONTROLLERS_ERROR 845
845 The controllers could not be accessed\non the selected RAID module.

$ #define FWDL_COMPATABLE_DOWNLOAD_ERROR 846
846 The file(s) selected for downloading are not\ncompatible with the current firmware versions\non the controllers.\n \nContinue?

$ #define FWDL_DOWNLOAD_JUMP_ERROR 847
847 The current firmware versions on one or both of\nthe controllers are not capable of an upgrade to\nthe specified firmware file(s). An intermediate\nfirmware download is required. Refer to the\nFirmware Specifications section in the Installation\nand Support Guide for the firmware files upgrade path.\n \nContinue?

$ #define FWDL_LUN_STATE_ERROR 848
848 It has been detected that\n%s has a LUN(s) in a\nstate that is unacceptable for the\nfirmware upgrade.  All LUNs on the\nRAID Module must be Optimal before\nthe upgrade can begin.\n \nSelect OK to exit Firmware Upgrade.

$ #define FWDL_OFFLINE_ALL_MODULE_ERROR 849
849 It has been detected that all\nRAID Modules are still receiving\nI/O. You must stop I/O to the\ntarget RAID Module(s) before the\nupgrade can begin.\n \nSelect OK to exit Firmware Upgrade.

$ #define FWDL_OFFLINE_IO_ERROR 850
850 It has been detected that\n%s is still receiving\nI/O. You must stop I/O to this RAID\nModule before the upgrade can begin.\n \nSelect OK to exit Firmware Upgrade.

$ #define FWDL_FWFILE_HEADER 851
851 Firmware File Error

$ #define FWDL_FWFILE_INCOMPAT_HEADER 852
852 File Incompatability

$ #define FWDL_FILE_NOT_FOUND_HEADER 853
853 File Not Found

$ #define FWDL_UPGRADE_RESTRICT_HEADER 854
854 Upgrade Restriction

$ #define FWDL_UPGRADE_ERROR_HEADER 855
855 Upgrade Error

$ #define FWDL_OFFLINE_UPGRADE_TITLE 856
856 Offline Firmware Upgrade

$ #define FWDL_ONLINE_UPGRADE_TITLE 857
857 Online Firmware Upgrade

$ #define FWDL_FWFILE_NOT_SPEC_HEADER 858
858 File Not Specified

$ #define FWDL_START_ALL_OFFLINE_UPGRADE 859
859 The offline upgrade is about to start\non All RAID Modules.\n \nOK to proceed?

$ #define FWDL_START_OFFLINE_UPGRADE 860
860 The offline upgrade is about to start.\n \nOK to proceed?

$ #define FWDL_START_ALL_NONLINE_UPGRADE 861
861 The online upgrade is about to start\non All RAID Modules. Any single\ncontroller modules in the list will not\nhave the files downloaded to them.\n \nOK to proceed?

$ #define FWDL_START_NONLINE_UPGRADE 862
862 The online upgrade is about to start.\n \nOK to proceed?

$ #define FWDL_PRERELEASE_UPGRADE 863
863 One of the firmware files is not recognized. It may be a\npre-release version of firmware or an NVSRAM file.\nTherefore, no compatibility checking will be performed.\n \nContinue?

$ #define STOP_IO_HEADER 864
864 Stop I/O

$ #define STOP_IO_TEXT 865
865 Stop all I/Os and, if applicable, unmount the\nfilesystems on %s.

$ #define ST_HLP_TXT1 866
866 Information In Message Log

$ #define ST_HLP_TXT2 867
867 Information In Show Details

$ #define ST_HLP_TXT3 868
868 Action For Modules With Exceptions Detected

$ #define ST_HLP_TXT4 869
869 What Statuses Appear In Health Check?

$ #define ST_LST_TYPE_HDR 870
870 List Types

$ #define SNMP_1 871
871 Data/parity mismatch - repair successful

$ #define SNMP_2 872
872 Controller or connection failure

$ #define SNMP_3 873
873 Attempt to recover from bad ICON failed

$ #define SNMP_4 874
874 Unrecovered write error

$ #define SNMP_5 875
875 Drive failed - unrecovered write error

$ #define SNMP_6 876
876 Drive failed - sector reassign failed

$ #define SNMP_7 877
877 Drive failed - reconstruction failure

$ #define SNMP_8 878
878 Drive warned - reconstruction failed

$ #define SNMP_9 879
879 Drive failed - H/W diagnostics failure

$ #define SNMP_10 880
880 Drive failed - unresponsive drive

$ #define SNMP_11 881
881 Drive failed - FORMAT UNIT failure

$ #define SNMP_12 882
882 Drive failed - user failed

$ #define SNMP_13 883
883 Drive failed - deferred drive error

$ #define SNMP_14 884
884 Drive failed - wrong drive replaced

$ #define SNMP_15 885
885 Drive failed - drive capacity < minimum

$ #define SNMP_16 886
886 Drive failed -drive has wrong block size

$ #define SNMP_17 887
887 Drive failed - DACSTORE failure

$ #define SNMP_18 888
888 Drive failed - unrecovered R/W

$ #define SNMP_19 889
889 Drive warned - deferred drive error

$ #define SNMP_20 890
890 Drive failed - faulty drive connection

$ #define SNMP_21 891
891 Drive failed - drive no longer present

$ #define SNMP_22 892
892 Module component failure or not installed

$ #define SNMP_23 893
893 AC power loss or operating on UPS

$ #define SNMP_24 894
894 Two minutes till loss of all power

$ #define SNMP_25 895
895 Low UPS battery power

$ #define SNMP_26 896
896 Normal AC power has been restored

$ #define SNMP_27 897
897 Write-cache battery discharged

$ #define SNMP_28 898
898 Write-cache battery charge completed

$ #define SNMP_29 899
899 LUN failure

$ #define SNMP_30 900
900 LUN failure - multiple drives failed

$ #define SNMP_31 901
901 LUN failure - mode parameter mismatch

$ #define SNMP_32 902
902 LUN failure -channel verification failed

$ #define SNMP_33 903
903 LUN failure - ID verification failed

$ #define SNMP_34 904
904 LUN failure - wrong drive was replaced

$ #define SNMP_35 905
905 LUN failure - multi-component failure

$ #define SNMP_36 906
906 Controller NVSRAM problem

$ #define SNMP_37 907
907 NVSRAM checksum error

$ #define SNMP_38 908
908 NVSRAM write count exceeded

$ #define SNMP_39 909
909 Firmware copy to multiple drives failed

$ #define SNMP_40 910
910 Component failure - processor RAM

$ #define SNMP_41 911
911 Component failure - RAID buffer

$ #define SNMP_42 912
912 Component failure - NVSRAM

$ #define SNMP_43 913
913 Component failure - RPA chip

$ #define SNMP_44 914
914 Battery-backed NVSRAM or clock failure

$ #define SNMP_45 915
915 Selftest failed -non-data-path component

$ #define SNMP_46 916
916 Selftest failed - data-path component

$ #define SNMP_47 917
917 Selftest failed - R/W buffer turnaround

$ #define SNMP_48 918
918 Selftest failed - drive inquiry

$ #define SNMP_49 919
919 Selftest failed - drive R/W turnaround

$ #define SNMP_50 920
920 Selftest failed - drive selftest

$ #define SNMP_51 921
921 Invalid AEN code sent by firmware

$ #define SNMP_52 922
922 Code cannot be saved to disk

$ #define SNMP_53 923
923 Code upload failed

$ #define SNMP_54 924
924 NVSRAM command error

$ #define SNMP_55 925
925 Subsystem configuration error

$ #define SNMP_56 926
926 Controller detected data/parity mismatch

$ #define SNMP_57 927
927 Controller remove/replace detected

$ #define SNMP_58 928
928 Write-cache disabled - low battery

$ #define SNMP_59 929
929 Write-cache disabled - size mismatch

$ #define SNMP_60 930
930 ICON failure

$ #define SNMP_61 931
931 Wrong NVSRAM settings - repair failed

$ #define SNMP_62 932
932 Wrong NVSRAM settings - repair successful

$ #define SNMP_63 933
933 Invalid software version detected

$ #define SNMP_64 934
934 RDAC initialization failure

$ #define SNMP_65 935
935 Battery failed - expiration date reached

$ #define SNMP_66 936
936 Battery near expiration date

$ #define SNMP_67 937
937 Drive failed - incorrect parameters

$ #define DEVICE_SCAN_HEADER 938
938 Device Scan

$ #define FAILED_LUN_CREATE 939
939 Failed LUN Creation

$ #define SUBSYSTEM_COMPONENT_REPLACE_FIRST1 940
940 \nfan or power supply is functional. Until then, running\nhealth check or the Recovery Guru may still report a fan or\npower supply failure.

$ #define LUN_CREATE_ERROR_HEADER 941
941 LUN Creation Error

$ #define LUN_0MB_NOCREATE 942
942 A LUN of 0 MB capacity cannot be created.\nPlease correct before continuing.

$ #define CREATE_OPTIONS_HEADER 943
943 Create Options

$ #define CREATE_HOTSPARE_OPTIONS_HEADER 944
944 Create Hot Spare -- Options

$ #define LOCATE_HEADER 945
945 Locate

$ #define RESET_HEADER 946
946 Reset Configuration

$ #define CONFIRM_RESET_HEADER 947
947 Confirm Reset

$ #define NO_RAIDMODULE_HEADER 948
948 No RAID Modules

$ #define NO_RESET_HEADER 949
949 Unable To Reset\n

$ #define RESET_COMPLETE_HEADER 950
950 Reset Complete

$ #define EVENT_4500_CAUSE 956
956 A selection time-out occurred on a drive channel.

$ #define EVENT_9136_CAUSE 957
957 A mode select was attempted while another was already active.

$ #define EVENT_AEN_2A01_CAUSE 958
958 The controller received a request from another initiator to change the mode parameters for the addressed logical unit.

$ #define EVENT_9100_CAUSE 959
959 Mode select errors.

$ #define EVENT_9103_CAUSE 960
960 Drive already exists; cannot do Add Drive Function 80.

$ #define EVENT_2600_CAUSE 961
961 Invalid field in parameter list.

$ #define EVENT_2500_CAUSE 962
962 The addressed logical unit is currently not configured.

$ #define EVENT_8400_CAUSE 963
963 The operation cannot be completed with the logical unit in its current state.

$ #define EVENT_9401_CAUSE 964
964 Invalid request because of current logical unit ownership.

$ #define EVENT_9101_CAUSE 965
965 Logical unit already exists; cannot do Add LUN Function 80.

$ #define EVENT_0402_CAUSE 966
966 Logical unit not ready; initializing command required.

$ #define EVENT_0401_CAUSE 967
967 Logical unit is in the process of becoming ready.

$ #define EVENT_A400_CAUSE 968
968 The capacity of the hot spare drive is not large enough to cover all of the drives in the RAID Module. If a drive with a capacity larger than the hot spare drive fails, the hot spare drive will not take over for it.

$ #define EVENT_9109_CAUSE 969
969 An operation was requested that cannot be performed because more than one logical unit is defined on the drive group.

$ #define EVENT_9104_CAUSE 970
970 The drive does not exist; therefore, the requested action cannot be performed.

$ #define EVENT_8700_CAUSE 971
971 The controller detected an error while downloading firmware and storing it in non-volatile memory.

$ #define EVENT_0000_CAUSE 972
972 The controller does not have sense data available for the requesting host and addressed logical unit combination.

$ #define EXIT_CONFIGURATION_TITLE 973
973 Exit Configuration

$ #define EXIT_CONFIGURATION_HEADER 974
974 Confirmation

$ #define EXIT_CONFIGURATION_TEXT 975
975 There are logical units (LUNs) currently formatting.\n \nYou should not exit Configuration while LUNs\nare formatting. If you exit and then restart\nConfiguration, the LUNs will not be visible on\nthe screen until after the format completes.

$ #define STARTUP_PARAMFILE_MISSING 984
984 The parameter file %s is not present - obtain a copy from\nthe installation media, or from a back up.\n

$ #define RU_GHS_1 985
985 Too many drives specified in list following -%s.\n

$ #define RU_GHS_2 986
986 A drive following -h option does not have an unassigned status.\n

$ #define RU_GHS_3 987
987 WARNING:  Some configured LUNs contain drives with capacities\nlarger than the just configured hot spare.\n

$ #define RU_GHS_4 988
988 A drive following the -h option has a capacity smaller\nthan all drives in the configured LUNs, or the maximum \nnumber of hot spares has been reached.\n

$ #define RU_GHS_5 989
989 A drive following the -H option does not have a hot spare\nstatus and therefore cannot be deleted.\n

$ #define RU_GHS_6 990
990 %s hot spare operation failed.  Status = %d\n

$ #define RU_VIEW_1 991
991 \n\n\tMode Sense Page 08 LUN %d

$ #define RU_VIEW_2 992
992 \nWCE                                 %4x

$ #define RU_VIEW_3 993
993 \nMF                                  %4x

$ #define RU_VIEW_4 994
994 \nRCD                                 %4x

$ #define RU_VIEW_5 995
995 \nDemand Read Retention Priority      %4x

$ #define RU_VIEW_6 996
996 \nWrite Retention Priority            %4x

$ #define RU_VIEW_7 997
997 \nDisable Pre-fetch Transfer Length   %4x

$ #define RU_VIEW_8 998
998 \nMinimum Pre-fetch                   %4x

$ #define RU_VIEW_9 999
999 \nMaximum Pre-fetch                   %4x

$ #define RU_VIEW_10 1000
1000 \nMaximum Pre-fetch Ceiling           %4x\n\n

$ #define REC_DL_SUCCESS 1001
1001 Successful

$ #define REC_DL_FAIL_IO 1002
1002 Failed -- Module had I/O activity occurring\n%sor filesystem(s) mounted

$ #define REC_DL_FAIL_FILECONTENTS 1003
1003 Failed -- Bad file contents

$ #define REC_DL_FAIL_WRITEBUFFER 1004
1004 Failed -- Write Buffer command failed

$ #define REC_DL_FAIL_RESET 1005
1005 Failed -- Could not reset controller

$ #define REC_DL_FAIL_UNKNOWN 1006
1006 Failed -- Unknown failure. The possible cause for\n%sthis failure may be shown in the Status\n%sApplication.

$ #define REC_DL_FAIL_LUNOP 1007
1007 Failed -- LUN(s) not optimal

$ #define REC_DL_FAIL_ROLLINGUP 1008
1008 Failed -- Upgrading to version 2.03 requires the\n%soffline method

$ #define REC_DL_FAIL_CONTFAIL 1009
1009 Failed -- Controllers could not be accessed

$ #define REC_DL_FAIL_COMPAT 1010
1010 Failed -- Files not compatible with current\n%sversion(s) on controller

$ #define REC_DL_FAIL_UPGRADABLE 1011
1011 Failed -- Current version not able to upgrade to\n%sspecified firmware file. An intermediate\n%sfirmware download may be required.

$ #define REC_DL_CAUTION 1012
1012 CAUTION:

$ #define REC_DL_INSTRUCTION 1013
1013 If any status is Failed, fix the specified failure and then start the download procedure again.

$ #define REC_DL_HEADER 1014
1014 Upgrade Complete -- Summary Report for file(s):  %s  %s  %s

$ #define REC_DL_BIGINSTRUCTION 1015
1015 Highlight files to download.\nThese files are listed in\ncompatible groups.  If the\nfiles are not displayed or\nyou want to download an\nNVSRAM file, then enter a\npath and/or file(s) in the\nPath area. For firmware\nfiles, you can specify\n

$ #define REC_DL_BIGINSTRUCTION2 1016
1016 multiple files in the same\npath by using a "+"\nbetween the files.

$ #define REC_DL_FWCOMPAT 1017
1017 fwcompat.def

$ #define REC_RECONTITLE 1018
1018 Reconstruct Drive

$ #define REC_RECONCONFIRM 1019
1019 Confirm Reconstruct

$ #define REC_RECONMSG 1020
1020 To view the reconstruction progress, go\nto the Status Application.

$ #define REC_RECONERROR 1021
1021 An error occurred while attempting\nto start reconstruction on the drive\nat location %s.

$ #define REC_DRIVETITLE 1022
1022 Manual Recovery -- Drives

$ #define REC_UNKNOWN 1029
1029 Unknown

$ #define REC_ALL_MODULES 1030
1030 All RAID Modules

$ #define REC_LUNOPTIMAL 1031
1031 Optimal

$ #define REC_LUNFORMATTING 1032
1032 Formatting

$ #define REC_LUNDEGRADED 1033
1033 Degraded

$ #define REC_LUNRECON 1034
1034 Reconstructing

$ #define REC_LUNDEAD 1035
1035 Dead

$ #define REC_CONTTITLE 1036
1036 Manual Recovery -- Controller Pairs

$ #define REC_CONTOFFLINE 1037
1037 Offline

$ #define REC_CONTOPTIMAL 1038
1038 Optimal

$ #define REC_CONTDEAD 1039
1039 Dead

$ #define REC_LUNTITLE 1040
1040 Manual Recovery -- Logical Units

$ #define REC_PARITYTITLE 1041
1041 Manual Parity Check/Repair

$ #define REC_HELPHOMEPAGE 1042
1042 Home Page

$ #define REC_HELPHELP 1043
1043 Help

$ #define REC_HELPERROR 1044
1044 The help system cannot be used because some\nhelp files are missing or corrupted.

$ #define REC_STATFLASH 1045
1045 Flash drive lights on the RAID Module.

$ #define REC_STATPROF 1046
1046 Receive information on the controllers, drives, and LUNs in the RAID Module.

$ #define REC_FAILTITLE 1047
1047 Fail Drive

$ #define REC_FAILHEADER 1048
1048 Confirm Fail

$ #define REC_FAILMSG 1049
1049 WARNING:  You may lose data\nredundancy or destroy data!\n \nFail drive(s) at the following location(s)?\n%s

$ #define REC_FAILERROR 1050
1050 Unable to fail drive %s, because either:\n1) A LUN or group is being modified, or\n2) A failure has occurred along the connection.\n \n- If a LUN or group is being modified, wait until the operation has\ncompleted.\n- If a failure has occurred, run the Recovery Guru and fix the problem. 

$ #define REC_REVIVETITLE 1051
1051 Revive Drive

$ #define REC_REVIVEHEADER 1052
1052 Confirm Revive

$ #define REC_REVIVEMSG 1053
1053 NOTE:  Revive a drive ONLY if you\nare instructed to do so in a Recovery\nprocedure.\n \nWARNING:  Using this option may\nresult in data corruption on any\nassociated LUN(s) with a dead status.\n \nRevive drive(s) at the following location(s)?\n%s

$ #define REC_REVIVEERROR 1054
1054 An error occurred while attempting\nto revive the drive at location %s.

$ #define REC_REVIVECOMPLETE 1055
1055 Revive Complete

$ #define REC_REVIVECOMPMSG 1056
1056 Check the parity on the LUNs (except RAID 0)\nassociated with the revived assigned drive(s)\nby selecting Manual Parity Check/Repair\nin the Recovery Application.

$ #define REC_HELPMANREC 1057
1057 Manual Recovery For Drives

$ #define REC_HELPMISSERROR 1058
1058 The help system cannot be used because some\nhelp files are missing or corrupted.

$ #define REC_FORMATTITLE 1059
1059 Format Logical Unit

$ #define REC_FORMATHEADER 1060
1060 Confirm Format

$ #define REC_FORMATMSG 1061
1061 WARNING:  Formatting will destroy all data on\nthe LUNs you have selected!\n \nNOTE: You cannot perform any other recovery\ntasks until the format has completed.\n \nFormat the following logical unit(s)?\n%s

$ #define REC_FORMATERROR 1062
1062 Could not format LUN(s) %s because either: \n \n1) an application is using those LUNs, \n2) a filesystem is mounted on those LUNs, \n3) another host has the LUNs reserved, \n4) one or more failed drives in a Dead LUN have not been replaced, \n5) a connection failure has occurred, or \n6) a modification operation (capacity expansion, RAID level change, \nsegment size change, or defragmentation) is in progress. \n \nTo help pinpoint the exact cause, observe any fault lights and refer to the \nMessage Log in the Status Application for possible failure entries.\n \nFor causes 1-3, either wait for the application to finish, unmount the filesystem, \nor have the other host release the LUNs and then retry the format. Note that \nsome operating systems require you to reboot the system to unmount a filesystem.\n \nFor causes 4 and 5, run the Recovery Guru to verify and fix the problem before \nretrying the format. \n \nFor cause 6, if you were attempting to format a LUN that transitioned to Dead \nduring a modification operation, run the Recovery Guru. Otherwise, wait for \nthe modification operation to complete and retry the format.

$ #define REC_FORMATCOMPLETE 1063
1063 Format Complete

$ #define REC_FORMATCOMPMSG 1064
1064 Format is complete. The LUN(s) are now\nusable, you can back up from tape.

$ #define REC_REVIVELUNTITLE 1065
1065 Revive Logical Unit

$ #define REC_REVIVELUNHEADER 1066
1066 Confirm Revive

$ #define REC_REVIVELUNMSG 1067
1067 WARNING:  Reviving a logical unit may cause data\ncorruption on the LUNs in the drive group!\n \nRevive the following logical unit(s)?\n%s

$ #define REC_REVIVELUNERROR 1068
1068 An error occurred while attempting to revive LUN(s) %s.\nDepending on the error that occurred and the status of the\ndrives in the LUN(s), part of the operation may have\nworked. Therefore, check the status of the LUNs and drives\nusing the applicable Options >> Manual Recovery choices.

$ #define REC_REVIVELUNCOMPLETE 1069
1069 Revive Complete

$ #define REC_REVIVELUNCOMPMSG 1070
1070 Check the parity on the revived LUNs (except\nRAID 0) by selecting Manual Parity Check\nand Repair in the Recovery Application.

$ #define REC_HELPMANRECLUNS 1071
1071 Manual Recovery For LUNs

$ #define REC_CONTPLACEOFFLINE 1072
1072 Place Controller Offline

$ #define REC_CONTCONFIRMOFFLINE 1073
1073 Confirm Offline

$ #define REC_CONTOFFLINEMSG 1074
1074 Place controller %s offline?

$ #define REC_OFFLINECOMPLETE 1075
1075 The controller has been placed offline.\n \nYou can remove it if desired.\n \nCAUTION:  Wait at least 1 minute\nbefore inserting a new controller.\n \nOnce you insert a new controller,\nplace it online using the Place\nOnline option.

$ #define REC_OFFLINEERROR 1076
1076 An error occurred while attempting to\nplace controller %s offline.

$ #define REC_CONTONLINE 1077
1077 Place Controller Online

$ #define REC_CONTCONFIRMONLINE 1078
1078 Confirm Online

$ #define REC_CONTONLINEMSG 1079
1079 Place controller %s online?

$ #define REC_ONLINECOMPLETE 1080
1080 The controller has been placed online.

$ #define REC_ONLINEERROR 1081
1081 An error occurred while attempting to place\ncontroller %s online.\n \nMake sure that the controller is inserted\ncorrectly and that cables are secure.  Retry\nthe operation.  If you still have a problem,\ncheck the section "Troubleshooting, Replacing\nControllers", in the installation guide.

$ #define REC_HELPCONTPAIRS 1082
1082 Manual Recovery For Controller Pairs

$ #define REC_PARITYCHECKREPAIR 1083
1083 Parity Check/Repair

$ #define REC_PARITYCANCELED 1084
1084 Parity Canceled

$ #define REC_PARITYMSG 1085
1085 The parity operation has been canceled.

$ #define REC_PARITYERROR 1086
1086 A manual parity scan on LUN %d was terminated because of an\nerror. Typically, the error is caused by a LUN that changed from an\n optimal state to a degraded state or that had a change in controller ownership.

$ #define REC_PARITYCOMPLETE 1087
1087 Parity Complete

$ #define REC_PARITYINC 1088
1088 Parity inconsistencies were found and\nrepaired on:\n%s.\n \nSelect Message Log in the Status\nApplication to determine the range and\nnumber of repaired data blocks.

$ #define REC_PARITYNOINC 1089
1089 No parity inconsistencies were found.

$ #define REC_HELPPARCHECKREPAIR 1090
1090 Information In Manual Parity Check/Repair

$ #define REC_STATGURU 1091
1091 Obtain step-by-step instructions to recover from a failure.

$ #define REC_STATPARITYCHECKREPAIR 1092
1092 Manually check and repair parity.

$ #define REC_STATSAVEPROF 1093
1093 Save the information in the module profile to a file.

$ #define REC_STATSAVEPROFGRAY 1094
1094 This option is not available because you chose the All RAID Modules selection.

$ #define REC_STATQUIT 1095
1095 Quit the Recovery Application.

$ #define REC_STATMANREC 1096
1096 Perform manual recovery.

$ #define REC_STATDRIVES 1097
1097 Perform manual recovery procedures on drives.

$ #define REC_STATLUNS 1098
1098 Perform manual recovery procedures on logical units.

$ #define REC_STATCONT 1099
1099 Perform manual recovery procedures on redundant controllers.

$ #define REC_STATFILE 1100
1100 Save Module profile information or exit.

$ #define REC_STATOPTIONS 1101
1101 Perform various recovery options.

$ #define REC_STATHELP 1102
1102 Get help on the Recovery Application.

$ #define REC_HELPGURU 1103
1103 Information In Recovery Guru

$ #define REC_HELPFILENAME 1104
1104 helprecv.txt

$ #define REC_RECONNOTE 1105
1105 NOTE:  Reconstruction normally occurs\nautomatically after you replace a drive.  Use\nthis option only if reconstruction has not\nstarted automatically.

$ #define REC_RECONCONFIRMLIST 1106
1106 Reconstruct drive(s) at the following location(s)?\n%s

$ #define REC_ONLINEREDISTERROR 1107
1107 An error occurred while attempting to\nredistribute LUNs to controller %s.\n \nGo to the Maintenance/Tuning application\nto manually redistribute the LUNs.

$ #define REC_DL_FAIL_ONECONT 1108
1108 Failed -- Only one controller exists or one\n%scontroller in pair not accessible

$ #define REC_DL_FAIL_ADPCONT 1109
1109 Failed -- ADP-93 controllers not upgradable online

$ #define FWDL_ONEGOODCONT_ERROR 1110
1110 One or both controllers in the selected\nRAID Module is not accessible.

$ #define FWDL_ADPCONT_ERROR 1111
1111 ADP-93 controllers cannot be upgraded ONLINE.\n \nContinue with OFFLINE upgrade?

$ #define FWDL_CONTCODEMISMATCH_ERROR 1112
1112 The selected firmware file(s) are not\ncompatible with the type of controller\nmodel(s) on the selected RAID Module.

$ #define REC_DL_FAIL_CONTCODEMISMATCH 1113
1113 Failed -- Selected firmware file(s) not compatible\n%swith controller model(s)

$ #define DPATH_FIRMWARE_MISMATCH_HEADER 1114
1114 Different Firmware Versions

$ #define DPATH_FIRMWARE_MISMATCH_TEXT 1115
1115 The controller replacement is complete.\n \nHowever, the firmware versions on the two controllers\ndo not match. Press OK to begin the firmware\nupgrade procedure.

$ #define DPATH_FIRMWARE_MISMATCH_STILL_TEXT 1116
1116 Firmware download succeeded, but there still is a firmware mismatch.\nPress OK to start firmware upgrade again.

$ #define CREATE_HS_ERR_MSG 1117
1117 An error occurred while creating hot spare %s.\n

$ #define CREATE_HS_INVALID_DEVICE_MSG 1118
1118 \nInvalid device.

$ #define CREATE_HS_SMALL_DRIVE_WARNING 1119
1119 \nA hot spare drive has been created using the drive at location\n%s. However, this drive has a smaller capacity (%ld) than some\nof the drives in the RAID Module. It will not be able to\ntake over if one of those drives fails.\n(Note that drive capacity differences can be caused by\ndrive firmware version discrepancies. Refer to Module Profile). 

$ #define CREATE_HS_SMALL_DRIVE_ERROR 1120
1120 \nThis drive was not made a hot spare because it has a smaller\ncapacity (%ld) than ALL of the assigned drives in the module.\n(Note that drive capacity differences can be caused by\ndrive firmware version discrepancies. Refer to Module Profile).
 
$ #define REC_DRIVEUNRESPONSIVE 1121
1121 Unresp.

$ #define FWDL_DOWNGRADE_ERROR 1122
1122 Going from a post-2.03 controller firmware version\nto a pre-2.03 version is not supported in a dual\ncontroller configuration.

$ #define REC_DL_FAIL_DOWNGRADE 1123
1123 Failed -- Pre-2.03 version not supported\n%sin dual controller configuration

$ #define REC_DL_FAIL_REDIST 1124
1124 Failed -- However, all files selected may have\n%sdownloaded. Go to Module Profile to\n%sview firmware levels. Also, all LUNs on\n%sone controller. Go to Maintenance/Tuning\n%sto balance LUNs.

$ #define REC_DL_FAIL_BRINGONLINE 1125
1125 Failed -- Unable to bring controller back to active\n%smode. Firmware on controllers are not the\n%ssame version.

$ #define SYSLOGF_TOO_MANY_MERGE 1126
1126 syslogfilter: too many merge specifications (%d is max)\n

$ #define SYSLOGF_TOO_MANY_FILTER 1127
1127 syslogfilter: null strings are not allowed for merge or filter specifications\n

$ #define SYSLOGF_INVALID_FILTER 1128
1128 syslogfilter: null strings are not allowed for merge or filter specifications\n

$ #define SYSLOGF_NO_PIPE_SPEC 1129
1129 syslogfilter: The pipe file must be specified\nUsage: syslogfilter -p {pipe file} [-m {merge string}] {filter string}\n

$ #define SYSLOGF_NONEXISTENT_PIPE 1130
1130 syslogfilter: The pipe file must exist\n

$ #define SYSLOGF_NO_FILTERS 1131
1131 syslogfilter: At least one filter specification must be specified\nUsage: syslogfilter -p {pipe file} [-m {merge string}] {filter string}\n

$ #define SYSLOGF_PIPE_INACCESSIBLE 1132
1132 syslogfilter: can't open pipe

$ #define REC_FAILED_MAYBE_DATA_PATH 1133
1133 The recovery procedure failed because of a possible data\npath failure. Rerun the Recovery Guru.

$ #define REC_FAILED_SCSI_PROBLEMS 1134
1134 Could not complete the recovery procedure. Possible\ncauses include a command timeout, or a temporary\ndisturbance on the communications channel. If you are\nreplacing a drive, the replacement drive could be bad.\n

$ #define GENWARN_PASSTHROUGH_NOT_DEFINED 1135
1135 The parameter %s is not defined in the %s file. Please\nupdate the rmparams file and retry the operation.

$ #define GENWARN_PASSTHROUGH_NOT_AVAILABLE 1136
1136 The LUN defined in parameter %s\nin %s either does not exist or is being\nused by another program. Please set the parameter\nto an existing LUN that is unused.

$ #define GENWARN_GENERAL_IO_ERROR 1137
1137 An attempt to communicate with a controller of %s has failed.\nRun the Recovery Guru to check for possible controller failure,\nand then retry the operation.

$ #define GENWARN_UNKNOWN_ERROR 1138
1138 An unexpected error occurred on %s. Check the event log for\nmore information.

$ #define REC_FAILED_SCSI_PROBLEMS_2 1139
1139 Re-run the Recovery Guru. If this problem persists, call\nyour Customer Support Representative.

$ #define CFG_DELHOTSPFAIL 1140
1140 Could not delete the hot spare at location [%d,%d],\nbecause either:\n1) A LUN or group is being modified, or\n2) A  failure has occurred along the connection.\n \n - If a LUN or group is being modified, wait until the operation\nhas completed.\n - If a failure has occurred, run the Recovery Guru and fix the\nproblem.

$ #define ABOUT_BOX_NETWORK_VERSION 1141
1141 Networked Version  

$ #define ABOUT_BOX_SCSI_VERSION 1142
1142  

$ #define EVENT_AEN_3FC7_FRU08_CAUSE 1143
1143 (1) A component other than a drive has failed or is not installed (for example, fan, power supply, battery, environmental card) and/or (2) There is an over-temperature condition.

$ #define HLTH_MULTI_TRAYED_FAN_FAILED 1144
1144 Both fans or the only fan in one of the trays have failed. This is a critical condition that may cause the tray to reach an unsafe operating temperature.

$ #define HLTH_TRAYED_FAN_FAILED 1145
1145 A fan in one of the disk drive trays has failed. The remaining fan should be able to maintain an acceptable operating temperature for a short period of time.

$ #define HLTH_MULTI_TRAYED_PSUPPLY_FAILED 1146
1146 Both power supplies in one of the disk drive trays have failed. This is a critical condition that requires immediate action.

$ #define HLTH_TRAYED_POWER_SUPPLY_FAILED 1147
1147 A power supply in one of the disk drive trays has failed. The remaining power supply should be able to maintain sufficient power; however, operating in this condition is not recommended.

$ #define ST_MULT_TRAYED_FAN_FAIL 1148
1148 Drive Tray-Fan Failures

$ #define ST_TRAYED_FAN_FAIL 1149
1149 Drive Tray-Fan Failure

$ #define ST_MULT_TRAYED_PS_FAIL 1150
1150 Drive Tray-Pwr Supp Failures

$ #define ST_TRAYED_POWER_SUPPLY_FAIL 1151
1151 Drive Tray-Pwr Supp Failure

$ #define ST_ENVIRON_CARD_FAIL 1152
1152 Environmental Card Failure

$ #define ST_TEMP_EXCEEDED 1153
1153 Drive Tray-Temp. Exceeded

$ #define AFF_COMP_ENVIRON_CARD 1154
1154 Affected Component: Environmental Card

$ #define HLTH_ENVIRON_CARD_FAILED 1155
1155 Lost communication with an environmental card in one of the disk drive trays.

$ #define AFF_COMP_TRAYED_FAN 1156
1156 Affected Component: Fan in Drive Tray

$ #define AFF_COMP_TRAYED_MULTI_FAN 1157
1157 Affected Component: Fans in Drive Tray

$ #define AFF_COMP_TRAYED_PS 1158
1158 Affected Component: Power Supply in Drive Tray

$ #define AFF_COMP_TRAYED_MULTI_PS 1159
1159 Affected Component: Power Supplies in Drive Tray

$ #define AFF_COMP_TRAYED_TEMP_EXCEEDED 1160
1160 Affected Component: Disk Drive Tray

$ #define HLTH_TEMP_EXCEEDED 1161
1161 The maximum temperature allowed within a disk drive tray has been exceeded. This is a critical condition that may cause the drive tray to turn off if you do not resolve the problem quickly.

$ #define LUN_BALANCING_IO_MESSAGE 1188
1188 Please ensure that you have stopped all I/Os to\nthe selected RAID Module(s) before performing\nLUN Balancing.

$ #define CREATE_HS_SMALL_DRIVE_WARN2 1189
1189 \n \nDo you still want to use this drive?

$ #define CFG_STARTUP 1190
1190 Configuration Startup

$ #define ARRAYLST_NOT_FOUND_GUI 1191
1191 The file %s was not found.\nThe application cannot start.

$ #define STAT_STARTUP 1192
1192 Status Startup

$ #define REC_STARTUP 1193
1193 Recovery Startup

$ #define MT_STARTUP 1194
1194 Maintenance and Tuning Startup

$ #define CFG_APP_HDR1 1195
1195 Configuration

$ #define STAT_APP_HDR1 1196
1196 Status

$ #define REC_APP_HDR1 1197
1197 Recovery

$ #define MT_APP_HDR1 1198
1198 Maintenance and Tuning

$ #define RU_DRIVE_COUNT_ERR 1202
1202 Wrong number of drives entered for the RAID level given.\n

$ #define PRINT_HIDE_SD_USAGE 1203
1203 \n\nUsage:  %s on | off\n

$ #define HIDE_SD_MSG_1 1204
1204 %s could not open RDAC control dev.\n

$ #define HIDE_SD_MSG_2 1205
1205 %s failed on devinfo traversal ioctl call.\n

$ #define HLTH_UNRESPONSIVE_DRIVE 1206
1206 One or more drives that were optimal are no longer accessible. If the drives receive any I/O, the controller will fail the drives.

$ #define LUN_CAPACITY_CHANGE_HEADER 1207
1207 LUN Capacity Change

$ #define LUN_CAPACITY_CHANGE_MSG 1208
1208 The drive selection you made has caused a change in total\nLUN Capacity.  This capacity has been divided equally among\nthe LUNs you have specified.\n \nUse the LUN Capacity option to view or change the new capacity.

$ #define FAILED_HS_MESSAGE 1219
1219 Cannot delete a failed hot spare drive.\n \nThe drive must be replaced using the Recovery Guru.

$ #define FAILED_HS_HEADER 1220
1220 Failed Hot Spare

$ #define HLTH_ACTION_UNRESPONSIVE_DRIVES 1222
1222 Please use the Recovery Guru application to resolve this problem.

$ #define FWDL_CONT_NOT_SPEC_HEADER 1223
1223 Controller Not Specified

$ #define FWDL_NOCONTSEL_ERROR 1224
1224 No controllers were specified for downloading.

$ #define FWDL_ONECONTSEL_ERROR 1225
1225 The selected controller is not accessible.\n \nUse the Recovery Guru to fix the problem.

$ #define FWDL_SINGLECONTIO_ERROR 1226
1226 The selected controller is currently receiving I/O.\n \nWhen downloading firmware to a single controller in a controller\npair, the only I/O activity that can occur must be on the other\ncontroller in the pair.

$ #define FWDL_STEP1 1227
1227 1. Select Controller(s) to Upgrade (both recommended)

$ #define FWDL_STEP2 1228
1228 2. Select Compatible Files/Versions

$ #define FWDL_TEXT1 1229
1229 Current Firmware version(s):

$ #define FWDL_TEXT2 1230
1230 Select Compatible Files/Versions

$ #define FWDL_IODETECTED_HEADER 1231
1231 I/O Detected

$ #define FWDL_BOTHCONTIO_ERROR 1232
1232 The controller(s) is currently receiving I/O.\n \n--If this RAID Module is the boot device, you CANNOT use\nthis Offline method. Press Cancel and use the Online method.\n \n--If this RAID Module is not a boot device either\n(1) stop all I/Os to the controller(s) and select OK to continue, or\n(2) select Cancel and use the Online method.\n \nWARNING\nIf you continue with I/Os still occurring, the I/Os and the\ndownload will probably fail.

$ #define FWDL_STARTBOTHOFF_UPGRADE 1233
1233 The offline upgrade is about to start\nto both controllers.\n \nOK to proceed?

$ #define FWDL_STARTAOFF_UPGRADE 1234
1234 The offline upgrade is about to start\nto Controller A only.\n \nOK to proceed?

$ #define FWDL_STARTBOFF_UPGRADE 1235
1235 The offline upgrade is about to start\nto Controller B only.\n \nOK to proceed?

$ #define FWDL_STARTBOTHON_UPGRADE 1236
1236 The online upgrade is about to start\nto both controllers.\n \nOK to proceed?

$ #define FWDL_STARTAON_UPGRADE 1237
1237 The online upgrade is about to start\nto Controller A only.\n \nOK to proceed?

$ #define FWDL_STARTBON_UPGRADE 1238
1238 The online upgrade is about to start\nto Controller B only.\n \nOK to proceed?

$ #define RECGURU_MULT_UNRESP_DRV 1247
1247 Multiple Unresponsive Drives

$ #define ST_MULT_UNRESP_DRV 1248
1248 Multiple Unresponsive Drives

$ #define ST_UNRESP_DRV 1249
1249 Unresponsive Drive

$ #define HLTH_UNRESP_DRIVE_ACTION 1250
1250 Please enter the Recovery application to resolve this problem.

$ #define ST_DET_MSG_AFF_LBL11 1251
1251 \nParity Repair Range:\n

$ #define ST_PARITY_RANGE_LBL 1252
1252 Parity Repair Range:

$ #define FW_WARN_NOTE1 1253
1253 NOTE 1:  You can download both Firmware and NVSRAM files with this option.\n

$ #define FW_WARN_NOTE2 1254
1254 NOTE 2:  It is recommended that you download to all controllers in the RAID Module.\n

$ #define FW_WARN_NOTE3 1255
1255 NOTE 3:  Always download the NVSRAM file (if required) before downloading firmware.\n

$ #define FW_WARN_NOTE4 1256
1256 NOTE 4:  Download the NVSRAM file using the Path line at the bottom of the file selection screen.\n

$ #define FW_WARN_NOTE5 1257
1257 NOTE 5:  Run nvutil -vf from the command line after downloading the NVSRAM file.\n

$ #define FW_WARN_NOTE1_LINE1 1258
1258 Use this option to download Firmware and NVSRAM files (the NVSRAM file specifies certain\ndefault settings for the controller). You can perform the download while there are I/Os continuing\n

$ #define FW_WARN_NOTE1_LINE2 1259
1259 to the controllers (Online Upgrade) or after I/Os have been stopped (Offline Upgrade). You can\nonly perform the Online Upgrade if you have a pair of redundant controllers.\n \n

$ #define FW_WARN_NOTE2_LINE1 1260
1260 If you have a redundant pair of controllers, it is highly recommended that you download the\nNVSRAM and Firmware files to both controllers at the same time. This will ensure that both\n

$ #define FW_WARN_NOTE2_LINE2 1261
1261 controllers have the same level of NVSRAM and Firmware files.\n \n

$ #define FW_WARN_NOTE3_LINE1 1262
1262 In most cases, you will have to download a new NVSRAM file (especially when upgrading from\none major firmware release to another, for example 2.03 to 2.04). Always download the NVSRAM\n

$ #define FW_WARN_NOTE3_LINE2 1263
1263 file separately, then use the option again to download the firmware. You can obtain the new\nNVSRAM file from your customer representative. If you do not download the NVSRAM file,\n

$ #define FW_WARN_NOTE3_LINE3 1264
1264 certain features of this RAID Management software and in the RAID controller may not work.\n \n

$ #define FW_WARN_NOTE4_LINE1 1265
1265 Enter the name of the NVSRAM file (and its appropriate path) on the Path line in the screen\nwhere you are asked to specify a file.\n \n

$ #define FW_WARN_NOTE5_LINE1 1266
1266 Once you have downloaded the new NVSRAM file to all of the controllers/RAID Modules you\nwant, run the nvutil command line utility to ensure that certain settings in the NVSRAM are set\n

$ #define FW_WARN_NOTE5_LINE2 1267
1267 up correctly for the RAID Management software.  At the command line enter: nvutil -vf. This\nwill check and correct any settings on all RAID controllers in your RAID Modules.

$ #define GENWARN_LUN_BUSY 1269
1269 An attempt to communicate with %s has failed, because\neither:\n \n(1) no formatted LUNs exist and LUNs are being created, or\n(2) another application has reserved all LUNs on the module.

$ #define GENWARN_LUN_BUSY2 1270
1270 \n \nWait for at least one LUN to be created, or for the other\napplication to complete, then retry the operation.

$ #define RDACUTIL_MSG_6 1271
1271 rdacutil -F <raid controller specifier>\n

$ #define CFG_CANNOT_CREATE_LUN 1272
1272 Unable To Create LUNs\n

$ #define CFG_CANNOT_CREATE_LUN_MSG 1273
1273 Unable to create logical units (LUNs) on this drive group because\nit currently has a failed drive.\n \nPlease use the Recovery Guru to replace the failed drive before\ncreating any additional LUNs on this drive group.

$ #define CONFIG_DEL_LUN_ERR_MSG2 1275
1275 to finish or stop the application.\n - If there is a mounted filesystem on the LUN, dismount it.\n - If the LUN is reconstructing, wait until reconstruction\nhas completed.\n -  If another host has the LUN reserved, have that host\nrelease the LUN.\n - If a LUN or group is being modified, wait until the\noperation has completed.

$ #define PRINT_DRIVUTIL_USAGE 1276
1276 \n \nUsage: %s%s%s%s%s

$ #define DRIVUTIL_ERR_1 1277
1277 An error occurred while attempting\nto reconstruct the drive at location %s.\n

$ #define DRIVUTIL_ERR_2 1278
1278 Could not get info for lun %d.\n

$ #define DRIVUTIL_ERR_3 1279
1279 Could not revive lun %d.\n

$ #define DRIVUTIL_ERR_4 1280
1280 %s is unable to retrieve the Logical array page from  %s.\n

$ #define DRIVUTIL_ERR_5 1281
1281 Invalid lun number (%d); the number must be 0-%d.\n

$ #define DRIVUTIL_ERR_6 1282
1282 Could not get reconstruction info for lun %d.\n

$ #define DRIVUTIL_OUT_MSG_1 1283
1283 degraded

$ #define DRIVUTIL_OUT_MSG_2 1284
1284 does not exist

$ #define DRIVUTIL_OUT_MSG_3 1285
1285 unknown lun

$ #define DRIVUTIL_OUT_MSG_4 1286
1286 progress indeterminate

$ #define DRIVUTIL_OUT_MSG_5 1287
1287 reconstruction pending

$ #define DRIVUTIL_OUT_MSG_6 1288
1288 optimal

$ #define DRIVUTIL_OUT_MSG_7 1289
1289 percent reconstructed

$ #define GRP_INFO1 1290
1290   Group         No. of    RAID       No. of       Total       Remaining

$ #define GRP_INFO2 1291
1291                 LUNs      Level      Drives       Space(MB)   Space(MB)

$ #define PRINT_FWUTIL_USAGE 1292
1292 \n\nUsage: %s

$ #define FWUTIL_MSG_1 1293
1293 fwutil <file> <raid controller specifier>\n

$ #define DRIV_INFO_HEADING_1 1294
1294 Location  Capacity   Status         Vendor  Product          Firmware     Serial

$ #define DRIV_INFO_HEADING_2 1295
1295             (MB)                              ID             Version      Number

$ #define PRINT_HEALTHCK_USAGE 1296
1296 \n\nUsage: %s%s

$ #define HEALTHCK_ERR_1 1297
1297 An error occurred while performing a Health Check on RAID module %s\n

$ #define HEALTHCK_MSG_1 1298
1298 optimal

$ #define DRIVUTIL_ERR_7 1299
1299 Could not get lun status for lun %d.\n

$ #define DRIVUTIL_OUT_MSG_8 1300
1300 dead

$ #define LUN_INFO_HEADING_1 1301
1301  LUN      Group      Device           RAID      Capacity      Status

$ #define LUN_INFO_HEADING_2 1302
1302                      Name             Level     (MB)

$ #define LUN_INFO_HEADING_3 1303
1303  Logical Unit Information for %s

$ #define HC_HEADING 1304
1304 Health Check Summary Information

$ #define HC_MSG_1 1305
1305 Optimal

$ #define HC_MSG_2 1306
1306 Channel Failure

$ #define HC_MSG_3 1307
1307 Multiple Drive Failure

$ #define HC_MSG_4 1308
1308 Drive Failure

$ #define HC_MSG_5 1309
1309 Multiple Unresponsive Drives

$ #define HC_MSG_6 1310
1310 Unresponsive Drive

$ #define HC_MSG_7 1311
1311 Warning Drive

$ #define HC_MSG_8 1312
1312 Data Path Failure

$ #define HC_MSG_9 1313
1313 Module Component Failure

$ #define HC_MSG_10 1314
1314 Drive Tray-Fan Failures

$ #define HC_MSG_11 1315
1315 Drive Tray-Fan Failure

$ #define HC_MSG_12 1316
1316 Drive Tray-Pwr Supp Failures

$ #define HC_MSG_13 1317
1317 Drive Tray-Pwr Supp Failure

$ #define HC_MSG_14 1318
1318 Thermal Sensor Fault

$ #define HC_MSG_15 1319
1319 Failed/Warning Drive

$ #define HC_MSG_16 1320
1320 Hotspare Failure

$ #define HC_MSG_17 1321
1321 Unit Failure

$ #define HC_MSG_18 1322
1322 Environmental Card Failure

$ #define HC_MSG_19 1323
1323 Unknown Failure

$ #define HC_MSG_20 1324
1324 An error occurred while attempting to get drive info.

$ #define GRP_INFO0 1325
1325 Group Information for %s

$ #define DRIV_INFO_HEADING_0 1326
1326 Drive Information for %s

$ #define MOD_PROF_SPARE 1327
1327 Spare%s

$ #define MOD_PROF_SPARE_STDBY 1328
1328 Spare-Stdby

$ #define DELETE_ALL_LUNS 1329
1329 Delete all logical units?\n \n

$ #define DELETE_ONE_LUN 1330
1330 Delete logical unit?\n \n

$ #define DELETE_SELECTED_LUNS 1331
1331 Delete selected logical unit(s)?\n \nThis will destroy all data on the selected\nlogical unit(s) and increase the remaining\ncapacity on the drive group.

$ #define DELETE_ALL_LUNS_TEXT 1332
1332 This will destroy all data and return the\ndrive group to an unassigned status.

$ #define INVALID_LUN_NUMBER 1333
1333 Affected Logical Unit:  -\n

$ #define DECIMAL_LUN_NUMBER 1334
1334 Affected Logical Unit:  %ld\n

$ #define STARTUP_RMPARAMS_ERROR 1335
1335 Cannot initialize the %s value.\nThe application cannot start.\n \nVerify the directory path and system variable\nare correct in the rmparams file.

$ #define RM6_STARTUP 1336
1336 Startup

$ #define LOCATE_MODULE_HEADER 1337
1337 Locate Module

$ #define RDACUTIL_MSG_7 1338
1338 rdacutil -l <LUN-list> <raid controller specifier>\n

$ #define RDACUTIL_ERR_1 1339
1339 bad argument %s in rdacutil command line, the lun must be in the range 0-%d.\n

$ #define SAVE_CACHE_IO_MESSAGE 1340
1340 Please ensure that you have stopped all I/Os to\nthe selected RAID Module(s) before attempting\nto change and save the caching parameters.

$ #define STOP_IOS_BEFORE_PROCEEDING 1341
1341 Stop I/Os Before Proceeding

$ #define PRODUCT_NAME 1342
1342 SYMplicity Storage Manager

$ #define BAD_LIST_TYPE 1343
1343 You must specify at least one type.

$ #define EVENT_AEN_3FD8_CAUSE 1344
1344 The controller has failed the battery because the battery has reached its expiration date.

$ #define EVENT_AEN_3FD9_CAUSE 1345
1345 The controller has detected that the battery is nearing its expiration date.

$ #define EVENT_AEN_3FD8_3FD9_ACTION 1346
1346 Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.

$ #define EVENT_AEN_3FBD_CAUSE 1347
1347 The controller was unable to query the drive for its current critical mode page settings or was unable to change these to the correct setting. The controller has marked the drive as failed.

$ #define EVENT_AEN_0C80_CAUSE 1348
1348 An unrecoverable write error has occurred. The controller has detected that its batteries, as well as those of its alternate controller (if present) are not functioning. User data may have been lost.

$ #define EVENT_AEN_3FC8_ACTION 1349
1349 Because the UPS has switched to standby power, you should save your data frequently in case the standby power is suddenly depleted. Repair the AC power problem.

$ #define GENERIC_CAUSE 1350
1350 This type of code is normally just an internal message issued from the controller to the host software/driver. If you are not experiencing any other problems, then there is no cause for concern.

$ #define GENERIC_ACTION 1351
1351 If you suspect any problem, run Health Check and/or check the online help topic, Status Application >> ASC/ASCQ Error Codes, for further details.

$ #define FW_WARN_NOTE5_CAUTION 1352
1352 If using the Networked version, specify the NVSRAM definition file using the -n\noption of nvutil (for example, nvutil -vf -n nt.def). See the user documentation\nfor further details.

$ #define SEARCHING_FOR_MODULES 1353
1353 Searching for RAID Modules. Please wait...

$ #define CONFIG_CHANGE_DETECTED 1354
1354 Updating screen - Please wait.

$ #define MON_HS_RECON_COMPLETE 1355
1355 Reconstruction complete for LUN %d on %s.  Hot spare at [%d,%d] has taken over for failed drive at [%d,%d]


$ #define MON_DRIVE_TO_OPTIMAL 1356
1356 Drive at [%d,%d] status changed to optimal\n

$ #define MON_CONTROLLER_ONLINE 1357
1357 The controller listed has detected that the alternate controller has returned to an online status in %s

$ #define GROUP_NUM 1358
1358  Group %2d:

$ #define GRP_INFO3 1359
1359 Drives in Group for %s

$ #define GRP_INFO4 1360
1360   Group          Drive List  [Channel,Id]\n

$ #define DELETE_LUN_REBOOT_MSG 1361
1361 \n \nIMPORTANT: If you see system error\nmessages relating to these deleted LUNs,\nyou may want to reboot your system to\npermanently remove any system\ninformation about these LUNs.

$ #define DEL_ADD_REBOOT_MSG 1362
1362 IMPORTANT: Because you added or deleted some\nLUNs, make sure you reboot your system\nso that any LUN changes are recognized\nby your operating system.

$ #define UNIT 1363
1363 unit

$ #define RU_CACHE_BATTERY_AGE 1364
1364 Battery age is between %d days and %d days.\n

$ #define RU_BATTERY_AGE_NOT_SET 1365
1365 The battery age has not been set.\n

$ #define MT_LUN_RECON_SAVE 1366
1366 Save LUN Reconstruction parameters.

$ #define PROF_MSG_48 1367
1367 Fibre Channel Level:

$ #define ADD_TITLE 1368
1368 Add

$ #define EDIT_TITLE 1369
1369 Edit

$ #define FIND_TITLE 1370
1370 Find

$ #define MODSEL_TITLE 1371
1371 RAID Module Selection

$ #define REMOVE_TITLE 1372
1372 Remove

$ #define NRMMOD_NOTDEFINED 1373
1373 No RAID Modules are currently defined.\nSelect OK to add RAID Modules.

$ #define FAILED_NRMMOD_CONNECTION 1374
1374 Could not connect to the selected RAID Module.\nCheck your network connection and try again.

$ #define ALLMOD_COMMENT 1375
1375 This is the All RAID Modules selection.

$ #define SEARCHITEM_NOTFOUND 1376
1376 The search item was not found.

$ #define SEARCH_ENDOFLIST 1377
1377 Finished searching the list.

$ #define ADD_NRMMOD_DEFINITION 1378
1378 Adding module definition and verifying\nhost names. Please wait...

$ #define ADD_NRMMOD_SUCCESS 1379
1379 The RAID Module was successfully added.

$ #define FAILED_ADD_NRMMOD 1380
1380 Could not connect to the selected RAID Module.\nVerify your host names and/or check your\nnetwork connection.

$ #define FAILED_AUTHORIZATION 1381
1381 You are not authorized to access controller %s\nfrom this host. Verify that your controller network\nconfiguration contains an RMS entry that is associated\nwith this host's IP address.\n \n

$ #define NRMMODINFO_NOTADDED 1382
1382 You have not added this information.\nAre you sure you want to exit?

$ #define NRMMODINFO_NOTSUPPLIED 1383
1383 You must include at least one host/controller name.

$ #define ADD_SCSIMOD 1384
1384 You cannot interactively add a RAID Module using this\ninterface (except for the Networked version). To\nadd/recognize a RAID Module, you will normally\nhave to reboot the system. However, consult the\nInstallation Guide for details.

$ #define INDEPENDENT_CNTRL_DETECTED 1385
1385 This RAID Module has been previously designated\nas having independent controllers. If you want\nto change this designation, use the Edit option\nin the Module Selection window.

$ #define ADD_NAMEPROB 1386
1386 You already have a module named %s.\nPlease enter a different name.

$ #define DUP_NAME_FOUND 1387
1387 Multiple RAID Modules have been detected with the name\n%s. One of the modules has TEMPORARILY\nchanged to %s.\n \nIMPORTANT\nYou MUST use the Edit option in Module Selection to\nresolve the name conflict between the modules either\nby permanently accepting the temporary name or by\nproviding another unique name. If you do not resolve\nthe name conflict, you will continue to be warned\neach time you open an application.

$ #define REMOVE_RAIDMOD 1388
1388 Removing a RAID Module will NOT affect the data already\nstored on it. Only references to it in the various\napplications will be deleted (except for the\nMessage Log option in the Status Application).\n \nAre you sure you want to remove the RAID Module?

$ #define EDIT_SAVECHANGES 1389
1389 Do you want to save your changes before exiting?

$ #define MOD_COLHEAD 1390
1390 Module\nName

$ #define CNTRL_COLHEAD 1391
1391 Controller\nInformation

$ #define INDEPCNTRL_COLHEAD 1392
1392 Indep.\nCntrls?

$ #define COMMENT_COLHEAD 1393
1393 Comment

$ #define INACCESSIBLE_STATUS 1394
1394 Inaccessible

$ #define INDEPENDENT_CONTROLLERS 1395
1395 Independent Controllers

$ #define MODSEL_STATLINE_MESS 1396
1396 Select or modify a RAID Module.

$ #define EVENT_AEN_3F8E_CAUSE 1397
1397 The drive has failed (read error) because of a interrupted write recovery process during a controller reset or a power failure.

$ #define EVENT_AEN_3F8E_ACTION 1398
1398 Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.

$ #define EVENT_AEN_3F98_CAUSE 1399
1399 The drive has been marked offline because an interrupted write recovery process has failed.

$ #define EVENT_AEN_3F98_ACTION 1400
1400 Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.

$ #define EVENT_AEN_3FEB_CAUSE 1401
1401 The LUN has been marked Dead because an interrupted write recovery process has failed.

$ #define EVENT_AEN_3FEB_ACTION 1402
1402 Record the affected LUN numbers and then use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.

$ #define PROF_MSG_OFFLINE 1403
1403 Offline

$ #define LUNMOVE_SPLITBUS_TEXT1 1404
1404 -- You cannot move LUNs to an inaccessible controller.\nIf you did this, it will not be saved.\n \n-- If you moved LUNs from an inaccessible controller to\nan accessible one, you cannot move these LUNs\nback from this host. You must use the LUN Balancing\n

$ #define LUNMOVE_SPLITBUS_TEXT2 1405
1405 option from the other host to move the LUNs back.\n \nWARNING\nIf you moved LUNs from an inaccessible controller, you\nMUST stop all I/Os to these LUNs before selecting OK.\nSelecting OK with I/O activity on these LUNs will\ncause the I/Os to fail!

$ #define SYMPING_USAGE 1406
1406 \nUsage:  symping [-q] [hostname]\n

$ #define UNABLE_TO_RESOLVE_HOSTNAME 1413
1413 The host was unable to resolve the controller\nhostname %s to an IP address.\n \n

$ #define NRM_VERIFICATION_SUCCESS 1414
1414 The path verification and host authorization check for\ncontroller %s completed successfully.\n \n

$ #define FAILED_NRMCNTRL_CONNECTION 1415
1415 Could not connect to controller %s.\nCheck your network connection and try again.\n \n

$ #define RMDIALOG_STR_MORE_DETAILS 1430
1430 &More Details

$ #define MANUAL_LUN_BAL_IO_MESSAGE 1431
1431 Make sure you have stopped all I/Os to\nthe drive group/logical units you select\nbefore balancing the LUNs.

$ #define PLACE_INACCESS_CONT_OFFLINE 1432
1432 You are about to place controller %s offline. Stop all I/Os\nto this inaccessible controller before selecting OK. Selecting OK\nwith I/O activity on this controller will cause the I/Os to fail!\n \nPlace controller %s offline?

$ #define LOCKED_LUN_STATUS 1433
1433 Locked

$ #define NO_REMOVE_ALLRAIDMODULES 1434
1434 You cannot remove the All RAID Modules selection.

$ #define NO_EDIT_ALLRAIDMODULES 1435
1435 You cannot edit the All RAID Modules selection.

$ #define INCORRECT_MODNAME 1436
1436 You cannot use this name. Please\nenter another one.

$ #define HOSTNAME_LONG 1437
1437 Only 8 characters of the host name will be displayed\nin the various screens. Press Cancel if you want to\nprovide another name.

$ #define MODNAME_REQUIRED 1438
1438 You must provide a name for the RAID Module.

$ #define MOD_REMOVE_FAILED 1439
1439 Unable to remove the RAID Module.

$ #define MOD_NO_INFO 1440
1440 Unable to obtain information on the selected RAID Module.

$ #define ILLEGAL_CHAR_MODNAME 1441
1441 You can only use characters A-Z, 0-9, a dash (-), an\nunderscore (_), and spaces for the RAID Module name.

$ #define ILLEGAL_CHAR_HOSTNAME 1442
1442 You can only use characters A-Z, 0-9, a dash (-), an underscore (_),\nand spaces for the controller information (host name).

$ #define ILLEGAL_CHAR_COMMENT 1443
1443 You cannot insert a newline or use a tilde (~)\ncharacter in your comments.

$ #define CNTRLS_NOT_IN_SAME_MODULE 1444
1444 The host names you entered are for two controllers that are not\nin the same physical RAID Module. Please re-enter the host names.

$ #define CNTRLS_NOT_IN_CORRECT_ORDER 1445
1445 The controller information you provided does not match the physical position\nof the controller(s) within the module. Please re-enter the information\nto represent the physical position of the controller(s).

$ #define REC_DL_FAIL_INDCONTS 1446
1446 Failed -- This RAID Module is configured for inde-\n%spendent controllers. You must select this\n%smodule separately to upgrade the firmware.

$ #define CAUTION_HDR 1447
1447 CAUTION

$ #define FW_INDCONTS_MSG1 1448
1448 Because this RAID Module has independent controllers, you will\nonly be able to upgrade the firmware on one controller from this host.\n \n

$ #define FW_INDCONTS_MSG2 1449
1449 It is very important that you maintain the same versions of firmware\non each controller. Therefore, after upgrading firmware on this controller,\nuse the Firmware Upgrade option on the other host to upgrade the\nfirmware on the other controller.

$ #define NAME_MATCHES_SERIALNO 1452
1452 The name you entered matches a serial number for a \nRAID controller. Please enter another name.

$ #define NO_UPDATE_EDIT_INFO 1453
1453 Cannot update the new module information.\nPlease try again later.

$ #define MODE_SELECT_LOCK 1454
1454 An application has failed to release a locked resource.\nPlease consult the online help/user manual for the\nappropriate procedure to release the locked resource.

$ #define INTERNAL_PROCESSING_ERROR 1459
1459 An internal processing error occurred on controller %s.\n \n

$ #define NVRAM_REBOOT 1460
1460 A NVSRAM field has been modified. You must power cycle the affected RAID Module(s).\n

$ #define CFG_ICONIZED_NAME 1461
1461 Config

$ #define REC_ICONIZED_NAME 1462
1462 Recov

$ #define MNT_ICONIZED_NAME 1463
1463 Maint

$ #define SYM_ICONIZED_NAME 1464
1464 symsm

$ #define NOT_AVAILABLE 1465
1465 Not Available

$ #define LOG_FILE_HDR 1466
1466 Log File Create

$ #define FWDL_IORESTRICTED 1467
1467 The selected controller(s) is currently receiving I/O.\n \nStop all I/Os to the controller(s) and restart the firmware upgrade.

$ #define FOR_ADDITIONAL_INFO 1468
1468 \nFor additional information: \n\n\tOn unix type 'man <topic>'\n\tOn NT type 'help <topic>' from the installation directory.\n

$ #define MAKELUN_116 1472
1472 \n LUNs successfully created\n

$ #define MAKELUN_117 1473
1473 \n LUNs successfully deleted\n

$ #define FWUTIL_USAGE_4 1474
1474 \n The file %s does not exist\n

$ #define STORUTIL_WIPE_FAILED 1475
1475 \nstorutil failed to clear the Host Store for module %s.\n

$ #define DRIVUTIL_USAGE_1 1477
1477 \n     drivutil -d | -i | -I | -l <raid module specifier>


$ #define DRIVUTIL_USAGE_2 1478
1478 \n     drivutil -f <drive> < raid module specifier>


$ #define DRIVUTIL_USAGE_3 1479
1479 \n     drivutil -p <lun> <raid module specifier>


$ #define DRIVUTIL_USAGE_4 1480
1480 \n     drivutil -r <lun> <raid module specifier>


$ #define DRIVUTIL_USAGE_5 1481
1481 \n     drivutil -u | -U <drive> <raid module specifier>


$ #define DRIVUTIL_USAGE_6 1482
1482 \n     drivutil -?

$ #define DRIVUTIL_USAGE_END 1483
1483 \n

$ #define HEALTHCK_USAGE_1 1488
1488 \n     healthck <raid module specifier>


$ #define HEALTHCK_USAGE_2 1489
1489 \n     healthck -a


$ #define HEALTHCK_USAGE_3 1490
1490 \n     healthck -?

$ #define HEALTHCK_USAGE_END 1491
1491 \n

$ #define LAD_USAGE_1 1492
1492 \n     lad


$ #define LAD_USAGE_2 1493
1493 \n     lad -a (NT only)


$ #define LAD_USAGE_3 1494
1494 \n     lad -?

$ #define LAD_USAGE_END 1495
1495 \n

$ #define LOGUTIL_USAGE_1 1496
1496 \n     logutil <log filename>


$ #define LOGUTIL_USAGE_2 1497
1497 \n     logutil -?

$ #define LOGUTIL_USAGE_END 1498
1498 \n

$ #define NVUTIL_USAGE_1 1499
1499 \n     nvutil -v [-q] [-f] [-s] [-n <filename>]


$ #define NVUTIL_USAGE_2 1500
1500 \n     nvutil -o [-q] <offset>[,<offset2>[,<offset3>-<offset4>]...]


$ #define NVUTIL_USAGE_3 1501
1501 \n               [<device>]


$ #define NVUTIL_USAGE_4 1502
1502 \n     nvutil -o [-q] <offset1>=<value1>[,<offset2>=<value2>...]


$ #define NVUTIL_USAGE_5 1503
1503 \n               [<device>]


$ #define NVUTIL_USAGE_6 1504
1504 \n     nvutil -?

$ #define NVUTIL_USAGE_END 1505
1505 \n

$ #define PARITYCK_USAGE_1 1506
1506 \n     parityck [ -a ] [ -f ] [ -n ] [ -q ] [ -r ] [ -R ] [ -c device ] [ -? ]

$ #define PARITYCK_USAGE_END 1507
1507 \n

$ #define RAIDUTIL_USAGE_1 1508
1508 \n     raidutil  -c device


$ #define RAIDUTIL_USAGE_2 1509
1509 \n               [ -b maximum prefetch ceiling ]


$ #define RAIDUTIL_USAGE_3 1510
1510 \n               [ -f multiplication factor ]


$ #define RAIDUTIL_USAGE_4 1511
1511 \n               [ -g drive group ]


$ #define RAIDUTIL_USAGE_5 1512
1512 \n               [ -h create hot spare ]


$ #define RAIDUTIL_USAGE_6 1513
1513 \n               [ -i display inquiry information ]


$ #define RAIDUTIL_USAGE_7 1514
1514 \n               [ -k minimum prefetch ]


$ #define RAIDUTIL_USAGE_8 1515
1515 \n               [ -l RAID level ]


$ #define RAIDUTIL_USAGE_9 1516
1516 \n               [ -m cache mirroring enable ]


$ #define RAIDUTIL_USAGE_10 1517
1517 \n               [ -n LUN number to create ]


$ #define RAIDUTIL_USAGE_11 1518
1518 \n               [ -p cache read ahead enable ]


$ #define RAIDUTIL_USAGE_12 1519
1519 \n               [ -q suppress print output during execution ]


$ #define RAIDUTIL_USAGE_13 1520
1520 \n               [ -r reconstruction rate ]


$ #define RAIDUTIL_USAGE_14 1521
1521 \n               [ -s LUN size ]


$ #define RAIDUTIL_USAGE_15 1522
1522 \n               [ -t Disable prefetch transfer length ]


$ #define RAIDUTIL_USAGE_16 1523
1523 \n               [ -v volatile caching allowed ]


$ #define RAIDUTIL_USAGE_17 1524
1524 \n               [ -w cache enable ]


$ #define RAIDUTIL_USAGE_18 1525
1525 \n               [ -x segment 0 size ]


$ #define RAIDUTIL_USAGE_19 1526
1526 \n               [ -z segment size ]


$ #define RAIDUTIL_USAGE_20 1527
1527 \n               [ -A demand flush amount ]


$ #define RAIDUTIL_USAGE_21 1528
1528 \n               [ -B display battery age ]


$ #define RAIDUTIL_USAGE_22 1529
1529 \n               [ -C read cache disable ]


$ #define RAIDUTIL_USAGE_23 1530
1530 \n               [ -D delete LUN ]


$ #define RAIDUTIL_USAGE_24 1531
1531 \n               [ -H delete hot spare ]


$ #define RAIDUTIL_USAGE_25 1532
1532 \n               [ -R reset battery age ]


$ #define RAIDUTIL_USAGE_26 1533
1533 \n               [ -S cache block size ]


$ #define RAIDUTIL_USAGE_27 1534
1534 \n               [ -T demand flush threshold ]


$ #define RAIDUTIL_USAGE_28 1535
1535 \n               [ -V view caching page (Page 08)]


$ #define RAIDUTIL_USAGE_29 1536
1536 \n               [ -W reset host store ]


$ #define RAIDUTIL_USAGE_30 1537
1537 \n               [ -X reset module configuration ]


$ #define RAIDUTIL_USAGE_31 1538
1538 \n               [ -? display usage information ]

$ #define RAIDUTIL_USAGE_END 1539
1539 \n

$ #define RDACUTIL_USAGE_1 1540
1540 \n     rdacutil -f <raid controller specifier>


$ #define RDACUTIL_USAGE_2 1541
1541 \n     rdacutil -F <raid controller specifier>


$ #define RDACUTIL_USAGE_3 1542
1542 \n     rdacutil -i <raid module specifier>


$ #define RDACUTIL_USAGE_4 1543
1543 \n     rdacutil -l <LUN-list> <raid controller specifier>


$ #define RDACUTIL_USAGE_5 1544
1544 \n     rdacutil -m <mode> [-b] <raid module specifier>


$ #define RDACUTIL_USAGE_6 1545
1545 \n     rdacutil -u <raid controller specifier>


$ #define RDACUTIL_USAGE_7 1546
1546 \n     rdacutil -U <raid controller specifier>


$ #define RDACUTIL_USAGE_8 1547
1547 \n     rdacutil -?

$ #define RDACUTIL_USAGE_END 1548
1548 \n

$ #define CFG_CACHING_LIMITS 1555
1555 Not Enough Memory

$ #define MT_ERR_OBTAIN_MOD_INFO2 1556
1556 This Module does not have the minimum configuration\nof 8 MB of cache memory and 8 MB of processor memory needed\nto enable the caching parameters. Use Module Profile to\ndetermine the current memory sizes.\n

$ #define CREATE_ON_PASSIVE_ERROR 1557
1557 Unable to create LUNs on a passive controller.\nChange controller pair to Active/Active using\nthe Maintenance/Tuning Application.

$ #define CREATE_HS_ON_PASSIVE_ERROR 1558
1558 Unable to create hot spare drives on a passive controller.\nChange controller pair to Active/Active using the\nMaintenance/Tuning Application.

$ #define IND_CONT_WITH_PASSIVE 1559
1559 WARNING:  Controller %c in %s is Passive.\nFor independent controller configuration, change\ncontroller pair to Active/Active using the\nMaintenance/Tuning Application.

$ #define DRIVE_OPS_ON_PASSIVE 1560
1560 Unable to perform drive operations on a passive\ncontroller. Change controller pair to Active/Active\nusing the Maintenance/Tuning Application.

$ #define FAIL_DRIVE_ON_PASSIVE_HEADER 1561
1561 Unable to fail drive(s)

$ #define REVIVE_DRIVE_ON_PASSIVE_HEADER 1562
1562 Unable to revive drive(s)

$ #define MT_BAL_LUNS_INFO 1563
1563 Information

$ #define MT_BAL_LUNS_NONE_AVAIL 1564
1564 No RAID Modules available for LUN balancing

$ #define MOD_ADD_NVRAM_CHANGED 1565
1565 You must now power cycle the RAID Module.\nSeveral specific NVSRAM settings were changed\nduring the addition of the RAID Module so that\nthis storage management software can be used\nwith the module.

$ #define FWDL_INVALIDDOWNGRADE 1566
1566 You cannot go back to the selected software version\non this controller(s). Downloading this version would\nmake the controller(s) inoperable because additional\nfeatures on this module are not supported by the\nselected version.

$ #define REC_DL_INVALID_DOWNGRADE 1567
1567 Failed -- Controller does not support going back\n%sto the selected version from the current\n%sversion

$ #define DEVIO_OPEN_FAIL_DEVICE 1568
1568 SysDevOpen failed, errno=%d (%s)\n

$ #define SENSE_KEY_LBL 1569
1569 Sense Key:  %s\n

$ #define PERFMON_STATHELP_START        1570
1570 Start the performance monitor.

$ #define PERFMON_STATHELP_STOP 1571
1571 Stop the performance monitor.

$ #define PERFMON_STATHELP_UPDATE       1572
1572 Update the screen with new data.

$ #define PERFMON_STATHELP_SETTINGS     1573
1573 Change controllers/LUNs to monitor or polling interval.

$ #define PERFMON_STATHELP_HELP 1574
1574 Get specific help on the performance monitor.

$ #define PERFMON_NODEVICES_SELECTED_HEADING    1575
1575 No Controllers/LUNs Selected

$ #define PERFMON_NODEVICES_SELECTED_TEXT       1576
1576 You must select at least one\ncontroller or LUN.

$ #define PERFMON_MONITOR_STILLACTIVE_HEADING   1577
1577 Performance Monitor Still Active

$ #define PERFMON_MONITOR_STILLACTIVE_TEXT      1578
1578 The performance monitor is currently active. Exiting\nthis option will stop the performance monitor.\n \nAre you sure you want to exit?

$ #define ILLEGAL_MODNAME 1579
1579 \nYou can only use characters A-Z, 0-9, a dash (-), an underscore (_), and spaces for the RAID Module name.\n \n

$ #define ILLEGAL_MODNAME_LENGTH 1580
1580 \nThe RAID Module name entered exceeds the maximum length of %d characters.\n \n

$ #define PERFMON_STATHELP_SAVE 1581
1581 Save the current performance data to a file.

$ #define PERFMON_OVERFLOW_HEADING      1582
1582 Capacity Reached

$ #define PERFMON_OVERFLOW_TEXT 1583
1583 The monitoring process has been stopped because the display\ncapacity of the performance monitor has been reached, or another\nuser has started the performance monitor on this module.

$ #define PERFMON_DUMP_LUNTITLE 1584
1584 LUN Performance Data For Device: %s\n \n

$ #define PERFMON_DUMP_CONTRLTITLE      1585
1585 Controller Performance Data For Device: %s\n \n

$ #define PERFMON_DUMP_TIMEDATE_HEADING 1586
1586 Host Time/Date:

$ #define PERFMON_DUMP_PARAM_HEADING    1587
1587 Parameter:

$ #define PERFMON_DUMP_LENGTH_HEADING   1588
1588 Length:

$ #define PERFMON_STATHELP_PERFMON      1589
1589 Monitor the performance of selected controllers/LUNs.

$ #define PERFMON_START_FIELD   1590
1590 Start:

$ #define PERFMON_STOP_FIELD    1591
1591 Stop:

$ #define PERFMON_TIMEMON_FIELD 1592
1592 Time Monitored:

$ #define PERFMON_NOTSUPPORTED_HEADING  1593
1593 Performance Monitor Not Supported

$ #define PERFMON_NOTSUPPORTED_TEXT     1594
1594 The controller(s) in this RAID Module do not have\nthe capability to support the performance monitor.

$ #define PERFMON_SAVEDATA_HEADING      1595
1595 Peformance Monitor Data For RAID Module %s:

$ #define PERFMON_SAVEDATA_COLHEADING1  1596
1596                                  Cache   Current      Max.    Current   Max.

$ #define PERFMON_SAVEDATA_COLHEADING2  1597
1597  Devices:     Total IOs  Read %  Hit %    KB/s       KB/s      IO/s     IO/s

$ #define PERFMON_MODTOTALS     1598
1598 Module Totals:

$ #define SENSE_KEY_LBL_SEARCH_STRING 1599
1599 Sense Key:

$ #define PERFMON_STATHELP_NOSAVE       1600
1600 This option is not available because you are not in the performance monitor.

$ #define PERFMON_STARTBUTTON   1601
1601 &Start

$ #define PERFMON_STOPBUTTON    1602
1602 &Stop

$ #define PERFMON_DYNAMIC_HEADING       1603
1603 Performance Monitor

$ #define REMOVE_RAIDMOD_CAUTION        1605
1605 \n \nCAUTION\nBefore continuing, make sure you disconnect the SCSI\nor Fibre cable between the host and the RAID Module;\notherwise the RAID Module will continue to be shown.

$ #define PERFMON_START_MESSAGE 1606
1606 Please press Start to begin monitoring.

$ #define PERFUTIL_USAGE_1      1607
1607 \nperfutil -b <LUN#> <raid controller specifier>

$ #define PERFUTIL_USAGE_2      1608
1608 \nperfutil -c <raid controller specifier>

$ #define PERFUTIL_USAGE_3      1609
1609 \nperfutil -l <LUN#> <raid controller specifier>

$ #define PERFUTIL_USAGE_4      1610
1610 \nperfutil -r <raid controller specifier>

$ #define PERFUTIL_USAGE_5      1611
1611 \nperfutil -?

$ #define PERFUTIL_USAGE_END    1612
1612 \n

$ #define LOGUTIL_FILENAME      1613
1613 Filename: %s\n

$ #define LOGUTIL_RECORDNUM     1614
1614 \nRecord # %d: \n

$ #define LOGUTIL_HOST          1615
1615 Host: %s\n

$ #define LOGUTIL_DEVICE        1616
1616 Device: %s\n

$ #define LOGUTIL_CONTROLLER    1617
1617 Controller: %s\n

$ #define LOGUTIL_ERRORTYPE     1618
1618 Error Type: %s\n

$ #define LOGUTIL_NUMBLOCKS     1619
1619 Number of blocks: %s\n

$ #define LOGUTIL_LUN           1620
1620 LUN: %s\n

$ #define LOGUTIL_ENDINGBLOCK   1621
1621 Ending block: %s\n

$ #define LOGUTIL_DRIVE         1622
1622 Drive: %s\n

$ #define LOGUTIL_MESSAGETEXT   1623
1623 Message text: %s\n

$ #define LOGUTIL_BEGINBLOCK    1624
1624 Beginning Block:  %s\n

$ #define LOGUTIL_ERRORNUM      1625
1625 Error Number: %s\n

$ #define LOGUTIL_CONDITIONCODE 1626
1626 Condition Code:

$ #define LOGUTIL_SENSE         1627
1627 Sense Data:

$ #define PM_HLP_TXT1           1628
1628 Information In Performance Monitor

$ #define CONTROLLER_NOT_FOUND  1630
1630 \nController could not be found\n

$ #define CTLR_A_SYS            1631
1631 Controller A:  %s ( %s )\n

$ #define CTLR_A                1632
1632 Controller A:  %s\n

$ #define CTLR_B_SYS            1633
1633 Controller B:  %s ( %s )\n

$ #define CTLR_B                1634
1634 Controller B:  %s\n

$ #define IND_CONT_MODE_ON      1635
1635 Independent Controller Configuration:  ON\n

$ #define IND_CONT_MODE_OFF     1636
1636 Independent Controller Configuration:  OFF\n

$ #define CONT_A_DOWNLD_MSG     1637
1637 Controller A download completed\nInitializing controller, please wait...

$ #define CONT_B_DOWNLD_MSG     1638
1638 Controller B download completed\nInitializing controller, please wait...

$ #define LUN_NOT_PRESENT       1639
1639 raidutil is unable to delete LUN %d because the LUN doesn't exist.\n

$ #define CFGCNVT_CONTROLLER_NOT_ADDED  1641
1641 Unable to add controller %s to new configuration\n

$ #define CFGCNVT_NOT_ADDED_REASONS     1642
1642 \nHere are the most probable reasons for not being able to reach these controllers:\n  - The controller hostname was not reachable\n    (Check the network connection to the controller)\n  - The controller hostname could not be resolved to an IP address\n    (Check your hosts file or DNS)\n  - This storage manager station was not authorized to configure the controller\n    (Check the BOOTP configuration for the controller)\n\nYou may use the symping utility for each controller to determine the exact\ncause.\n

$ #define EVENT_AEN_4081_CAUSE 1644
1644 The controller has detected a defective memory module. This controller will remain inoperative until you replace it with a new controller.

$ #define EVENT_AEN_4081_ACTION 1645
1645 Please use the Recovery Guru in the Recovery Application as soon as possible to resolve this problem.

$ #define RU_MLUN_246 1646
1646 Successfully deleted LUN %d\n

$ #define MAX_CTL_EXCEEDED 1647
1647 Cannot add another controller, the maximum number of controllers has been reached!\nThis is controlled by the parameter SystemMaxControllers in the rmparams file\n

$ #define FWDL_DOWNGRADE_RESTRICT_HEADER 1648
1648 Downgrade Restriction

$ #define FWDL_INVALIDUPGRADE             1649
1649 This controller model does not support an upgrade\nto the selected firmware version.

$ #define REC_DL_FAIL_INVALID_UPGRADE   1650
1650 Failed -- Controller model does not support\n%supgrade to specified firmware version

$ #define REC_DL_FAIL_INVALID_BOARD_TYPE  1651
1651 Failed -- Controller model does not support\n%sdownload of specified firmware version.\n%sSee the Message Log in the Status\n%sApplication for details.

$ #define REC_DL_FAIL_GENERAL             1652
1652 Failed -- Controller failed the download operation.\n%sSee the Message Log in the Status\n%sApplication for details.

$ #define EVENT_8708_CAUSE                1653
1653 This particular controller model does not support an upgrade to the version of firmware you were attempting to download.

$ #define EVENT_8708_ACTION               1654
1654 Information Only. No action required unless you want to upgrade your hardware to a compatible controller model.

$ #define CONTROLLER_ALREADY_IN_A_MODULE  1655
1655 One of the controllers entered is in a previously registered module.

$ #define NO_MODULES_PRESENT_APP_EXITING  1656
1656 There are no RAID modules currently defined.\nPress OK to exit the application.

$ #define RESET_MSG4                      1657
1657 ERROR TYPE: INVALID DEVICE

$ #define RESET_MSG5                      1658
1658 ERROR TYPE: DLFW_EXCLUSIVE_ACCESS_ERROR

$ #define RESET_MSG6                      1659
1659 ERROR_TYPE: UNIT_RESERVED

$ #define RESET_MSG7                      1660
1660 ERROR_TYPE: LUN_BUSY

$ #define MAINT_CACHE_SAVE_TIME_WARNING   1661
1661 Saving cache parameters usually requires at least 30 seconds per selected LUN.\n                Please wait while the cache parameters are saved.

$ #define MAINT_CACHE_SAVE_FOR_LUN        1662
1662 Saving cache parameters for LUN %d

$ #define HLTH_CHANNEL_FAIL               1663
1663 One or more channels are failed because all drives on the channel are either failed or unresponsive. Use Module Profile to check the status of the LUNs.

$ #define PROF_MSG_49                     1664
1664 Product Revision:

$ #define RU_RDAC_PAGE_FAIL               1665
1665 Reading RDAC page 2E

$ #define RU_CME_FAIL                     1666
1666 Cannot enable cache mirroring.  No alternate controller present.

$ #define ST_MOD_MENU_MSG                 1667
1667 Select, locate, or receive information on the module.

$ #define CFG_RESET_CONFIG                1668
1668 Reset the configuration to a default setting.

$ #define CFG_EXIT_APP                    1669
1669 Quit the Configuration Application.

$ #define CFG_LOCATE_DRV_DISABLED         1670
1670 Option not available. Select a drive group node or individual drive.

$ #define CFG_CREATE_LUN_DISABLED         1671
1671 Option not available. Select unassigned or configured group node with available capacity.

$ #define CFG_CREATE_SPARE_DISABLED       1672
1672 Option not supported or available. Maximum reached or select an unassigned or hot spare group node.

$ #define CFG_MODIFY_LUN                  1673
1673 Modify RAID level, group capacity(add drive), segment size, or defragment unused capacity.

$ #define CFG_MODIFY_LUN_DISABLED         1674
1674 Option not supported or available. Select a configured group node or individual LUN.

$ #define CFG_DELETE_DISABLED             1675
1675 Option not available. Select a configured or hot spare group node or individual LUN.

$ #define CFG_MODIFY_RAID_LEVEL           1676
1676 Change the RAID level of the selected group.

$ #define CFG_MOD_RAID_LEVEL_DISABLED     1677
1677 Option not supported or available. Select a configured group node.

$ #define CFG_MODIFY_CAPACITY             1678
1678 Increase the capacity of a group by adding a drive.

$ #define CFG_MODIFY_CAPACITY_DISABLED    1679
1679 Option not supported or available. Select a configured group node.

$ #define CFG_MODIFY_SEGSIZE              1680
1680 Change the segment size of the selected LUN.

$ #define CFG_MODIFY_SEGSIZE_DISABLED     1681
1681 Option not supported or available. Select a configured group node or individual LUN.

$ #define CFG_DEFRAGMENT                  1682
1682 Consolidate all unused capacity on a configured group.

$ #define CFG_DEFRAGMENT_DISABLED         1683
1683 Option not supported or available. Select a configured group node with unused capacity.

$ #define CFG_FILE_MENU                   1684
1684 Save module profile, reset configuration, or quit application.

$ #define CFG_OPTIONS_MENU                1685
1685 Perform various configuration options.

$ #define GEN_HELP_MENU                   1686
1686 Access help topics.

$ #define GEN_HELP_CONTENTS               1687
1687 Display table of contents.

$ #define CFG_SINGLE_DRV_FLASHING         1688
1688 The light of the drive at location\n[%d,%d] is flashing.

$ #define CFG_DEL_SINGLE_LUN              1689
1689 Delete logical unit %d ?

$ #define CFG_RESET_DISABLED              1690
1690 Option not available. A controller has an inaccessible status.

$ #define LOCATE_DRIVE_HEADER             1691
1691 Locate Drive

$ #define CFG_DEL_SINGLE_LUN_TXT          1692
1692 \n \nThis will destroy all data on the selected\nlogical unit and increase the remaining\ncapacity on the drive group.

$ #define ONE_OR_NO_CONTROLLERS         1693
1693 Option not available. Only one controller is seen or the controller pair is active/passive.

$ #define ALL_CONTROLLERS_ACTIVE        1694
1694 This option is not available because all controllers are active.

$ #define REC_DYNRECONFIG               1695
1695 Modifying

$ #define MSG_DRIVE_OPTIMAL             1696
1696 Optimal

$ #define MSG_DRIVE_FAILED              1697
1697 Failed

$ #define MSG_DRIVE_FAILED_READ         1698
1698 Failed Read

$ #define MSG_DRIVE_FAILED_NORESP       1699
1699 Failed Noresp

$ #define MSG_DRIVE_FAILED_FORMAT       1700
1700 Failed Format

$ #define MSG_DRIVE_FAILED_WRITE        1701
1701 Failed Write

$ #define MSG_DRIVE_FAILED_USER         1702
1702 Failed User

$ #define MSG_DRIVE_FAILED_DACSTOR      1703
1703 Failed DacStor

$ #define MSG_DRIVE_REPLACED            1704
1704 Replaced

$ #define MSG_DRIVE_MISMATCH            1705
1705 Mismatch

$ #define MSG_DRIVE_MISMATCH_SECTOR     1706
1706 Mismatch Sector

$ #define MSG_DRIVE_MISMATCH_CAP        1707
1707 Mismatch Capacity

$ #define MSG_DRIVE_MISMATCH_CHANNEL    1708
1708 Mismatch Channel

$ #define MSG_DRIVE_MISMATCH_ID         1709
1709 Mismatch ID

$ #define MSG_DRIVE_WRONG_REPLACED      1710
1710 Wrong Drive

$ #define MSG_DRIVE_WARNING             1711
1711 Warning

$ #define MSG_DRIVE_UNRESPONSIVE        1712
1712 Unresponsive

$ #define MSG_DRIVE_OFFLINE             1713
1713 Offline

$ #define MSG_DRIVE_UNKNWN              1714
1714 Unknown

$ #define CFG_DRIVES                    1715
1715 Drives

$ #define CFG_UNASSIGNED2               1716
1716 Unassigned

$ #define CFG_LUN_LABEL                 1717
1717 LUN %d

$ #define CFG_GROUP_LABEL               1718
1718 Group %d

$ #define CFG_A                         1719
1719 A

$ #define CFG_B                         1720
1720 B

$ #define CFG_CANNOT_CREATE_LUN_MSG2    1721
1721 You cannot use the Create LUN option when all existing LUNs\non the RAID Module are formatting, inaccessible, dead,\nor being modified.

$ #define DCE_ERROR_TITLE				1722
1722 Modify Group Capacity Error

$ #define DCE_CONFIRM_TITLE				1723
1723 Confirm Modify Group Capacity
 
$ #define DCE_INVALID_DRIVE_SELECTION	1724
1724 This drive group contains RAID 1 LUNs.\nYou must select an even number of drives.
 
$ #define DCE_LAUNCH_CONFIRMATION		1725
1725 This modification may take several minutes up to many\nhours, depending on I/O load and drive group data size.\n \nYou cannot cancel this operation once it begins. However,\nthe drive group's data will remain accessible during\nthis operation.
 
$ #define DCE_OPERATION_ERROR			1726
1726 Could not perform the modification because either\n(1) another modification is being performed using the same controller,\n(2) there is a hot spare drive that has taken over for a failed\ndrive in this drive group,\n(3) a failure has occurred along the connection, or\n(4) another application is using this drive group.\n\n \nIf a failure has occurred, run the Recovery Guru to obtain\ninstructions on how to fix the failure. If another application\nis using this drive group or another modification is in progress\nusing the same controller, wait until that operation is finished.
 
$ #define DRM_ERROR_TITLE				1727
1727 Modify RAID Level Error
 
$ #define DRM_CONFIRM_TITLE				1728
1728 Confirm Modify RAID Level

$ #define DRM_OPERATION_ERROR			1729
1729 Could not perform the RAID migration because either\n(1) another modification is being performed using the same controller,\n(2) there is not enough capacity in the drive group to convert to\nthe new RAID level,\n(3) there is a hot spare drive that has taken over for a failed\ndrive in this drive group,\n(4) a failure has occurred along the connection, or\n(5) another application is using this drive group.\n\n \nIf there is not enough capacity, add another drive to the drive\ngroup using Modify Group/LUN >> GroupCapacity in the Configuration\nApplication. If a failure has occurred, run the Recovery Guru to\nobtain instructions on how to fix the failure. If another application\nis using this drive group or another modification is in progress\nusing the same controller, wait until that operation is finished.
 
$ #define DRM_LAUNCH_CONFIRMATION		1730
1730 This modification may take several minutes up to many\nhours, depending on I/O load and drive group data size.\n \nYou cannot cancel this operation once it begins. However,\nthe drive group's data will remain accessible during\nthis operation.
 
$ #define DSS_ERROR_TITLE				1731
1731 Modify Segment Size Error

$ #define DSS_CONFIRM_TITLE				1732
1732 Confirm Modify Segment Size
 
$ #define DSS_OPERATION_ERROR			1733
1733 Could not perform the modification because either\n(1) another modification is being performed using the same controller,\n(2) there is a hot spare drive that has taken over for a failed\ndrive in this drive group,\n(3) a failure has occurred along the connection, or\n(4) another application is using this drive group.\n \nFor Causes #2 and #3, run the Recovery Guru to obtain instructions\non how to fix the failure. For Causes #1 and #4, wait until that operation\nis finished. If you still are unable to perform this operation, then\nthere is not enough capacity immediately following this LUN on the\ndrive group.
 
$ #define DSS_LAUNCH_CONFIRMATION		1734
1734 This modification may take several minutes up to many\nhours, depending on I/O load and LUN capacity.\n \nYou cannot cancel this operation once it begins. However,\nthe drive group's data will remain accessible during\nthis operation.
 
$ #define DSS_NO_SEG_SIZE_SELECTION		1735
1735 You must select a segment size before\nperforming this operation.
 
$ #define DEFRAG_ERROR_TITLE			1736
1736 Defragment Drive Group Error

$ #define DEFRAG_CONFIRM_TITLE			1737
1737 Confirm Defragment Drive Group
 
$ #define DEFRAG_OPERATION_ERROR		1738
1738 Could not perform the modification because either\n(1) another modification is being performed using the same controller,\n(2) there is a hot spare drive that has taken over for a failed\ndrive in this drive group,\n(3) a failure has occurred along the connection, or\n(4) another application is using this drive group.\n\n \nIf a failure has occurred, run the Recovery Guru to obtain\ninstructions on how to fix the failure. If another application\nis using this drive group or another modification is in progress\nusing the same controller, wait until that operation is finished.

$ #define DEFRAG_LAUNCH_CONFIRMATION	1739
1739 This modification will recover %d megabytes on this drive\ngroup. This modification may take several minutes up to\nmany hours, depending on I/O load and drive group's\ndata size.\n \nYou cannot cancel this operation once it begins. However,\nthe drive group's data will remain accessible during\nthis operation.
 
$ #define DEFRAG_NO_SPACE_TO_RECOVER	1740
1740 There is no space to recover in this drive group.

$ #define DEFRAG_COMPLETE_TITLE			1741
1741 Drive Group Defragment Complete

$ #define CFG_MODIFYLUN_TITLE			1742
1742 Modify Group/LUN Capacity

$ #define CFG_NO_UNASSIGNED				1743
1743 You cannot perform this option because there are\nnot any unassigned drives in the RAID Module.

$ #define CFG_RECONFIG_PROGRESS_FMT		1744
1744     %s - %hd%%
 
$ #define REC_DL_FAIL_LUNSRECONFIG		1745
1745 Failed -- Due to modifying LUNs or groups. Please\nwait until the modification operation is finished and then try again.

$ #define RESET_MSG8				1746
1746 Unable to reset the configuration.\n\nA Capacity Expansion, RAID Level Change, Segment Size Change\nor Defragmentation operation is being performed on a LUN or\ngroup.  Please wait for the operation to finish, and then\nretry the operation.

$ #define REC_REVIVEERROR_RECFG			1747
1747 An error occurred while attempting\nto revive the drive at location %s.\n\nA Capacity Expansion, RAID Level Change, Segment Size Change\nor Defragmentation operation is being performed on a LUN or group.\nPlease wait for the operation to finish, and then retry the operation.

$ #define REC_REVIVELUNERROR_RECFG		1748
1748 An error occurred while attempting\nto revive LUN(s) %s.\nA Capacity Expansion, RAID Level Change, Segment Size Change\nor Defragmentation operation is being performed on a LUN or group.\nPlease wait for the operation to finish, and then retry the operation.

$ #define EVENT_9150_CAUSE			1749
1749 Could not perform an operation because of the group/LUN state. Examples include: Modifying a group/LUN during another modification, creating/deleting LUNs or hot spares during a modification, or failing a drive on a drive group that is already dead.

$ #define EVENT_9150_ACTION			1750
1750 If a modification is occurring, wait for the modification to finish.  If there is a degraded or dead LUN, fix it using the Recovery Guru.


$ ================================================================================================

$ ******************** Recovery Guru Error Messages  *********************************

$ #define RECGURU_INVALID_STATE_TEXT 1755
1755 The Recovery Guru cannot verify the failure type(s).

$ #define RECGURU_DRIVES_NOT_IN_SAME_GROUP 1756
1756 The drives do not belong to the same drive group.

$ #define RECGURU_LUNS_DIFF_STATES 1757
1757 One or more LUNs in the drive group do not have the expected LUN state.


$ ******************** General Recovery Guru  *********************************

$ #define RECGURU_ADDITIONAL_NOTES 1761
1761 Additional Notes

$ #define RECGURU_PROBABLE_CAUSE 1762
1762 Probable Cause 

$ #define RECGURU_STEPS 1763
1763 Recovery Steps
 
$ #define RECGURU_WARNING 1764
1764 CAUTION

$ #define RECGURU_HEADER 1765
1765 Summary Information

$ #define RECGURU_DETAILED_STATUS 1766
1766 Detailed Status

$ #define RECGURU_IMPORTANT 1767
1767 Important

$ #define RECGURU_AFFECTED_COMPONENTS 1768
1768 Affected Components: %s

$ #define RECGURU_HELP_TITLE 1769
1769 Recovery Guru Procedure - 

$ #define RECGURU_INVALID_STATE_HEADER 1770
1770 Verification Failed

$ #define RECGURU_HEADING 1771
1771 Recovery Guru - Summary Information

$ #define RECGURU_TITLE 1772
1772 Recovery Guru

$ #define RECGURU_NO_ENTRY 1773
1773 no entry

$ #define HEALTH_CHECK_TITLE 1774
1774 Health Check 

$ #define NOT_APPLICABLE 1775
1775 N/A 

$ #define RECGURU_ICONRESOURCE 1776
1776 rm6res

$ #define RECBROWSER_INDCTL 1777
1777 independent controllers

$ #define RECBROWSER_NETWORKCTL 1778
1778 networked version

$ #define RECBROWSER_OFFLINE 1779
1779 Offline  

$ #define RECBROWSER_AWAITING_FORMAT 1780
1780 Awaiting Format 




$ *********************** Help ********************

$ #define HELP_HEADER 1800
1800 \\def_style 0 \\font font.normal \\fg color.black \\bg color.transparent  \\def_style 1 \\font font.bold \\fg color.black \\bg color.transparent         \\def_style 2 \\font font.bold \\fg color.blue \\bg color.transparent \\curs curs.magglass \\def_style 3 \\font font.bold \\fg color.blue \\bg color.transparent \\curs helpw.curstopic  \\def_style 4 \\font font.bold \\fg color.red \\bg color.transparent  \\def_style 5 \\font font.italic \\fg color.black \\bg color.transparent 
 
$ #define HELP_CONTENTS_RG 1801
1801 \\topic Home 

$ #define HELP_TITLE 1802
1802 \\0\\p\\1 %s\0 

$ #define HELP_NEWLINE 1803
1803 \\p\\0 

$ #define HELP_NEWPARAGRAPH 1804
1804 \\p\\p\\1 

$ #define HELP_ICON_FILE 1805
1805 \\{\\2\\insert_image %s \\}

$ #define HELP_HYPERTEXT_HEADER 1806
1806 \\p \\{\\3\\subtopic \"%s\" %s\\}

$ #define HELP_HYPERTEXT_BODY 1807
1807 \\topic \"%s\" \\0\\p\\1 %s \\0 \\p\\p

$ #define HELP_BOLD_ON 1808
1808 \\1 

$ #define HELP_BOLD_OFF 1809
1809 \\0 

$ #define HELP_BULLET 1810
1810 \\p\\1 o \\0 

$ #define HELP_CAUTION 1811
1811 \\4 CAUTION \\0 



$ ******************************** Unknown Failure Type

$ #define UNKNOWN_TITLE 1821
1821 Unknown Failure Type

$ #define UNKNOWN_CAUSE 1822
1822 A failure was detected but it is not recognized by the Recovery Guru possibly because of an internal Recovery Guru error. 

$ #define UNKNOWN_WARNING 1823
1823 no entry

$ #define UNKNOWN_IMPORTANT 1824
1824 no entry

$ #define UNKNOWN_STEPS 1825
1825 1. Check your RAID Module for any visible indication of failures.\\p\\p 2. In the Status Application, select Message Log and see if there are any recent entries for failures.\\p\\p - If there are no indications of failures, then you can ignore the Unknown Failure Type.\\p\\p - If you suspect a failure, re-run Recovery Guru. If you still receive the Unknown Failure Type, contact a Customer Support Representative.

$ #define UNKNOWN_NOTES 1826
1826 no entry

$ #define UNKNOWN_ICON 1827
1827 UnknownFailure


$ ******************** Host *********************************

$ #define HOST_HEADER 1828
1828 Host: %s  


$ ******************** Module *********************************


$ #define MODULE_HEADER 1829
1829 Module: %s




$ ******************************** Failed Module

$ #define MODULE_FAILURE_TITLE 1830
1830 Failed Module

$ #define MODULE_FAILURE_CAUSE_NW 1831
1831 Unable to communicate with the only controller or both controllers in the RAID Module. A Failed Module could be caused by one of the following problems:\\p\\p \\1 o \\0 No power to the RAID Module \\p\\p \\1 o \\0 You have physically removed the RAID Module \\p\\p \\1 o \\0 Disconnected or faulty cables \\p\\p \\1 o \\0 Disconnected or faulty transceiver (Networked (Ethernet) connection only)\\p\\p \\1 o \\0 Adapter failure \\p\\p \\1 o \\0 Defective RAID Controller(s)

$ #define MODULE_FAILURE_CAUSE 1832
1832 Unable to communicate with the only controller or both controllers in the RAID Module. A Failed Module could be caused by one of the following problems:\\p \\p \\1 o \\0 No power to the RAID Module \\p\\p \\1 o \\0 You have physically removed the RAID Module \\p\\p \\1 o \\0 Disconnected or faulty cables\\p\\p \\1 o \\0 Disconnected or faulty terminators (SCSI connection only) \\p\\p \\1 o \\0 Adapter failure\\p\\p \\1 o \\0 Hub or fabric switch malfunction (Fibre connection only)\\p\\p \\1 o \\0 Defective RAID Controller(s)

$ #define MODULE_FAILURE_WARNING 1833
1833 no entry 

$ #define MODULE_FAILURE_IMPORTANT 1834
1834 Before attempting any of the Recovery Steps, first make sure that there is power to the RAID Module and correct if necessary. Also, make sure that any operating system (OS) configuration files are set appropriately to recognize all LUNs on the RAID Module (for example, sd.conf for Solaris). 

$ #define MODULE_FAILURE_STEPS 1835
1835 1. If you have physically removed the RAID Module and no longer wish to recognize it within the storage management applications, perform the following actions; otherwise go to step 2.\\p\\p a. In the Recovery Application, choose Select Module.\\p\\p b. Highlight the RAID Module you want to remove and then select Remove.\\p The storage management applications will no longer recognize this RAID Module except for the Message Log option in the Status Application. It will retain past events for this RAID Module but display "No Match Found" for the RAID Module name. \\p\\p 2. Make sure you ran the Recovery Guru with the "All RAID Modules" selection. Then, look at the Summary Information screen of the Recovery Guru and answer the following question: \\p\\p "Are ALL other RAID Modules on the same connection (adapter and cable) reporting either Failed Modules, Offline Controllers, or Unresponsive Controllers?"\\p\\p - Yes; you probably have a defective adapter. Go to step 3. If you want to explore other possible causes before fixing the adapter, go to step 4.\\p\\p - No; go to step 4.

$ #define MODULE_FAILURE_STEPS_2 1836
1836 \\p\\p \\1 Fixing Adapter Problem \\0 \\p 3. Fix the adapter problem and then re-run the Recovery Guru.\\p\\p - If a Failed Module is reported again, then the problem is at the connection or RAID Controller(s). Go to step 4 to check the connection.\\p\\p - If a Failed Module is NOT reported again, then the problem has been fixed. You are done with this procedure. \\p\\p \\1 Checking/Fixing The Connection \\0 \\p 4. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables \\p\\p \\1 o \\0 Terminators (SCSI connection only) \\p\\p \\1 o \\0 Hubs and switches (Fibre connection only)\\p\\p - If there is a problem with the connection, go to step 5.\\p\\p - If these components are OK, the only controller or both controllers in the RAID Module are probably defective. Go to step 6.

$ #define MODULE_FAILURE_STEPS_2NW 1837
1837 \\p\\p \\1 Fixing Adapter Problem \\0 \\p 3. Fix the adapter problem and then re-run the Recovery Guru.\\p\\p - If a Failed Module is reported again, then the problem is at the connection or RAID Controller(s). Go to step 4 to check the connection.\\p\\p - If a Failed Module is NOT reported again, then the problem has been fixed. You are done with this procedure. \\p\\p \\1 Checking/Fixing The Connection \\0 \\p 4. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables \\p\\p \\1 o \\0 Transceivers (Networked (Ethernet) connection only) \\p\\p - If there is a problem with the connection, go to step 5.\\p\\p - If these components are OK, the only controller or both controllers in the RAID Module are probably defective. Go to step 6.
 
$ #define MODULE_FAILURE_STEPS_3 1838
1838 \\p\\p 5. Fix the connection problem (for example, reconnect or replace cable, etc.) and then re-run the Recovery Guru.\\p\\p - If a Failed Module is reported again, then the problem is with the RAID Controller(s). Go to step 6. \\p\\p - If a Failed Module is NOT reported again, then the problem has been fixed. You are done with this procedure. \\p\\p \\1 Replacing The RAID Controller \\0 \\p\\p NOTE: You MUST close all storage management applications (except Recovery) BEFORE replacing the RAID controller. \\p\\p 6. Remove the failed controller(s) (fault LEDs should be on). Make sure at least 1 minute has elapsed before inserting the new controller(s).

$ #define MODULE_FAILURE_STEPS_3NW 1839
1839 \\p\\p NOTE: If you are using the Networked version of the storage management software, you must associate the new controller's hardware Ethernet address with the host name/IP address you assigned to the failed controller BEFORE you go to step 7. The address is located on an Ethernet ID label near the back of the controller canister. Consult the software installation guide for details.

$ #define MODULE_FAILURE_STEPS_4 1840
1840 \\p\\p 7. Insert the new controller(s) firmly into the RAID Module.\\p\\p NOTE: Because you are replacing the only controller or both controllers in the RAID Module, the RAID Module name may change because of the different serial numbers associated with each new controller. \\p\\p 8. Exit all of the storage management applications and restart the application to recognize the new controller(s) and the associated RAID Module. \\p\\p 9. Re-run the Recovery Guru to ensure the failure has been fixed. \\p\\p - If a Failed Module is reported again, you could have an adapter problem. Go back to step 3 if you hadn't serviced the adapter. Otherwise, contact a Customer Support Representative if you have checked and replaced, if necessary, all components along the connection. \\p\\p - If any other type of problem is reported (such as a mismatch of controller firmware versions), fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.

$ #define MODULE_FAILURE_NOTES 1841
1841 \\1 o \\0 If you replaced the controller and the filesystems/logical units do not respond, you may need to reboot your system.\\p\\p \\1 o \\0 If you replaced BOTH controllers in your RAID Module, you must reboot the system to enable RDAC protection on the module.

$ #define MODULE_ICON 1842
1842 FailModule


$ ******************************** Locked Module

$ #define MODULE_LOCKED_TITLE 1843
1843 Locked Module

$ #define MODULE_LOCKED_CAUSE 1844
1844 Certain operations (such as downloading firmware or formatting logical units) use special files called locked files (*.lock) to prevent concurrent access to the logical units or other settings until the current operation is complete. Once the operation is complete, the lock is automatically cleared. The procedure of using these lock files is normal. However, during an application or system crash, the lock files may not get cleared.

$ #define MODULE_LOCKED_WARNING 1845
1845 If the locked module is due to a current storage management operation requiring the temporary locks, do not clear the locks or reboot the system as described in the following steps.

$ #define MODULE_LOCKED_IMPORTANT 1846
1846 no entry

$ #define MODULE_LOCKED_STEPS 1847
1847 1. If there are storage management operations currently in progress, wait for all of these operations to complete and then re-run the Recovery Guru. Under normal operations, the locks will be automatically cleared and Recovery Guru will not report a Locked Module. However, if the Locked Module failure persists and there are NO storage management operations being performed or you have NOT experienced an application or system crash, go to step 2.\\p\\p 2. Clear the locks using ONE of the methods described below:\\p\\p a. Exit all storage management applications in progress. Run the 'clean' script from your installation directory where you installed the storage management applications. This script will stop and restart the Disk Array Monitor and clear all existing locks. If necessary, refer to the installation guide for details.\\p\\p b. Reboot your operating system. All the internal storage management lock files (*.lock files and the contents of the lunlocks file) are deleted. During the shutdown, the Disk Array Monitor, RDAC driver, and any open storage management applications are stopped. When the system restarts, the Disk Array Monitor and RDAC driver are automatically restarted. You can restart the storage management applications by selecting their appropriate icons.

$ #define MODULE_LOCKED_NOTES 1848
1848 no entry

$ #define MODULE_LOCKED_ICON 1849
1849 LockedModule



$ ******************************** Module fw mismatch

$ #define MODULE_FW_MISMATCH_TITLE 1851
1851 Firmware Mismatch

$ #define MODULE_FW_MISMATCH_CAUSE 1852
1852 The versions of firmware on the controllers in the RAID Module do not match. This is probably because you replaced a failed controller with a new controller that does not have the same version of firmware.

$ #define MODULE_FW_MISMATCH_WARNING 1853
1853 Controllers with different versions of firmware may cause unexpected results. Therefore, use this recovery procedure as soon as possible to make the versions consistent.

$ #define MODULE_FW_MISMATCH_IMPORTANT 1854
1854 \\1 o \\0 If you are upgrading from one major release to another, you may have to download a new NVSRAM file before upgrading the firmware. If the NVSRAM file is not included with the controller firmware upgrade files, then contact a Customer Support Representative. The NVSRAM file specifies certain default settings for the controller. You can use the following recovery steps to download NVSRAM or firmware files.\\p\\p \\1 o \\0 Make sure you have copied the NVSRAM file to your system before attempting to download it. \\p\\p \\1 o \\0 With any new controller firmware upgrade, you should receive one to three firmware files (appware, bootware, and fibre channel) and the fwcompat.def file. The fwcompat.def file allows this software to compare the firmware files for compatibility and also provides you with a list of compatible files to select for downloading. You must download at least the appware and bootware files.\\p\\p \\1 o \\0 If you received new firmware files (including the fwcompat.def file), copy them to the appropriate subdirectory on your system before attempting to perform the firmware upgrade. The storage management software automatically searches a default subdirectory under the directory where you installed the software (if needed, open the rmparams file and check the parameter "System_RmFirmwareDirectory=" for the name of the subdirectory).

$ #define MODULE_FW_MISMATCH_STEPS 1856
1856 1. In the Maintenance/Tuning Application, make sure the affected RAID Module is selected.\\p\\p 2. Select the Firmware Upgrade toolbar button, read the important notes, and select OK.\\p\\p 3. Select either the Online or the Offline method (Offline method recommended).\\p\\p 4. In the main firmware screen, check the current version of firmware for each controller.\\p\\p 5. Select one or both controllers as needed. If you inserted a controller with 3.X firmware into a RAID Module whose other controller has 2.X firmware, you must select both controllers.\\p\\p NOTE: If the list in the Compatible Files/Versions area is blank, then the appropriate subdirectory does not contain all the necessary firmware files. Remember, the initial search is made in a default subdirectory where you installed the storage management software.\\p\\p 6. Select the firmware files to download from the list in the Compatible Files/Versions area or enter the appropriate files (for example, the NVSRAM file) including the complete path name on the Path line and select OK. A progress screen is displayed and then eventually a summary screen. \\p\\p \\1 Important \\0 \\pMake sure that the firmware is compatible with your current storage management software. You may need to obtain another version of the storage management software (consult the software installation guide for details). \\p\\p 7. If you downloaded an NVSRAM file, perform the following steps; otherwise, go to step 8. \\p\\p a. Run the nvutil command line utility to EACH controller: nvutil -vf 'controller device name' \\p This utility will verify and correct the NVSRAM settings for the operating system you are using. If you need information on the device name, select Module Profile and look at the Summary Information screen. \\p\\p b. If nvutil reports that it made changes, turn the controller power switches or the RAID Module off and then on again.\\p\\p 8. Re-run the Recovery Guru to ensure that the failure has been fixed.

$ #define MODULE_FW_MISMATCH_NOTES 1858
1858 no entry

$ #define MODULE_FW_MISMATCH_ICON 1859
1859 Firmwaremiss 



$ ******************** Controller ****************************

$ #define CTL_HEADER 1860
1860 Controller: %s



$ ******************* Controller Offline (held in reset) 

$ #define CTL_OFFLINE_TITLE 1861
1861 Offline Controller

$ #define CTL_OFFLINE_WARNING 1862
1862 At this time, there may be a fault light indicating a controller failure. However, do NOT replace the controller until you are instructed to do so in the following steps.

$ #define CTL_OFFLINE_IMPORTANT 1863
1863 \\1 o \\0 You can diagnose and correct the problem while the RAID Module is on and receiving I/O.

$ #define CTL_OFFLINE_NOTES 1864
1864 If you replaced the controller and the filesystems/logical units do not respond, you may need to reboot your system.

$ #define CTL_OFFLINE_ICON 1865
1865 OffCtrl


$ #define CTL_OFFLINE_STEPS 1866
1866 This procedure will first instruct you to check the adapters, then check the components along the connection, and eventually instruct you how to replace the controller, if necessary.\\p\\p 1. Make sure you ran the Recovery Guru with the "All RAID Modules" selection. Then, look at the Summary Information screen of the Recovery Guru and answer the following question: \\p\\p "Are ALL other RAID Modules on the same connection (adapter and cable) reporting either Failed Modules, Offline Controllers, or Unresponsive Controllers?"\\p\\p - Yes; you probably have a defective adapter. Go to step 2. If you want to explore other possible causes before fixing the adapter, go to step 3.\\p\\p - No; go to step 3.\\p\\p \\1 Fixing Adapter Problem \\0 \\p 2. Fix the adapter problem and then perform the following actions: \\p\\p a. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar.\\p\\p b. Highlight the controller with an Offline status and select Place Online. The transition to Online may take several minutes.

$ #define CTL_OFFLINE_STEPS_3 1867
1867 \\p\\p 4. Fix the connection problem (for example, reconnect or replace cable, etc.) and then perform the following actions:\\p\\p a. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar. \\p\\p b. Highlight the controller with an Offline status and select Place Online. The transition to Online may take several minutes.\\p\\p - If the controller does NOT return to the Online status, then you probably have a defective RAID controller or a defective adapter. Go back to step 2 if you suspect an adapter problem. Go to step 5 to replace the RAID controller.\\p\\p - If the controller returns to the Online status, go to step 9. \\p\\p \\1 Replacing The RAID Controller \\0 \\p\\p NOTE: You MUST close all storage management applications (except Recovery) BEFORE replacing the RAID controller. \\p\\p  5. Remove the failed controller (its fault LEDs should be on). Make sure at least 1 minute has elapsed before inserting the new controller.

$ #define CTL_OFFLINE_STEPS_4 1868
1868 \\p\\p 6. Insert the new controller firmly into the RAID Module.\\p\\p 7. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar.\\p\\p 8. Highlight the controller with an Offline status and select Place Online. The transition to Online may take several minutes. \\p\\p - If the controller does NOT return to the Online status, then you probably have a defective adapter (go back to step 2).\\p\\p - If the controller returns to the Online status, go to step 9.\\p\\p 9. Re-run the Recovery Guru to ensure the failure has been fixed. Performing this step is especially important if you have replaced the controller.\\p\\p If any other type of problem is reported (such as a mismatch of controller firmware versions), fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.


$ ********** non-network, non-indep offline ctl entries ***********

$ #define CTL_OFFLINE_CAUSE 1869
1869 A RAID Controller has been placed in the Offline status because of one of the following problems:\\p\\p \\1 o \\0 Disconnected or faulty cables\\p\\p \\1 o \\0 Disconnected or faulty terminators (SCSI connection only) \\p\\p \\1 o \\0 Adapter failure\\p\\p \\1 o \\0 Hub or fabric switch malfunction (Fibre connection only)\\p\\p \\1 o \\0 Defective RAID Controller

$ #define CTL_OFFLINE_STEPS_2 1870
1870 \\p\\p - If the controller does NOT return to the Online status, then the problem is at the connection or RAID controller. Go to step 3 to check the connection.\\p\\p - If the controller returns to the Online status, go to step 9.\\p\\p \\1 Checking/Fixing The Connection \\0 \\p 3. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables \\p\\p \\1 o \\0 Terminators (SCSI connection only)\\p\\p \\1 o \\0 Hubs and switches (Fibre connection only)\\p\\p - If there is a problem with the connection, go to step 4.\\p\\p - If these components are OK, you probably have a defective RAID Controller. Go to step 5.


$ ********** network offline ctl entries ***********

$ #define CTL_OFFLINE_CAUSE_NW 1871
1871 A RAID Controller has been placed in the Offline status because of one of the following problems:\\p\\p \\1 o \\0 Disconnected or faulty cables\\p\\p \\1 o \\0 Disconnected or faulty transceiver (Networked (Ethernet) connection only)\\p\\p \\1 o \\0 Adapter failure \\p\\p \\1 o \\0 Defective RAID Controller

$ #define CTL_OFFLINE_IMPORTANT_NW 1872
1872 \\p\\p \\1 o \\0 The host adapters described in this recovery procedure refer to host adapters contained in the host performing the I/Os to this module. This host must be running the RDAC driver in order for a fail-over (placing the dead controller Offline) to have occurred due to failed I/Os. If RDAC is not running on any host attached to this module, then it is likely the controller was placed Offline manually via a network storage management application.

$ #define CTL_OFFLINE_STEPS_2NW 1873
1873 \\p\\p - If the controller does NOT return to the Online status, then the problem is at the connection or RAID controller. Go to step 3 to check the connection.\\p\\p - If the controller returns to the Online status, go to step 9.\\p\\p \\1 Checking/Fixing The Connection \\0 \\p 3. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables\\p\\p \\1 o \\0 Transceivers (Networked (Ethernet) connection only)\\p\\p - If there is a problem with the connection, go to step 4.\\p\\p - If these components are OK, you probably have a defective RAID Controller. Go to step 5.

$ #define CTL_OFFLINE_STEPS_4NW 1874
1874 \\p\\p NOTE: When using the Networked version of the storage management software, you must associate the new controller's hardware Ethernet address with the host name/IP address you assigned to the failed controller BEFORE you go to step 6. The address is located on an Ethernet ID label near the back of the controller canister. Consult the software installation guide for details.



$ ********************** Unresponsive/Dead Controller **********************

$ #define CTL_UNRESP_TITLE 1875
1875 Unresponsive Controller

$ #define CTL_UNRESP_CAUSE 1876
1876 An unresponsive controller can be caused by the following:\\p\\p \\1 o \\0 Disconnected or improperly seated controller\\p\\p \\1 o \\0 Disconnected or faulty cables\\p\\p \\1 o \\0 Disconnected or faulty terminators (SCSI connection only) \\p\\p \\1 o \\0 Hub or fabric switch malfunction (Fibre connection only)\\p\\p \\1 o \\0 Adapter failure\\p\\p \\1 o \\0 Defective RAID Controller

$ #define CTL_UNRESP_CAUSE_NW 1877
1877 An unresponsive controller can be caused by the following:\\p\\p \\1 o \\0 Disconnected or improperly seated controller\\p\\p \\1 o \\0 Disconnected or faulty cables \\p\\p \\1 o \\0 Disconnected or faulty transceiver (Networked (Ethernet) connection only)\\p\\p \\1 o \\0 Adapter failure\\p\\p \\1 o \\0 Defective RAID Controller

$ #define CTL_UNRESP_WARNING 1878
1878 Incorrect NVSRAM settings on the controller can result in Unresponsive controllers. If you follow the steps below and are still having problems, contact a Customer Support Representative.

$ #define CTL_UNRESP_IMPORTANT 1881
1881 \\1 o \\0 The status displayed for the RAID controller may be Unresponsive or Dead. \\p\\p\\1 o \\0 A power cycle of the RAID module during the operating system's device scan (for example, during a host reboot) may cause the storage management software to detect an Unresponsive controller. Rebooting the operating system after the RAID module has completed its initialization may fix the problem.

$ #define CTL_UNRESP_STEPS 1882
1882 1. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables \\p\\p \\1 o \\0 Terminators (SCSI connection only)\\p\\p \\1 o \\0 Hubs and switches (Fibre connection only)\\p\\p 2. Fix any connection problems (for example, reconnect or replace cable, etc.).\\p\\p 3. Re-run the Recovery Guru to ensure the failure has been fixed.\\p\\p If the failure is still reported, place the unresponsive controller offline using the Options >> Manual Recovery >> Controller Pairs option and re-run the Recovery Guru. Highlight the Offline Controller failure and select Show Procedure. Use the steps in the controller replacement section of that procedure to replace the controller. Consult a Customer Support Representative, if necessary.\\p\\p - If any other problem is reported, fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.

$ #define CTL_UNRESP_STEPS_NW 1883
1883 1. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables \\p\\p \\1 o \\0 Transceivers (Networked (Ethernet) connection only) \\p\\p 2. Fix any connection problems (for example, reconnect or replace cable, etc.).\\p\\p 3. Re-run the Recovery Guru to ensure the failure has been fixed.\\p\\p - If an Unresponsive controller is still reported, place the unresponsive controller offline using the Options >> Manual Recovery >> Controller Pairs option and re-run the Recovery Guru. Highlight the Offline Controller failure and select Show Procedure. Use the steps in the controller replacement section of that procedure to replace the controller. Consult a Customer Support Representative, if necessary.\\p\\p - If any other problem is reported, fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.

$ #define CTL_UNRESP_NOTES 1884
1884 \\1 o \\0 If the failure has been resolved and the filesystems/logical units do not respond, you may need to reboot your system. If you have two controllers, select LUN Balancing in the Maintenance and Tuning Application to make sure the logical units are balanced across both controllers. \\p\\p\\1 o \\0 Run the command line utility "lad" to verify all controllers are visible to the storage management software. 

$ #define CTL_UNRESP_ICON 1885
1885 UnrespCtrl


$ ************************ Controller nvsram changed

$ #define CTL_NVRAM_TITLE 1891
1891 Incorrect NVSRAM Settings

$ #define CTL_NVRAM_CAUSE 1892
1892 Incorrect NVSRAM settings have been detected. This can be caused by\\p\\p \\1 o \\0 downloading an incorrect NVSRAM file to the RAID controller\\p\\p \\1 o \\0 replacing a RAID controller with a controller whose NVSRAM settings are incorrect\\p\\p \\1 o \\0 moving the RAID Module to a host with a different operating system

$ #define CTL_NVRAM_WARNING 1893
1893 no entry

$ #define CTL_NVRAM_IMPORTANT 1894
1894 no entry

$ #define CTL_NVRAM_STEPS 1895
1895 1. Run the nvutil command line utility to EACH controller: nvutil -vf 'controller device name'\\p This will verify and correct the NVSRAM settings for the operating system you are using. If you need information on the device name, select Module Profile and look at the Summary Information screen. \\p\\p 2. Make sure all I/O is stopped. Then, turn the controller power switches or the RAID Module off and then on again.\\p\\p 3. Re-run the Recovery Guru to ensure that the failure has been fixed.

$ #define CTL_NVRAM_NOTES 1896
1896 no entry

$ #define CTL_NVRAM_ICON 1897
1897 Nvsram


$ ************** Controller RPA Parity Error ***********************
 
$ #define CTL_RPA_TITLE 1901
1901 Defective Memory Module
 
$ #define CTL_RPA_CAUSE 1902
1902 A defective memory module has been detected on the controller. This controller will remain inoperative until you replace it with a new controller.

$ #define CTL_RPA_WARNING 1903
1903 no entry
 
$ #define CTL_RPA_IMPORTANT 1904
1904 \\1 o \\0 Refer to the applicable hardware manual for any additional notes on servicing the memory module. \\p\\p \\1 o \\0 If you have two controllers in your RAID Module, you can remove the failed controller while the RAID Module is on and receiving I/O.

$ #define CTL_RPA_STEPS 1905
1905 1. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar to determine if the controller listed has an Offline status.\\p\\p - If the controller has an Offline status, go to step 2. \\p\\p - If the controller does NOT have an Offline status, highlight the controller and select Place Offline. The transition to Offline may take several minutes. Go to step 2.\\p\\p 2. Remove the failed controller (its fault LEDs should be on). Make sure at least 1 minute has elapsed before inserting the new controller.

$ #define CTL_RPA_STEPS_NW 1906
1906 \\p\\p NOTE: If you are using the Networked version of the storage management software, you must associate the new controller's hardware Ethernet address with the host name/IP address you assigned to the failed controller BEFORE you go to step 3. The address is located on an Ethernet ID label near the back of the controller canister. Consult the software installation guide for details.

$ #define CTL_RPA_STEPS_2 1907
1907 \\p\\p 3. Insert the new controller firmly into the RAID Module.\\p\\p 4. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar.\\p\\p 5. Highlight the controller with an Offline status and select Place Online. The transition to Online may take several minutes.\\p\\p - If the controller returns to the Online status, go to step 6.\\p\\p - If the controller does NOT return to the Online status, then you have probably not inserted (seated) the controller correctly; repeat steps 3-5.\\p\\p 6. Re-run the Recovery Guru to ensure the failure has been fixed.\\p\\p If any other type of problem is reported (such as a mismatch of controller firmware versions), fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.

$ #define CTL_RPA_NOTES 1908
1908 no entry
 
$ #define CTL_RPA_ICON 1909
1909 CtrlMem
 
$ ************** Controller F/W Incompatability ***********************
 
$ #define CTL_INCOMPAT_SW_TITLE 1911
1911 Incompatible Firmware
 
$ #define CTL_INCOMPAT_SW_CAUSE 1912
1912 The versions of firmware on the controllers in the RAID Module are incompatible. One controller has version 2.X and the other controller has version 3.X. This is probably because you replaced a failed controller with a new controller that does not have the same version of firmware.
 
$ #define CTL_INCOMPAT_SW_WARNING 1913
1913 Controllers with an incompatible version of firmware (2.X and 3.X) may cause unexpected results. Therefore, use this recovery procedure as soon as possible to make the versions consistent.
 
$ #define CTL_INCOMPAT_SW_IMPORTANT 1914
1914 \\1 o \\0 If you are upgrading from one major firmware release to another, you may have to download a new NVSRAM file before upgrading the firmware. If the NVSRAM file is not included with the controller firmware upgrade files, then contact a Customer Support Representative. The NVSRAM file specifies certain default settings for the controller. You can use the following recovery steps to download NVSRAM or firmware files.\\p\\p \\1 o \\0 Make sure you have copied the NVSRAM file to your system before attempting to download it. \\p\\p \\1 o \\0 With any new controller firmware upgrade, you should receive one to three firmware files (appware, bootware, and fibre channel) and the fwcompat.def file. The fwcompat.def file allows this software to compare the firmware files for compatibility and also provides you with a list of compatible files for downloading. You must download at least the appware and bootware files.\\p\\p \\1 o \\0 If you received new firmware files (including the fwcompat.def file), copy them to the appropriate subdirectory on your system before attempting to perform the firmware upgrade. The storage management software automatically searches a default subdirectory under the directory where you installed the software (if needed, open the rmparams file and check the parameter "System_RmFirmwareDirectory=" for the name of the subdirectory).
 
$ #define CTL_INCOMPAT_SW_STEPS 1916
1916  1. In the Maintenance/Tuning Application, make sure the affected RAID Module is selected.\\p\\p 2. Select the Firmware Upgrade toolbar button, read the important notes, and select OK.\\p\\p \\1 Important \\0\\pBefore going to step 3, you must stop all I/O going to the RAID Module. In addition, if the RAID Module is connected to a clustered environment, you must temporarily stop the cluster service during the firmware upgrade (consult the system documentation for details on how to stop the service). Once the upgrade has completed, you can restart the service.\\p\\p 3. Select the Offline method (required).\\p\\p 4. In the main firmware screen, check the current version of firmware for each controller.\\p\\p - If the new replacement controller has 3.X firmware, you must download 3.X firmware to both controllers.\\p\\p \\1 Important \\0\\pIt is highly recommended that you also obtain and install the latest version of this storage management software. This will prevent any compatibility issues and allow you to use the new features found in the 3.X firmware (consult the software installation guide for details).\\p\\p - If the new replacement controller has 2.X firmware, you must download 3.X firmware only to the replacement controller.\\p\\p 5. Select the appropriate controller as described above. \\p\\p NOTE: If the list in the Compatible Files/Versions area is blank, then the appropriate subdirectory does not contain all of the necessary firmware files. Remember, the initial search is made in a default subdirectory where you installed the storage management software.\\p\\p 6. Select the firmware files to download from the list in the Compatible Files/Versions area or enter the appropriate files (for example, the NVSRAM file) including the complete path name on the Path line and select OK. A progress screen is displayed and then eventually a summary screen.\\p\\p 7. If you downloaded an NVSRAM file, perform the following steps; otherwise, go to step 8.\\p\\p a. Run the nvutil command line utility to EACH controller: nvutil -vf 'controller device name'\\p This will verify and correct the NVSRAM settings for the operating system you are using. If you need information on the device name, select Module Profile and look at the Summary Information screen.\\p\\p b. If nvutil reports that it made changes, turn the controller power switches off and then on again.\\p\\p 8. Re-run the Recovery Guru to ensure that the failure has been fixed.
 
$ #define CTL_INCOMPAT_SW_NOTES 1918
1918 no entry
 
$ #define CTL_INCOMPAT_SW_ICON 1919
1919 IncompatFW





$ ********************* LUNs ***********************

$ #define LUN_HEADER 1920
1920 Affected LUNs: %s 

$ #define LUN_HEADER_STATUS 1921
1921 LUN Status: %s

$ #define LUN_HEADER_RAID_LEVEL 1922
1922 RAID Level: %s 

$ #define LUN_ICON 1923
1923 lun

$ #define LUN_HOT_SPARE_IN_USE 1924
1924 (Hot Spare In Use)




$ ****************** Degraded Luns ************************

$ #define LUN_DEGRADED_TITLE 1931
1931 Degraded LUN

$ #define LUN_DEGRADED_CAUSE 1932
1932 A drive has failed causing the Degraded LUN(s). The data on the LUNs is still accessible.

$ #define LUN_DEGRADED_CAUSE_MULTI 1933
1933 Drives have failed causing the Degraded LUN(s). The data on the LUNs is still accessible.

$ #define LUN_DEGRADED_WARNING 1934
1934 no entry

$ #define LUN_DEGRADED_IMPORTANT 1935
1935 \\1 o \\0 Make sure the replacement drive has a capacity equal to or greater than the failed drive you will remove in the following steps.\\p\\p \\1 o \\0 You can remove the failed drive while the RAID Module is on and receiving I/O.

$ #define LUN_DEGRADED_STEPS_MULTI 1936
1936 For each failed drive in this drive group (see drive list above):\\p\\p

$ #define LUN_DEGRADED_STEPS 1937
1937 1. Remove the failed drive (its fault light should be on).\\p\\p 2. Make sure at least 30 seconds have elapsed; then, insert the new drive (its fault light may come on for a short time (one minute or less)).\\p\\p NOTE: Data reconstruction should begin on the new replacement drive (its fault light will go off and the active lights of the other drives in the drive group will start flashing). Use the LUN Reconstruction option in the Status Application to check the reconstruction progress or change the rate. If reconstruction does NOT start, use Options >> Manual Recovery >> Drives from the top menu bar in the Recovery Application to start reconstruction on the replacement drive.\\p\\p 3. Re-run the Recovery Guru to ensure the failure has been fixed.

$ #define LUN_DEGRADED_NOTES 1938
1938 For RAID Levels 3 and 5, a single drive failure will cause a Degraded LUN.  It is possible, however, for a Degraded RAID Level 1 LUN to have multiple failed drives if the failed drives belong to different mirrored pairs.

$ #define LUN_DEGRADED_ICON 1939
1939 DegradedLUN


$ ******************** Dead Luns (generic dead lun)

$ #define LUN_DEAD_TITLE 1940
1940 Dead LUN

$ ******************** Dead Luns - Failed Drives

$ #define LUN_DEAD_DRIVES_TITLE 1941
1941 Dead LUN - Failed Drives

$ #define LUN_DEAD_DRIVES_CAUSE 1942
1942 Drive(s) have failed causing the Dead LUN(s) or a Wrong Drive Replaced condition has occurred.

$ #define LUN_DEAD_DRIVES_WARNING 1943
1943 \\1 o \\0 Some data on the LUN(s) has been lost. This procedure will recommend formatting the affected LUN(s) and restoring the data from back up. \\p\\p\\1 o \\0 Wait until the Replaced drives are ready (Fault light Off) before attempting to Format the LUN(s). \\p\\p\\1 o \\0 When failed drives in a Dead RAID 0 LUN are replaced, the LUN automatically transitions to Optimal even though the LUN has NOT been formatted (see recovery step 3 below). 

$ #define LUN_DEAD_DRIVES_IMPORTANT 1944
1944 \\1 o \\0 To your operating system (OS), a Dead LUN is exactly the same as a normal (non-RAID) Failed drive. Refer to your OS documentation for any special requirements concerning a Failed drive and perform them where instructed to do so.\\p\\p \\1 o \\0 Make sure the Replacement drive has a capacity equal to or greater than the Failed drive you will remove in the following steps.\\p\\p \\1 o \\0 You can remove the Failed drive while other LUN(s) in the RAID Module are receiving I/O. \\p\\p \\1 o \\0 A Dead LUN can be caused by a Wrong Drive Replaced condition (an Optimal drive in a Degraded LUN replaced in error). If this has occurred, you should either see another Recovery Guru failure type entry for Wrong Drive Replaced (select this failure first) or a previously Optimal drive will now have a Replaced state (see Help >> Recovery Guru Procedures >> Wrong Drive Replaced for instructions). \\p\\p\\1 o \\0 Fix any channel failures reported in the Summary Information screen of the Recovery Guru before proceeding with the steps below. Fixing the channel failure first may prevent restoring data from back up.

$ #define LUN_DEAD_DRIVES_STEPS 1945
1945 Perform steps 1 and 2 for each Failed drive in this drive group (see drive list above):\\p\\p 1. Remove ONE Failed drive (its fault light should be on). \\p\\p 2. Make sure at least 30 seconds have elapsed; then, insert the new drive (its fault light may come on for a short time (one minute or less)). \\p\\p 3. Format all LUN(s) in this drive group: \\p\\1 o \\0 In the Recovery Application, make sure the affected RAID Module is selected. \\p\\p \\1 o \\0 Select Options >> Manual Recovery >> Logical Units from the top menu bar. Highlight the LUN(s) with a Dead status and then select Format. The LUN states will transition from Dead to Formatting, then Optimal.\\p NOTE: If the replaced drive(s) belongs to a RAID 0 LUN(s) the LUN(s) will already be Optimal, however, the LUN(s) must still be highlighted and formatted.\\p\\p 4. Re-run the Recovery Guru to ensure the failure has been fixed. \\p\\p 5. Add the LUN(s) back to the operating system. You may need to reboot the system to see the LUN(s).\\p NOTE: Do NOT start I/O to these LUN(s) until restoring from back up. \\p\\p 6. Restore the data for these LUN(s) from back up.

$ #define LUN_DEAD_DRIVES_NOTES 1946
1946 \\p\\p \\1 o \\0 The Recovery Guru will display a Wrong Drive Replaced failure only if an Optimal drive is removed from the Degraded LUN's drive group and NOT replaced. The LUN transitions from Degraded to Dead. Once a drive is inserted into this slot, it will transition from Wrong Drive Replaced to Replaced (the LUN remains Dead). \\p\\p\\1 o \\0 Dead RAID 0 LUNs transition from Dead to Optimal after replacing the failed drives. Even though Optimal, the LUNs must be formatted and data restored from back up before use.\\p\\p \\1 o \\0 A Dead LUN can occur during a modification process (for example, changing a RAID level or capacity expansion) as a result of failed drives. In this case you should replace the failed drives and allow the modification to restart and complete before formatting the LUN(s).

$ #define LUN_DEAD_DRIVES_ICON 1947
1947 DeadLUN



$ ********************** Dead Lun - Awaiting Format (no failed drives) 


$ #define LUN_DEAD_FORMAT_TITLE   1951
1951 Dead LUN - Awaiting Format

$ #define LUN_DEAD_FORMAT_CAUSE   1952
1952 This condition is caused by either (1) unformatted LUNs containing drives with a Replaced status. This is a result of failed drives that were replaced but the LUN was never formatted, or (2) failed or unresponsive drives that were caused by a channel failure.

$ #define LUN_DEAD_FORMAT_WARNING 1953
1953 no entry

$ #define LUN_DEAD_FORMAT_IMPORTANT 1954
1954 Fix any channel failures reported in the Summary Information screen of the Recovery Guru before proceeding with the steps below. Fixing the channel failure first may prevent restoring data from back up.

$ #define LUN_DEAD_FORMAT_STEPS   1955
1955 1. Format all LUNs in this drive group: \\p\\1 o \\0 In the Recovery Application, make sure the affected RAID Module is selected. \\p\\p \\1 o \\0 Select Options >> Manual Recovery >> Logical Units from the top menu bar. Highlight the LUNs with a Dead status and then select Format. The LUN states will transition from Dead to Formatting, then Optimal.\\p\\p 2. Re-run the Recovery Guru to ensure the the failure has been fixed. \\p\\p 3. Add the LUN(s) back to the operating system (you may need to reboot the system to see the LUNs).\\p NOTE: Do NOT start I/O to these LUNs until restoring from back up. \\p\\p 4. Restore the data for these LUNs from back up.

$ #define LUN_DEAD_FORMAT_NOTES   1956
1956 \\1 o \\0 If the Format attempt fails and this drive group contains multiple LUNs, try the following:\\p\\p a. Highlight the Replaced drives and select Fail. Wait for the drives to transition to a Failed status.\\p\\p b. Highlight these drives again and select Revive.\\p\\p c. Format these LUNs. \\p\\p \\1 o \\0 If you attempt to Format the LUN(s) before the replaced drives are ready (completed spinning up), a "format error" panel will appear. If this occurs, wait until the replaced drives are ready (fault light Off) and try to Format again.

$ #define LUN_DEAD_FORMAT_ICON    1957
1957 DeadLUN



$ *********************** Lun Wrong Drive Replaced 

$ #define LUN_WDR_TITLE 1961
1961 Wrong Drive Replaced

$ #define LUN_WDR_CAUSE 1962
1962 A non-failed drive was inadvertently removed. This probably occurred while attempting to replace a failed drive.

$ #define LUN_WDR_WARNING 1963
1963 Do not Fail and Revive a Replaced drive unless absolutely sure the drive has good data and is in the correct slot. It is generally recommended to Reconstruct a Failed or Replaced drive if the LUN(s) are Degraded than to Revive a Failed drive.

$ #define LUN_WDR_IMPORTANT 1964
1964 \\1 o \\0 A Wrong Drive Replaced state can occur if an Optimal drive is removed (and NOT replaced) from a drive group containing Degraded LUN(s). The LUN(s) will transition to Dead. If the removed drive is replaced either with the original or with a different drive, the drive will transition to Replaced (LUN(s) remain Dead). \\p\\p \\1 o \\0 A drive belonging to an Unassigned drive group, if removed, will no longer be visible to the storage management applications.

$ #define LUN_WDR_STEPS 1965
1965 1. Locate the empty drive slot and insert the original drive. If the original drive has been replaced by another drive, remove the Replaced drive and insert the original drive.\\p\\p 2. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Drives from the top menu bar.\\p\\p - If the drive has an Optimal status, go to step 3.\\p\\p - If the drive has a Replaced status, do the following.\\p\\p a. Highlight that drive and select Fail. Wait for the drive to transition to a Failed status. \\p\\p b. Highlight the drive again and select Revive.\\p\\p 3. Re-run the Recovery Guru to ensure this Wrong Drive Replaced failure has been fixed. If so, you should expect to see a Degraded LUN entry in the Recovery Guru Summary Information Screen.

$ #define LUN_WDR_NOTES 1966
1966 If the Wrong Drive Replaced condition persists, contact a Customer Support Representative.

$ #define LUN_WDR_ICON 1967
1967 WrongDrive



$ *********************** Hotspare Lun 

$ #define LUN_HOTSPARE_TITLE 1971
1971 LUN - Hot Spare In Use

$ #define LUN_HOTSPARE_CAUSE 1972
1972 A drive in the logical unit has failed and a hot spare drive has automatically taken over for it. The data on the LUN(s) is still accessible.

$ #define LUN_HOTSPARE_WARNING 1973
1973 no entry

$ #define LUN_HOTSPARE_IMPORTANT 1974
1974 \\1 o \\0 Depending on how many hot spare drives you have configured, a logical unit could remain Optimal and still have several failed drives (each one being covered by a hot spare).\\p\\p \\1 o \\0 Make sure the replacement drive has a capacity equal to or greater than the failed drive you will remove in the following steps.\\p\\p \\1 o \\0 You can remove the failed drive while the RAID Module is on and receiving I/O.

$ #define LUN_HOTSPARE_STEPS 1975
1975 Repeat this procedure, if necessary, for each failed drive.\\p\\p 1. Remove the failed drive (its fault light should be on).\\p\\p 2. Make sure at least 30 seconds have elapsed; then, insert the new drive (its fault light may come on for a short time (one minute or less)).\\p\\p NOTE: The hot spare drive returns to a standby status after you have replaced the drive and the data has been automatically copied back to the replacement drive (the replacement drive will go from a Replaced status to an Optimal status). You can select Options >> Manual Recovery >> Drives from the top menu bar to monitor the drive status.\\p\\p 3. Repeat steps 1 and 2 if there is another failed drive reported; otherwise, go to step 4.\\p\\p 4. Make sure the drive has returned to the Optimal status and then re-run the Recovery Guru to ensure the failure has been fixed.

$ #define LUN_HOTSPARE_NOTES 1976
1976 no entry

$ #define LUN_HOTSPARE_ICON 1977
1977 HotspareLUN



$ ********************* Drives ************************

$ #define DRIVE_HEADER 1980
1980 Drive(s): %s 

$ #define DRIVE_ICON 1981
1981 drive


$ ***************** Unresponsive Drives

$ #define DRIVE_UNRESP_CAUSE 1984
1984 Unresponsive drives are inaccessible from the host. They can be caused by (1) environmental card failure (note that some models of RAID Modules do not contain environmental cards), (2) drives not inserted correctly, (3) a drive hardware failure, or (4) drives still spinning-up because of a power cycle on the drive tray.

$ #define DRIVE_UNRESP_WARNING 1985
1985 The RAID Controllers will fail Unresponsive drives if they receive any I/O. 

$ #define DRIVE_UNRESP_IMPORTANT 1986
1986 If a Failed Environmental Card is reported, select Show Procedure, and fix this before attempting to fix the Unresponsive Drive failure.

$ #define DRIVE_UNRESP_STEPS 1987
1987 1. Ensure the affected drives are inserted correctly and re-run the Recovery Guru.\\p\\p - If there are NO Unresponsive drives reported, this procedure is done.\\p\\p - If there are still Unresponsive drives reported, continue with step 2. \\p\\p 2. Manually fail the unresponsive drives using the following procedure:

$ #define DRIVE_UNRESP_NOTES 1988
1988 \\1 o \\0 Unresponsive, unassigned-drives (not contained in a LUN or a Hot Spare) are not visible to the RAID controllers or the storage management applications and will not appear in any drive lists.

$ #define DRIVE_UNRESP_ICON 1989
1989 UnrespDrive


$ ***************** Unresponsive Drives - In Lun

$ #define DRIVE_UNRESP_IN_LUN_TITLE 1991
1991 Unresponsive Drives - In LUN

$ #define DRIVE_UNRESP_IN_LUN_STEPS 1992
1992 \\p\\p\\4 CAUTION \\0\\p If the LUNs associated with the Unresponsive drives are either RAID 0 or are in a degraded state, you will lose ALL data on these LUNs. \\p\\pa. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Drives from the top menu bar. \\p\\pb. Highlight the Unresponsive drives and select Fail (if not grayed-out). \\p\\pc. If the Fail button is grayed-out (associated LUNs are Dead), use the drivutil command line utility to fail each Unresponsive drive as follows: drivutil -f <drive location> <RAID Module>.\\p\\p 3. Re-run the Recovery Guru to obtain the appropriate procedures for replacing these drives.


$ ********************** Offline LUNs

$ #define LUN_OFFLINE_TITLE 2001
2001 Dead LUN - Offline 

$ #define LUN_OFFLINE_CAUSE 2002
2002 An interrupted write recovery process has failed during a controller reset or a power failure causing the LUN(s) to be marked Dead. The drives associated with this error have been failed and/or placed offline. All data on the LUN(s) is lost. This procedure will reformat the affected LUNs. You will be required to restore from back up.

$ #define LUN_OFFLINE_WARNING 2003
2003 no entry

$ #define LUN_OFFLINE_IMPORTANT 2004
2004 no entry

$ #define LUN_OFFLINE_STEPS 2005
2005 1. In the Status Application, select Message Log, and highlight the most recent entries with a Hardware Error Code of 3FEB.\\p\\p 2. Select Show Details and record the LUNs associated with this error code.\\p\\p 3. Stop all I/Os (and any queued processes) to the LUNs you recorded in step 2.\\p\\p 4. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Drives from the top menu bar. \\p\\p 5. Highlight the drives associated with the affected LUNs (the drives will have a status of Failed or Offline) and select Revive. The drives will return to an Optimal status.\\p\\p 6. Select Options >> Manual Recovery >> Logical Units and highlight the LUNs you recorded in step 2 and select Format. \\p\\p 7. Re-run the Recovery Guru to ensure the failure has been fixed.\\p\\p 8. Restore the data from back up to the LUNs you formatted.

$ #define LUN_OFFLINE_NOTES 2006
2006 no entry

$ #define LUN_OFFLINE_ICON 2007
2007 DeadLUN


$ ************************** Failed or Unresponsive Hot Spare Drive

$ #define DRIVE_HOTSPARE_TITLE 2021
2021 Failed/Unresponsive Hot Spare Drive

$ #define DRIVE_HOTSPARE_CAUSE 2022
2022 A hot spare drive has either Failed or is Unresponsive (no response or missing). 

$ #define DRIVE_HOTSPARE_WARNING 2023
2023 A Failed or Unresponsive hot spare drive results in a lost level of data protection (no longer eligible to take over for another failed drive belonging to a LUN). Therefore, make sure that the hot spare drive is returned to Optimal-Standby as soon as possible.

$ #define DRIVE_HOTSPARE_IMPORTANT 2024
2024 \\1 o \\0 Unresponsive drives are inaccessible from the host. They can be caused by (1) Environmental Card failure (select Show Procedure and fix this before attempting to fix the Unresponsive Drive failure), (2) drives missing or not inserted correctly, or (3) a drive hardware failure. \\p\\p\\1 o \\0 A Failed hot spare drive may be the result of a drive hardware failure while it was In-Use. That is, while it was sparing another Failed drive belonging to LUN(s). In this case, the LUN(s) no longer contain this hot spare drive and may have transitioned to Degraded.

$ #define DRIVE_HOTSPARE_STEPS 2025
2025 1. Ensure the affected drives are inserted correctly into the drive slot and re-run the Recovery Guru. If Failed or Unresponsive hot spare drives remain, continue with step 2. \\p\\p 2. Remove this failed or unresponsive drive. (You can remove this drive while the RAID Module is on and receiving I/O) \\p\\p 3. Make sure at least 30 seconds have elapsed; then, insert the new drive (its fault light may come on for a short time (one minute or less)). Make sure the replacement drive has a capacity equal to or greater than the hot spare drive you removed. \\p\\p 4. Re-run the Recovery Guru to ensure the failure has been fixed.

$ #define DRIVE_HOTSPARE_NOTES 2026
2026 \\1 o \\0 To verify the hot spare drive has transitioned to Standby, see the Configuration Application's component tree view for Hot Spare drives or the Recovery Application's Options >> Manual Recovery >> Drives. \\p\\p\\1 o \\0 A Replaced hot spare drive will retain its hot spare status. That is, the replaced drive does not require being reselected as a hot spare drive via the Configuration Application. \\p\\p\\1 o \\0 A Failed hot spare drive may have been user-Failed using the Fail option in Recovery Application's Options >> Manual Recovery >> Drives. \\p\\p\\1 o \\0 Some models of RAID Modules do not contain Environmental Cards. 

$ #define DRIVE_HOTSPARE_ICON 2027
2027 FailHotspare



$ ************************** Unassigned (Spare) Drive
 
$ #define DRIVE_SPARE_TITLE 2031
2031 Failed Unassigned Drive
 
$ #define DRIVE_SPARE_CAUSE 2032
2032 An unassigned drive has failed probably because it was manually failed using the Fail option in Options >> Manual Recovery >> Drives from the top menu bar in the Recovery Application.

$ #define DRIVE_SPARE_WARNING 2033
2033 no entry

$ #define DRIVE_SPARE_IMPORTANT 2034
2034 \\1 o \\0 Because an unassigned drive is NOT part of a LUN, there is no data affected.\\p\\p \\1 o \\0 Make sure a replacement drive has a capacity equal to or greater than the failed drive you may remove in the following steps.\\p\\p \\1 o \\0 You can remove the failed drive while the RAID Module is on and receiving I/O.

$ #define DRIVE_SPARE_STEPS 2035
2035 1. In the Recovery Application, select the appropriate RAID Module, and then select Options>> Manual Recovery >> Drives.\\p\\p 2. Highlight the failed unassigned drive and select Revive.\\p\\p - If the drive continues to display a fault light and a status of Failed, go to step 3.\\p\\p - If the drive shows a status of Optimal, the drive has been fixed and the procedure is complete, go to Step 5.\\p\\p 3. Remove the failed drive (its fault light should be on).\\p\\p 4. Make sure at least 30 seconds have elapsed; then, insert the new drive.\\p\\p 5. Re-run the Recovery Guru to ensure the failure has been fixed.
 
$ #define DRIVE_SPARE_NOTES 2036
2036 no entry
 
$ #define DRIVE_SPARE_ICON 2037
2037 FailUnassigned



$ ************************** Unknown Failed Drive

$ #define DRIVE_UNKNOWN_TITLE 2041
2041 Cannot Get LUN Information

$ #define DRIVE_UNKNOWN_CAUSE 2042
2042 The information for the LUN(s) cannot be obtained at this time.

$ #define DRIVE_UNKNOWN_WARNING 2043
2043 no entry

$ #define DRIVE_UNKNOWN_IMPORTANT 2044
2044 no entry

$ #define DRIVE_UNKNOWN_STEPS 2045
2045 If the LUN(s) are currently locked, wait for the process locking the LUN (for example, a format operation or a firmware download) to complete and then re-run Recovery Guru.

$ #define DRIVE_UNKNOWN_NOTES 2046
2046 no entry

$ #define DRIVE_UNKNOWN_ICON 2047
2047 no entry


$ ********************** Drive Channel ***************************

$ #define CHANNEL_FAILURE_HEADER 2050
2050 Failed channel(s): %s

$ #define CHANNEL_FAILURE_TITLE 2051
2051 Failed Drive Channel

$ #define CHANNEL_FAILURE_CAUSE 2052
2052 A drive channel has failed. This could be caused by (1) loss of power to the drive tray (2) a disconnected or faulty drive cable, (3) a drive that is not inserted (seated) correctly, (4) a failed environmental card, (5) a failed component on the controller, (6) failed circuitry in the RAID Module, or (7) individual failures of all drives on the channel. Note that some models of RAID Modules do not contain environmental cards.

$ #define CHANNEL_FAILURE_WARNING 2053
2053 no entry

$ #define CHANNEL_FAILURE_IMPORTANT 2054 
2054 \\1 o \\0 In most cases, a channel failure prevents access to the data on the drives but does NOT cause data loss.\\p\\p \\1 o \\0 Some RAID Modules do not have external drive cables.\\p\\p \\1 o \\0 The Recovery Guru cannot determine the specific hardware component causing the channel failure. However, use the steps below to help pinpoint the problem and restore access to the drives.

$ #define CHANNEL_FAILURE_STEPS 2055
2055 1. Check to make sure there is power to the drive tray/RAID Module. Correct the problem if necessary and go to step 4; otherwise, go to step 2.\\p\\p 2. Check the drives to make sure they are inserted (seated) correctly. Also, if applicable, check the external drive cables to make sure that (1) there are no bent pins, (2) there is no visible damage, and (3) they are securely connected. \\p\\p - If the drives and cables are OK, there may be a problem with an environmental card. Go to step 3. \\p\\p - If there is a problem with the drives or cables, fix the problem and then go to step 4.\\p\\p 3. Is an environmental card failure being reported in the Summary Information screen of Recovery Guru?\\p\\p - No; go to step 4.\\p\\p - Yes; highlight the failure, select Show Procedure, and use this Recovery Guru procedure to fix the environmental card failure and the associated channel failure (do NOT use the rest of this procedure).\\p\\p 4. Re-run the Recovery Guru. \\p\\p - If a channel failure is still reported, consult your Customer Support Representative for other possible solutions. Once you have corrected the channel failure, go to step 5.\\p\\p - If a channel failure is NOT reported, go to step 5.\\p\\p 5. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Drives from the top menu bar and take the appropriate action below:\\p\\p - If the LUNs associated with the failed drives have a Dead Status, record these LUNs and stop all I/Os (and any queued processes) to these LUNs. Then, highlight the drive(s), and select Revive. \\p\\p - If the LUNs associated with the failed drive have an Optimal or Degraded Status, highlight the drive(s), and select Reconstruct. \\p\\p NOTE: Wait for the drives and LUNs to return to an Optimal status before going to step 6. If there were no LUNs with a Dead status (refer back to step 5), skip step 6 and go to step 7.\\p\\p 6. Select Manual Parity Check/Repair. Highlight any LUNs you recorded in step 5 that had a Dead status and select Parity Check/Repair. Make a note if there are any inconsistencies found.\\p\\p 7. Re-run the Recovery Guru to ensure that the failure has been fixed. If any parity inconsistencies were found and repaired by Manual Parity Check/Repair (see step 6), you must restore the data from back up because even though the parity inconsistencies were repaired, the data itself may be corrupted.

$ #define CHANNEL_FAILURE_NOTES 2058 
2058 no entry

$ #define CHANNEL_FAILURE_ICON 2059 
2059 FailChannel


$ ****************** Subsystem Components *******************


$ #define TRAY_HEADER 2060
2060 Affected Tray: %s 


$ ****************** Module Component (Fan or PS)

$ #define MODULE_COMPONENT_TITLE 2061
2061 Failed Module Component

$ #define MODULE_COMPONENT_CAUSE 2062
2062 A fan or power supply has failed in the RAID Module.

$ #define MODULE_COMPONENT_WARNING 2063
2063 A second fan or power supply failure could cause the RAID Module to shut down or fail. Replace the failed component as soon as possible.
 
$ #define MODULE_COMPONENT_IMPORTANT 2064
2064 no entry 

$ #define MODULE_COMPONENT_STEPS 2065
2065 1. Replace all fans and power supplies that have their fault lights on.\\p\\p NOTE: It could take up to 10 minutes before the fans or power supplies are reported as operational. Therefore, do NOT re-run the Recovery Guru during this time because the same failure may still be reported.\\p\\p 2. Wait at least 10 minutes and then re-run the Recovery Guru to ensure the failure has been fixed.

$ #define MODULE_COMPONENT_NOTES 2066
2066 no entry

$ #define MODULE_COMPONENT_ICON 2067
2067 FailModComp


$ ************** Trayed Fan (Single)

$ #define TRAYED_FAN_TITLE 2071
2071 Failed Fan 

$ #define TRAYED_FAN_CAUSE 2072
2072 A fan in a fan canister has failed in a tray.

$ #define TRAYED_FAN_WARNING 2073
2073 There is a time limit (in the 5 to 15 minute range) beyond which you should not operate the affected tray with a fan canister removed from the tray. This time limit depends on the model of the tray. To reduce the possibility of overheating, refer to the applicable hardware manual for the specific time limit.

$ #define TRAYED_FAN_IMPORTANT 2074
2074 \\1 o \\0 A second fan failure could cause the tray to shut down. Therefore, replace the fan canister as soon as possible.\\p\\p \\1 o \\0 Before performing any recovery procedures verify that the tray(s) are properly connected to an operational power source.

$ #define TRAYED_FAN_STEPS 2075
2075 1. Remove the failed fan canister in the tray (a fault light should be on).\\p\\p 2. Insert the new fan canister. Make sure the canister is inserted correctly and secured into place.\\p\\p NOTE: It could take up to 10 minutes before the fan is reported as operational. Therefore, do NOT re-run the Recovery Guru during this time because the same failure may still be reported.\\p\\p 3. Wait at least 10 minutes and then re-run the Recovery Guru to ensure the failure has been fixed.

$ #define TRAYED_FAN_NOTES 2076
2076 If needed, refer to the applicable hardware manual for detailed replacement procedures.

$ #define TRAYED_FAN_ICON 2077
2077 Failfan



$ *************** Trayed Power Supply (Single) 

$ #define TRAYED_PS_TITLE 2081
2081 Failed Power Supply

$ #define TRAYED_PS_CAUSE 2082
2082 A power supply has failed in a tray.

$ #define TRAYED_PS_WARNING 2083
2083 For some models, you must remove a fan canister to access the power supply. There is a time limit (in the 5 to 15 minute range) beyond which you should not operate the affected tray with a fan canister removed from the tray. This time limit depends on the model of the tray. To reduce the possibility of overheating, refer to the applicable hardware manual for the specific time limit. 

$ #define TRAYED_PS_IMPORTANT 2084
2084 \\1 o \\0 A second power supply failure could cause the tray to shut down. Therefore, replace the power supply as soon as possible.\\p\\p \\1 o \\0 Before performing any recovery procedures verify that the tray(s) are properly connected to an operational power source.

$ #define TRAYED_PS_STEPS 2085
2085 1. Remove the failed power supply in the tray (a fault light should be on).\\p\\p 2. Insert the new power supply.\\p\\p NOTE: It could take up to 10 minutes before the power supply is reported as operational. Therefore, do NOT re-run the Recovery Guru during this time because the same failure may still be reported.\\p\\p 3. Wait at least 10 minutes and then re-run the Recovery Guru to ensure the failure has been fixed.

$ #define TRAYED_PS_NOTES 2086
2086 If needed, refer to the applicable hardware manual for detailed replacement procedures.

$ #define TRAYED_PS_ICON 2087
2087 Failps



$ ******************* Thermal Sensor (indicates Drive Temp exceeded)

$ #define THERMAL_SENSOR_TITLE 2091
2091 Over-Temperature Condition

$ #define THERMAL_SENSOR_CAUSE 2092
2092 The maximum temperature allowed within a tray has been exceeded.

$ #define THERMAL_SENSOR_WARNING 2093
2093 An over-temperature condition is critical and may cause the tray to automatically turn off if you do not resolve the problem quickly.

$ #define THERMAL_SENSOR_IMPORTANT 2094
2094 no entry

$ #define THERMAL_SENSOR_STEPS 2095
2095 1. Locate the affected tray.\\p\\p 2. Are there any corresponding fan fault lights on?\\p\\p - Yes; a Fan Failure or Module Component Failure should be reported in the Summary Information screen of the Recovery Guru. Highlight the failure, select Show Procedure, and use the associated Recovery Guru procedure to fix the fan failures.\\p\\p - No; fix any potential room cooling problems.\\p\\p 3. Re-run the Recovery Guru to ensure the failure has been fixed.

$ #define THERMAL_SENSOR_NOTES 2096
2096 no entry

$ #define THERMAL_SENSOR_ICON 2097
2097 OverTemp


$ ************** Environment Card ***********************

$ #define ENVCARD_TITLE 2101
2101 Failed Environmental Card 

$ #define ENVCARD_CAUSE 2102
2102 An environmental card has failed in a drive tray.

$ #define ENVCARD_WARNING 2103
2103 In some cases, the drives in the drive tray associated with the failed card will be automatically spun down (failed) to avoid potential damage to the drives. If the drives are spun down, the Summary Information screen of the Recovery Guru may also report drive, LUN, and channel failures. However, do NOT use the associated procedures for the drive, LUN, or channel failures reported. Instead, fix the failed environmental card and any other associated failures using the following recovery steps.

$ #define ENVCARD_IMPORTANT 2104
2104 \\1 o \\0 There are several conditions which may cause loss of communication with the environmental card; therefore, use your hardware manual to help diagnose the problem. One possible cause is that you changed the option switches or ID of the environmental card without cycling power on the controller tray. If this is the case, you must turn the controller power switches off and then on again. Then, go to step 6.\\p\\p \\1 o \\0 Other names used to refer to the environmental card include SEN and ESM card. Check your hardware manual for the exact reference.

$ #define ENVCARD_STEPS 2105
2105 1. If there are failed drives or LUNs reported, select Module Profile >> Drives and record the location of each failed drive (for example, [4,8], [4,9], etc.). They should all be in the same drive tray associated with the failed environmental card. \\p\\p 2. Check to make sure there is power to the drive tray/RAID Module. \\p\\p - If there is power, go to step 3.\\p\\p - If there is no power, turn on the power and then go to step 6. \\p\\p 3. Check the external drive cables to make sure that (1) there are no bent pins, (2) there is no visible damage, and (3) they are securely connected. \\p\\p - If the drive cables are OK, go to step 4.\\p\\p - If there is a problem with the drive cables, correct the problem and then go to step 6. \\p\\p 4. Power off the drive tray associated with this environmental card and replace the card. Make sure it has the same option switch settings and ID as the failed card. Power on the drive tray. \\p\\p NOTE: You must perform step 5 if the controller firmware version is prior to 2.05.02 or a system reboot or power cycle occurred before you replaced the failed card. You can check the firmware version by selecting Module Profile >> Controllers. \\p\\p 5. Stop host I/O to this subsystem. Turn the controller power switches off and on again to cause the controllers to recognize the replacement card. \\p\\p 6. Re-run the Recovery Guru. If you performed step 5 and a failed card is still reported, review steps 2-4. \\p\\p If the controllers have successfully detected the replacement card, a failed environmental card or channel failure should NOT be reported. There should be no unresponsive drives in this drive tray. Reconstruction or global hot spare copyback processes should begin on drives in this drive tray associated with degraded LUNs. If this is not the case and you did not perform step 5, you should do so. \\p\\p Note: If you are satisfied that the controllers have successfully detected the replacement environmental card and degraded LUNs have not initiated reconstruction or copyback, you can highlight the failed drive(s) and select Reconstruct. \\p\\p 7. In the Recovery Application, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Drives. If the LUNs associated with the failed drives have a Dead status, record these LUNs and stop all I/Os (and any queued processes) to these LUNs. Then, highlight the drives and select Revive. \\p\\p NOTE: Wait for the drives and LUNs to return to an Optimal status before going to step 8. If there were no LUNs with a Dead status (refer back to step 7), skip step 8 and go to step 9.\\p\\p 8. Select Manual Parity Check/Repair. Highlight any LUNs you recorded in step 7 that had a Dead status and select Parity Check/Repair. Make a note if there are any inconsistencies found.\\p\\p 9. Re-run the Recovery Guru to ensure that the failure has been fixed. If any parity inconsistencies were found and repaired by Manual Parity Check/Repair (see step 8), you must restore the data from back up because even though the parity inconsistencies were repaired, the data itself may be corrupted.

$ #define ENVCARD_NOTES 2107
2107 \\1 o \\0 An environmental card can be associated with two channels, depending on whether the drive tray is configured as a split-bus. \\p\\p \\1 o \\0 If the system can be taken offline during this environmental card replacement procedure, consider performing step 5 regardless of the controller firmware level to ensure the controllers detect the new environmental card.

$ #define ENVCARD_ICON 2108
2108 FailEnvcard


$ ************** UPS Error ***********************

$ #define UPS_TITLE 2111
2111 UPS - Alert
 
$ #define UPS_CAUSE 2112
2112 An uninterruptible power supply (UPS) has indicated that the depletion of its standby power source is imminent!
 
$ #define UPS_WARNING 2113
2113 no entry 

$ #define UPS_IMPORTANT 2114
2114 no entry 

$ #define UPS_STEPS 2115
2115 1. Stop all writes to the RAID Module now.\\p\\p 2. Repair the AC power problem.
 
$ #define UPS_NOTES 2116
2116 no entry
 
$ #define UPS_ICON 2117
2117 UPSAlert


$ ************** UPS Standby Warning  ***********************

$ #define UPS_STANDBY_TITLE 2121
2121 UPS - Standby Power
 
$ #define UPS_STANDBY_CAUSE 2122
2122 AC power has been lost. The uninterruptible power supply (UPS) is operating on standby power.
 
$ #define UPS_STANDBY_WARNING 2123
2123 no entry 

$ #define UPS_STANDBY_IMPORTANT 2124
2124 no entry 

$ #define UPS_STANDBY_STEPS 2125
2125 1. Because the UPS has switched to standby power, you should save your data frequently in case the standby power is suddenly depleted.\\p\\p 2. Repair the AC power problem.

$ #define UPS_STANDBY_NOTES 2126
2126 no entry
 
$ #define UPS_STANDBY_ICON 2127
2127 UPSStandby
 
$ ************** Cache Battery ***********************

$ #define CACHE_BATTERY_WARNING 2131
2131 \\1 o \\0 Do not perform these recovery steps if you have just turned on the RAID Module or replaced a controller. During these two situations, the battery's self-test diagnostics takes approximately 12 to 15 minutes to complete (dependent on the controller type and whether the batteries were discharged). Until the diagnostic test is completed, you may see Battery Alert or Failure indications in the Recovery Guru for batteries that are operational and fully charged. \\p\\p\\1 o \\0 On some models, the battery canister can weigh up to 24 pounds (10.86 kilograms). Use both hands to remove and replace the canister.

$ #define CACHE_BATTERY_IMPORTANT 2132
2132 \\1 o \\0 The battery and its replacement procedure vary depending on the type of RAID Module you have. The following steps provide common procedures you will need to perform for a battery replacement. Consult the appropriate hardware manual if you need details on locating and accessing the battery.\\p\\p\\1 o \\0 Each controller in a dual controller module has its own view of the battery's expiration date and current time of day. Under normal circumstances these views should be consistent and you should observe two battery entries in the Recovery Guru Summary Information Screen, one for each controller.

$ #define CACHE_BATTERY_STEPS 2133
2133 1. Stop all I/O activity to the controller and turn off the power to the RAID Module.\\p\\p 2. Remove the battery canister and replace it with a new one.\\p\\p 3. Record today's date (installation) and the new replacement date on the label. The replacement date is 2 years from the installation date.\\p\\p 4. Turn on the power to the RAID Module. Use the raidutil command line utility as follows to reset the battery age for EACH controller (device) in the RAID Module: raidutil -c <device name> -R\\p\\p If you need information on the device name, select Module Profile and look at the Summary Information screen.\\p\\p 5. Wait 15 minutes and re-run the Recovery Guru to ensure that the failure has been fixed. If a battery alert or failure is reported again, you probably did not reset the battery age on EACH controller.

$ #define CACHE_BATTERY_NOTES 2134
2134 Some older RAID Modules may have separate batteries mounted on each controller. In this case, a battery failure entry refers to the battery associated with the controller reporting the failure.



$ ************** Cache Battery Failure ***********************
 
$ #define CACHE_BATTERY_FAILURE_TITLE 2135
2135 Failed Battery
 
$ #define CACHE_BATTERY_FAILURE_CAUSE 2136
2136 The batteries in the battery canister have failed or reached their expiration date.
 
$ #define CACHE_BATTERY_FAILURE_ICON 2137
2137 FailBattery


$ ************** Cache Battery Warning ***********************

$ #define CACHE_BATTERY_WARNING_TITLE 2141
2141 Battery Alert
 
$ #define CACHE_BATTERY_WARNING_CAUSE 2142
2142 The batteries in the battery canister are nearing their expiration date or have been removed. You should replace the canister as soon as possible. 

$ #define CACHE_BATTERY_WARNING_ICON 2143
2143 BatteryAlert


$ #define CREATE_HS_FAILED_CATCHALL		2148
2148 Unable to create hot spare drive %s, because either:\n1) A LUN or group is being modified, or\n2) A failure has occurred along the connection.\n \n - If a LUN or group is being modified, wait until the operation has\ncompleted.\n - If a failure has occurred, run the Recovery Guru and fix the problem.

$ #define EVENT_8A10_CAUSE		2149
2149 Could not perform the modification because either (1) some or all of the LUNs in the group have non-standard segment sizes or (2) the RAID controller doesn't have sufficient resources to perform it.

$ #define EVENT_8A10_ACTION	2150
2150 For Cause #1: Check the segment sizes of the LUNs by using Module Profile>>LUNs. The standard segment sizes (in blocks) are: 16, 32, 64, 128, 256, and 512.  If some of the LUNs in the group have non-standard segment sizes, the only way to complete the modification operation is to back up the data, delete these LUNs, and recreate them with the desired RAID level, number of drives, and segment size. For Cause #2: If the LUNs in the group have standard segment sizes, use Options>>Modify Group/LUN>>Segment Size in Configuration and attempt to select a smaller size and retry the modification operation. If the modification operation fails again, the only way to complete the modification operation is to back up the data, delete these LUNs, and recreate them with the desired RAID level, number of drives, and segment size.

$ #define MT_OPTIONS_MENU                2151
2151 Perform various maintenance and tuning options.

$ *********************Trayed Fan (Multiple)

$ #define TRAYED_FANS_TITLE 2161
2161 Failed Fans
 
$ #define TRAYED_FANS_CAUSE 2162
2162 Multiple fan canisters have failed in a tray.
 
$ #define TRAYED_FANS_WARNING 2163
2163 This is a critical condition that may cause the tray to reach an unsafe operating temperature. Replace the fan canisters as soon as possible.
 
$ #define TRAYED_FANS_IMPORTANT 2164
2164 Before performing any recovery procedures verify that the tray(s) are properly connected to an operational power source.
 
$ #define TRAYED_FANS_STEPS 2165
2165 1. Remove the failed fan canister(s) in the tray (a fault light should be on).\\p\\p 2. Insert the new fan canister(s). Make sure the canister is inserted correctly and secured into place.\\p\\p NOTE: It could take up to 10 minutes before the fans are reported as operational. Therefore, do NOT re-run the Recovery Guru during this time because the same failure may still be reported.\\p\\p 3. Wait at least 10 minutes and then re-run the Recovery Guru to ensure the failure has been fixed.
 
$ #define TRAYED_FANS_NOTES 2166
2166 If needed, refer to the applicable hardware manual for detailed replacement procedures.
 
$ #define TRAYED_FANS_ICON 2167
2167 Failfan

$ *********************Trayed Power Supply (Multiple)

$ #define TRAYED_PSM_TITLE 2171
2171 Failed Power Supplies
 
$ #define TRAYED_PSM_CAUSE 2172
2172 Multiple power supplies have failed in a tray.
 
$ #define TRAYED_PSM_WARNING 2173
2173 For some models of trays, you must remove a fan canister to access the power supply. There is a time limit (in the 5 to 15 minute range) beyond which you should not operate the affected tray with a fan canister removed from the tray. This time limit depends on the model of the tray. To reduce the possibility of overheating, refer to the applicable hardware manual for the specific time limit.
 
$ #define TRAYED_PSM_IMPORTANT 2174
2174 Before performing any recovery procedures verify that the tray(s) are properly connected to an operational power source.
 
$ #define TRAYED_PSM_STEPS 2175
2175 1. Remove the failed power supplies in the tray (a fault light should be on).\\p\\p 2. Insert the new power supplies.\\p\\p NOTE: It could take up to 10 minutes before the power supplies are reported as operational. Therefore, do NOT re-run the Recovery Guru during this time because the same failure may still be reported.\\p\\p 3. Wait at least 10 minutes and then re-run the Recovery Guru to ensure the failure has been fixed.
 
$ #define TRAYED_PSM_NOTES 2176
2176 If needed, refer to the applicable hardware manual for detailed replacement procedures.
 
$ #define TRAYED_PSM_ICON 2177
2177 Failps

$ #define ST_DET_MSG_AFF_COMP 2178
2178 Affected Component:  %s\n

$ #define ST_DET_MSG_AFF_TRAY 2179
2179 Affected Tray:  %s\n

$ #define ST_AFF_TRAY 2180
2180 Affected Tray:

$ #define ST_POWERSUPPLY 2181
2181 Power Supply

$ #define ST_FAN 2182
2182 Fan

$ #define ST_ENVIRONMENTAL_CARD 2183
2183 Environmental Card

$ #define ST_CONTROLLER 2184
2184 Controller

$ #define ST_NONVOLATILE_CACHE 2185
2185 Non-volatile Cache

$ #define ST_UNINTERRUPTIBLE_POWER_SUPPLY 2186
2186 Uninterruptible Power Supply (UPS)

$ #define ST_CONTROLLER_MODULE        2187
2187 Controller Module

$ #define EVENT_AEN_9801_CAUSE              2188
2188 There are multiple drive trays with the same tray ID selected.
 
$ #define EVENT_AEN_9801_ACTION     2189
2189 Make sure that each drive tray has a unique ID setting.

$ #define EVENT_AEN_0C81_CAUSE		2190
2190 A recovery attempt from a data cache error was unsuccessful. User data may have been lost.

$ #define EVENT_AEN_OC81_ACTION		2191
2191 You should restore the LUN's data from back up.

$ #define EVENT_AEN_A600_CAUSE		2192
2192 The controller has detected and corrected a recoverable error in processor memory.

$ #define EVENT_AEN_A700_CAUSE		2193
2193 The controller has detected and corrected a recoverable error in the data buffer memory.

$ #define SNMP_68	2194
2194 Drive trays with duplicate ID settings.

$ #define STORUTIL_USAGE_1 2195
2195 \n     storutil  -c <raid module specifier>

$ #define STORUTIL_USAGE_2 2196
2196 \n               [ -w clear host store ]

$ #define STORUTIL_USAGE_3 2197
2197 \n               [ -n <new module name> change module name ]

$ #define STORUTIL_USAGE_4 2198
2198 \n               [ -i <on | off> independent controller setting ]

$ #define STORUTIL_USAGE_5 2199
2199 \n               [ -d display information from host store ]

$ #define STORUTIL_USAGE_6 2200
2200 \n               [ -? display usage information ]

$ #define STORUTIL_USAGE_END 2201
2201 \n

$ #define DCE_SMALLER_DRIVE_CAPACITY 2202
2202 One or more drives you have selected has a capacity that is\nsmaller than any of the drives currently in the drive group.\nIf you perform this operation using this drive, you will not\nbe able to use some of the capacity on the drives in\nthe current drive group.\n \nNOTE: If you need to determine the capacity of the drives\nin the current drive group, select Cancel twice to return\nto the main configuration window. Highlight the desired\ndrive group, and then select List/Locate Drives.\n \nSelect OK to proceed with this operation.

$ #define DCE_NO_DRIVE_SELECTION 2203
2203 You must select an available drive\nto complete this operation.

$ #define NO_AUTO_LUN_BALANCE	2204
2204 The controllers were successfully changed to active/active mode.\nHowever, the LUNs were not automatically balanced across\nthe controllers.\n \nAttempt to use the LUN Balancing option in the Maintenance/Tuning\nApplication to balance the LUNs.

$ ******************* Independent Controller Offline (held in reset)
 
$ #define INDCTL_OFFLINE_TITLE 2210
2210 Offline Controller
 
$ #define INDCTL_OFFLINE_CAUSE 2211
2211 A RAID Controller connected to the other host, in an independent controller configuration, has been manually placed in the Offline status.
 
$ #define INDCTL_OFFLINE_WARNING 2212
2212 You can diagnose and correct the problem while the RAID Module is on and receiving I/O.
 
$ #define INDCTL_OFFLINE_IMPORTANT 2213
2213 \\1 o \\0 The host that has the Offline controller will be referred to as host #1 in this procedure. The host on which you are currently running this Recovery Guru procedure will be referred to as host #2.\\p\\p \\1 o \\0 You will be required to perform steps from both hosts. Therefore, if desired, print this procedure for your reference or select Help >> Recovery Guru Procedures from host #1 and select the "Offline Controller - Independent Controller" topic.
 
$ #define INDCTL_OFFLINE_STEPS 2214
2214 1. Take the following action:\\p\\p - If you manually placed the controller Offline because you were following the Unresponsive Controller procedure provided by the Recovery Guru from host #1, continue to follow the Unresponsive Controller procedure to replace the controller. Do NOT use this procedure.\\p\\p - If you manually placed the controller Offline for any other reason and you want to attempt to place it back Online, go to step 2; otherwise, go to step 4 to replace the controller.\\p\\p 2. In the Recovery Application from this host (host #2), make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar.\\p\\p 3. Highlight the controller with the Offline (inaccessible) status and select Place Online. The transition to Online may take several minutes. \\p\\p - If the controller returns to the Online status, go to step 8.\\p\\p - If the controller does NOT return to the Online status, go to step 4 to replace the controller.\\p\\p 4. Remove the failed controller (its fault LEDs should be on). Make sure at least 1 minute has elapsed before inserting the new controller.\\p\\p 5. Insert the new controller firmly into the RAID Module.\\p\\p 6. In the Recovery Application from this host (host #2), make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar. \\p\\p 7. Highlight the controller with an Offline (inaccessible) status and select Place Online. The transition to Online may take several minutes.\\p\\p - If the controller returns to the Online status, go to step 8.\\p\\p - If the controller does NOT return to the Online status, then either you have not inserted (seated) the controller correctly, there may be a defective adapter card in your host, or there is a connection problem. Check these possible problems and then repeat steps 6 and 7.\\p\\p 8. Start the Maintenance/Tuning Application from host #1, select the appropriate RAID Module, and choose Controller Mode. Change the controller mode to active/active. Then, select LUN Balancing and redistribute the LUNs properly across each controller.\\p\\p 9. Re-run the Recovery Guru from host #1 to ensure that the failure has been fixed.\\p\\p If any other type of problem is reported (such as a mismatch of controller firmware versions), fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.

$ #define INDCTL_OFFLINE_NOTES 2217
2217 If you replaced the controller and the filesystems/logical units do not respond, you may need to reboot your system.
 
$ #define INDCTL_OFFLINE_ICON 2218
2218 OffCtrl

$ ******************* Independent Controller Unresponsive
 
$ #define INDCTL_UNRESP_TITLE 2220
2220 Unresponsive Controller
 
$ #define INDCTL_UNRESP_CAUSE 2221
2221 A RAID Controller connected to this host, in an independent controller configuration, is Unresponsive. An Unresponsive controller can be caused by the following:\\p\\p \\1 o \\0 Disconnected or improperly seated controller\\p\\p \\1 o \\0 Disconnected or faulty cables\\p\\p \\1 o \\0 Disconnected or faulty terminators (SCSI connection only)\\p\\p \\1 o \\0 Hub or fabric switch malfunction (Fibre connection only)\\p\\p \\1 o \\0 Adapter failure\\p\\p \\1 o \\0 Defective RAID Controller
 
$ #define INDCTL_UNRESP_WARNING 2222
2222 no entry
 
$ #define INDCTL_UNRESP_IMPORTANT 2223
2223 \\1 o \\0 The host on which you are currently running this Recovery Guru procedure will be referred to as host #1 in this procedure. The other host connected to the RAID Module will be referred to as host #2.\\p\\p \\1 o \\0 You may be required to perform steps from both hosts. Therefore, if desired, print this procedure for your reference or select Help >> Recovery Guru Procedures from host #2 and select the "Unresponsive Controller - Independent Controller" topic.\\p\\p  \\1 o \\0 Another potential cause could be that this controller was placed offline from host #2 and never placed back online. If you suspect this could be the problem, go to host #2 and run the Recovery Guru. If an Offline Controller failure type is reported, select Show Procedure and follow those steps.\\p\\p \\1 o \\0 Another potential cause could be incorrect NVSRAM settings on the controller. If you follow the steps below and are still having problems, contact a Customer Support Representative.

$ #define INDCTL_UNRESP_STEPS 2224
2224 1. Make sure you ran the Recovery Guru with the "All RAID Modules" selection. Then, look at the Summary Information screen of the Recovery Guru and answer the following question:\\p\\p "Are ALL other RAID Modules on the same connection (adapter and cable) reporting Unresponsive Controllers?"\\p\\p - Yes; you probably have a defective adapter. Go to step 2. If you want to explore other possible causes before fixing the adapter, go to step 3.\\p\\p - No; go to step 3.\\p\\p \\1 Fixing Adapter Problem \\0 \\p 2. Fix the adapter problem and then re-run the Recovery Guru from this host (host #1).\\p\\p - If an Unresponsive Controller is reported again, then the problem is at the connection or RAID Controller. Go to step 3 to check the connection.\\p\\p - If an Unresponsive Controller is NOT reported again, then the problem has been fixed. You are done with this procedure. \\p\\p \\1 Checking/Fixing The Connection \\0 \\p 3. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables\\p\\p \\1 o \\0 Terminators (SCSI connection only)\\p\\p \\1 o \\0 Hubs and switches (Fibre connection only)\\p\\p - If there is a problem with the connection, go to step 4.\\p\\p - If these components are OK, the controller connected to host #1 is probably defective. Go to step 5.\\p\\p 4. Fix the connection problem (for example, reconnect or replace cable, etc.) and then re-run the Recovery Guru from this host (host #1).\\p\\p - If an Unresponsive Controller is reported again, then the problem is with the RAID Controller. Go to step 5.\\p\\p - If an Unresponsive Controller is NOT reported again, then the problem has been fixed. You are done with this procedure. \\p\\p \\1 Replacing The RAID Controller \\0 \\p\\p NOTE: You MUST close all storage management applications (except Recovery) BEFORE replacing the RAID controller. \\p\\p  5. In the Recovery Application from host #2, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar.\\p\\p 6. Highlight the controller with an Unresponsive or Dead (inaccessible) status and select Place Offline. The transition to Offline may take several minutes.\\p\\p 7. Remove the failed controller (its fault LEDs should be on). Make sure at least 1 minute has elapsed before inserting the new controller.\\p\\p 8. Insert the new controller firmly into the RAID Module.\\p\\p 9. In the Recovery Application from host #2, make sure the affected RAID Module is selected. Then, select Options >> Manual Recovery >> Controller Pairs from the top menu bar.\\p\\p 10. Highlight the controller with an Offline (inaccessible) status and select Place Online. The transition to Online may take several minutes.\\p\\p - If the controller does NOT return to the Online status, then you have probably not inserted (seated) the controller correctly. Insert the controller again and repeat steps 9 and 10. \\p\\p - If the controller returns to the Online status, go to step 11.\\p\\p 11. Re-run the Recovery Guru from host #1 to ensure the failure has been fixed.\\p\\p - If an Unresponsive controller is still reported, repeat steps 2 through 4. Consult a Customer Support Representative, if necessary .\\p\\p - If any other type of problem is reported (such as a mismatch of controller firmware versions), fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.
 
$ #define INDCTL_UNRESP_NOTES 2228
2228 \\1 o \\0 If you replaced the controller and the filesystems/logical units do not respond, you may need to reboot your system. \\p\\p\\1 o \\0 Run the command line utility "lad" to verify all controllers are visible to the storage management software.
 
$ #define INDCTL_UNRESP_ICON 2229
2229 UnrespCtrl

$ #define SINGLE_CTRL_CACHE	2230
2230 If you want to enable write caching in a single controller RAID\nModule, you must enable the write caching option AND\ndisable the write cache mirroring option if it is currently\nenabled. The controller will NOT perform write caching if\nthe write cache mirroring option is enabled and an alternate\n(redundant) controller is not present.


$ ************** Drive Failure - Reconstructing or Formatting  ***********************

$ #define DRIVE_FAIL_RECON_TITLE 2231
2231 Failed Drive - Reconstructing or Formatting LUN
 
$ #define DRIVE_FAIL_RECON_CAUSE 2232
2232 The LUN(s) associated with the failed drive are either reconstructing or formatting.
 
$ #define DRIVE_FAIL_RECON_WARNING 2233
2233 no entry 

$ #define DRIVE_FAIL_RECON_IMPORTANT 2234
2234 no entry 

$ #define DRIVE_FAIL_RECON_STEPS 2235
2235 Wait until the reconstructing or formatting process completes and then re-run the Recovery Guru. Note that a "Degraded LUN" or "LUN - Hotspare In Use" failure will probably be reported (because of the failed drive).

$ #define DRIVE_FAIL_RECON_NOTES 2236
2236 no entry
 
$ #define DRIVE_FAIL_RECON_ICON 2237
2237 no entry
 
$ #define DRM_UNABLE_TO_MIGRATE	2238
2238 You cannot modify this group's RAID level. The\nnumber of drives in the selected drive group\nis only valid with the current RAID level.

$ #define MON95_HELP_TITLE 2239
2239 Disk Array Monitor Help

$ #define MON95_HELP_TEXT 2240
2240 The Disk Array Monitor assists the Storage Management\nsoftware by:\n\n    -- Detecting configuration changes\n    -- Notifying it of problems\n    -- Initiating the automatic parity check\n\nYou should leave it running unless instructed otherwise.\n\n\nTo toggle the Disk Array Monitor on/off, double-click\non its taskbar icon using the left mouse button.

$ #define MON95_RUNNING_ICON_TEXT 2241
2241 The Disk Array Monitor is running

$ #define MON95_STOPPED_ICON_TEXT 2242
2242 The Disk Array Monitor is stopped

$ #define PROFILE_HOST_INTERFACE 2243
2243 Host Interface:

$ #define PROFILE_PARALLEL_SCSI 2244
2244 Parallel SCSI

$ #define PROFILE_FCP 2245
2245 Fibre Channel - FCP

$ #define PROFILE_TOPOLOGY 2246
2246 Topology:

$ #define PROFILE_POINT_TO_POINT 2247
2247 Point-to-Point

$ #define PROFILE_FABRIC 2248
2248 Fabric

$ #define PROFILE_PRIVATE_LOOP 2249
2249 Arbitrated Loop - Private

$ #define PROFILE_PUBLIC_LOOP 2250
2250 Arbitrated Loop - Public

$ #define PROFILE_UNKNOWN 2251
2251 Unknown

$ #define PROFILE_CONTROLLER_ID 2252
2252 Controller ID - NL_Port (hex):

$ #define PROFILE_PREFERRED_ALPA 2253
2253 Preferred Address - AL_PA (hex):

$ #define PROFILE_PREFERRED_LOOPID 2254
2254 Preferred Loop ID (dec):

$ #define PROFILE_HOST_ID_SWITCH 2255
2255 Host-side ID (dec):

$ #define PROFILE_FC_PORT_NAME 2256
2256 Worldwide Port Name (hex):

$ #define PROFILE_PHYSICAL_CONNECT 2257
2257 Physical Connection:

$ #define PROFILE_COPPER 2258
2258 Copper

$ #define PROFILE_OPTICAL 2259
2259 Optical

$ #define PROFILE_LINK_SPEED 2260
2260 Link Speed (MB/sec):

$ #define DCE_MAX_DRIVES_SELECTED 2261
2261 You have reached the maximum number of\ndrives allowed for this drive group.

$ #define MT_GENERIC_FILE 2262
2262 %s\n(File: %s)

$ #define MT_FIRMWARE_FILE 2263
2263 %s\n(Firmware File: %s)

$ #define MT_BOOTWARE_FILE 2264
2264 %s\n(Bootware File: %s)

$ #define MT_FIBRE_FILE 2265
2265 %s\n(Fibre Channel File: %s)

$ #define MT_CTLA_FIRMWARE_FILE 2266
2266 %s: Controller A\n(Firmware File: %s)

$ #define MT_CTLB_FIRMWARE_FILE 2267
2267 %s: Controller B\n(Firmware File: %s)

$ #define MT_CTLA_BOOTWARE_FILE 2268
2268 %s: Controller A\n(Bootware File: %s)

$ #define MT_CTLB_BOOTWARE_FILE 2269
2269 %s: Controller B\n(Bootware File: %s)

$ #define MT_CTLA_FIBRE_FILE 2270
2270 %s: Controller A\n(Fibre Channel File: %s)

$ #define MT_CTLB_FIBRE_FILE 2271
2271 %s: Controller B\n(Fibre Channel File: %s)

$ #define MT_CTLA_GENERIC_FILE 2272
2272 %s: Controller A\n(File: %s)

$ #define MT_CTLB_GENERIC_FILE 2273
2273 %s: Controller B\n(File: %s)

$ #define HOTSPARE_PARTIAL_COVERAGE  2274
2274 \nThe selected drive at location %s has a smaller capacity\n(%ld) than some of the drives in the RAID Module. It will not\nbe able to take over if one of those drives fails.\n(Note that drive capacity differences can be caused by\ndrive firmware version discrepancies. Refer to Module Profile).\n \nDo you still want to create a hot spare using this drive?

$ ********* Independent Controllers Flag Mismatch Error ******************

$ #define INDCTL_FLAG_MISMATCH_TITLE 2275
2275 Independent Controllers Not Detected

$ #define INDCTL_FLAG_MISMATCH_CAUSE 2276
2276 The independent controller check box has been set for this RAID Module. However, this host is able to access both controllers. Therefore, this RAID Module has not been connected correctly for an independent controller configuration or the check box has been inadvertently selected.

$ #define INDCTL_FLAG_MISMATCH_WARNING 2277
2277 no entry

$ #define INDCTL_FLAG_MISMATCH_IMPORTANT 2278
2278 An independent controller configuration is where two host machines are connected to a dual-controller RAID Module. One host machine is connected by one cable to one controller and the second host machine is connected by another cable to the other controller. Each host acts as if it is connected to a single-controller RAID Module.

$ #define INDCTL_FLAG_MISMATCH_STEPS 2279
2279 1. Do you want this RAID Module to be set up in an independent controller configuration?\\p\\p Yes - Check the cable connections and make sure that you are cabled correctly with each host connected to only one controller in the RAID Module. Then, go to step 5.\\p\\p No - perform steps 2 - 5.\\p\\p 2. In the Recovery Application, choose Select Module. The RAID Module selection window is displayed.\\p\\p 3. Highlight the affected module and select Edit. The edit window is displayed.\\p\\p 4. Select the check box next to the "Independent Controllers?" label to turn off this feature and select OK. The independent Controller column (Indep. Cntrls?) column in the RAID Module selection window should say No for the affected RAID Module.\\p\\p 5. Re-run the Recovery Guru to ensure the failure has been fixed.

$ #define INDCTL_FLAG_MISMATCH_NOTES 2280
2280 no entry

$ #define INDCTL_FLAG_MISMATCH_ICON 2281
2281 IndepCtrlNOT


$ ******************************** Other Host Failure Type

$ #define OTHER_HOST_TITLE 2291
2291 Failure On Other Host - Independent Controller

$ #define OTHER_HOST_CAUSE 2292
2292 A failure was detected that should be fixed from the other host.

$ #define OTHER_HOST_WARNING 2293
2293 no entry

$ #define OTHER_HOST_IMPORTANT 2294
2294 no entry

$ #define OTHER_HOST_STEPS 2295
2295 Re-run the Recovery Guru from the other host to detect and fix the problem.

$ #define OTHER_HOST_NOTES 2296
2296 no entry

$ #define OTHER_HOST_ICON 2297
2297 no entry

$ #define ST_UNABLE_TO_LOG_SELECT 2298
2298 There was an error initializing the performance statistics.\nSelect OK to exit the performance monitor.

$ #define RECONFIG_FAILURE_DACSTOR 2299
2299 The modification operation could not be performed because there is\ninsufficient capacity reserved on each drive for internal configuration\npurposes. If you want to complete this modification, the only solution\nis to back up the data on the drive group's LUNs, delete the LUNs, and\nrecreate them with the desired RAID level, number of drives, and segment\nsize.\n \nNOTE: There may be a decrease in drive group capacity when recreating\nthe LUNs (about 38 MB per drive), since this drive group was originally\ncreated with pre-2.05 controller firmware and release 3.X controller\nfirmware requires more reserved capacity per drive for internal\nconfiguration purposes.

$ #define RECONFIG_FAILURE_VDDRESOURCE 2300
2300 Could not perform the modification because either\n(1) some or all of the LUNs in the group have non-standard segment\nsizes, or\n(2) the RAID controller doesn't have sufficient resources to perform it.\n \nFor Cause #1:\nCheck the segment sizes of the LUNs by using Module Profile>>LUNs.\nThe standard segment sizes (in blocks) are: 16, 32, 64, 128, 256,\nand 512.  If some of the LUNs in the group have non-standard segment\nsizes, the only way to complete the modification operation is to back\nup the data, delete these LUNs, and recreate them with the desired\nRAID level, number of drives, and segment size.\n \nFor Cause #2:\nIf the LUNs in the group have standard segment sizes, use Options>>\nModify Group/LUN>>Segment Size in Configuration and attempt to select\na smaller size and retry the modification operation. If the\nmodification operation fails again, the only way to complete the\nmodification operation is to back up the data, delete these LUNs,\nand recreate them with the desired RAID level, number of drives,\nand segment size.

$ #define REC_REVIVECOMP_NO_PARITY 2301
2301 The drive has been restored and returned to its original\nstatus (unassigned or hot spare).

$ #define LOG_FULL_EXISTS 2302
2302 The message log %s has exceeded\nthe maximum size specified.  It will be saved to a separate\nfile and a new log file will be created.\n \nA previously saved log file %s\ncurrently exists.  Do you wish to overwrite this file with the\ncurrent log file being saved?\n \nSelecting No will cause the log to be saved to a new file\n%s and leave the existing file\nintact.

$ #define LOG_FULL_NONEXIST 2303
2303 The message log %s\nhas exceeded the maximum size specified.\nIt will be saved to a separate file and a new\nlog file will be created.\n \nThe log contents will be saved to the file\n%s.

$ #define REC_HELP_GURU_PROC 2304
2304 General reference procedures for recovering from failures.

$ ******************************** Module Scan Error Failure Type

$ #define MODULE_SCAN_TITLE 2311
2311 Unable To Scan Module

$ #define MODULE_SCAN_CAUSE 2312
2312 A failure occurred while attempting to obtain information about the RAID Module.

$ #define MODULE_SCAN_WARNING 2313
2313 The Recovery Guru cannot detect any problems and your storage management applications will not function properly while this condition persists.

$ #define MODULE_SCAN_IMPORTANT 2314
2314 no entry

$ #define MODULE_SCAN_STEPS 2315
2315 1. If a firmware download operation is in progress or the controller(s) in the RAID Modules are initializing after a reset (for example, the RAID Module was turned off and then on again), wait for these operations to complete and then re-run the Recovery Guru. If the problem persists, go to step 2.\\p \\p 2. Try the following actions:\\p \\p - Run the command line utility "lad" to verify the controller(s) are visible to the storage management software. \\p \\p -  Run the appropriate 'clean' utility or reboot the operating system to fix any temporary problem with the storage management software.\\p \\p - Check the 'System_MaxLunsPerController' parameter in the rmparams file to make sure that there are not too many LUNs existing on the controller(s) in this RAID Module (that is, more than your operating system can handle).\\p \\p - Check and fix any unterminated cables (SCSI connection only).\\p \\p - Check for any problems with the adapter or drivers in your host system.
 
$ #define MODULE_SCAN_NOTES 2316
2316 no entry

$ #define MODULE_SCAN_ICON 2317
2317 NoScanModule

$ #define LOG_SAVE_MESSAGES 2318
2318 The message log has exceeded its maximum size specified in Options >> Log Settings of the Status Application.  It has been saved to %s.  You should open this file once to make sure there are not any recent entries that you did not view in the message log.  After viewing this file, you should then use the current message log (%s) to view any new entries.

$ #define ASSIGN_LUN_PASSIVE_CONT 2319
2319 Cannot assign LUNs to a passive controller.\n

$ ******************************** Lun Reconfiguring

$ #define LUN_RECONFIG_TITLE 2321
2321 Reconfiguring LUN

$ #define LUN_RECONFIG_CAUSE 2322
2322 The LUN(s) in this drive group are reconfiguring due to an ongoing modification operation (for example, changing RAID level or a capacity expansion).

$ #define LUN_RECONFIG_WARNING 2323
2323 If the LUN modification process does not complete in a reasonable time, rerun the Recovery Guru. Check for Dead LUNs contained in this drive group.

$ #define LUN_RECONFIG_IMPORTANT 2324
2324 No corrective action is required. Wait for this operation to complete before using the LUN(s).

$ #define LUN_RECONFIG_STEPS 2325
2325 See the Configuration Application to display the percent complete for the ongoing modification operation for this drive group. 

$ #define LUN_RECONFIG_NOTES 2326
2326 The LUN(s) are not locked during this operation.

$ #define LUN_RECONFIG_ICON 2327
2327 no entry

$ #define PROF_MSG_4SERIES 2328
2328 4th Generation

$ ******************************** RecGuru Browser subtitles

$ #define MODULE_BROWSER_TITLE 2331
2331 Module Failures

$ #define CTL_BROWSER_TITLE 2332
2332 Controller Failures

$ #define LUN_BROWSER_TITLE 2333
2333 Logical Unit Failures

$ #define DRIVE_BROWSER_TITLE 2334
2334 Drive Failures

$ #define HARDWARE_BROWSER_TITLE 2335
2335 Hardware Component Failures

$ #define MISC_BROWSER_TITLE 2336
2336 Miscellaneous Failures

$ #define PARITY_CHECK_OK 2337
2337 No parity errors detected on 

$ #define FWDL_UPGRADE_RESTRICT_MSG 2338
2338 This controller model does not support a direct\nupgrade from pre-2.05.03 to 3.X firmware.\nRefer to the Firmware Specifications section in the\nInstallation and Support Guide for the firmware\nfiles upgrade path.

$ #define FWDL_ONLINE_UPGRADE_RESTRICT_MSG 2339
2339 Because you are upgrading from pre-2.05.03 firmware\nto 3.X firmware, you must use the Offline method.

$ #define REC_UPGRADE_RESTRICT_MSG 2340
2340 Failed -- Upgrading from pre-2.05.03 to 3.X\n%sfirmware requires active/active controllers\n%sand each controller must own at\n%sleast one LUN.

$ #define REC_ONLINE_UPGRADE_RESTRICT_MSG 2341
2341 Failed -- Upgrading from pre-2.05.03 to 3.X\n%sfirmware requires the Offline method.

$ #define REC_FORMATFAILHEADER 2342
2342 Format Failed

$ #define EVENT_AEN_2982_CAUSE 2343
2343 Controller firmware was successfully synchronized with the replacement controller.

$ #define EVENT_FW_UPGRADE_ACTION 2344
2344 Use the Recovery Guru/Health Check in the Recovery Application to obtain instructions on how to download firmware to make the versions consistent.

$ #define DRIVES_ON_SAME_CHANNEL 2345
2345 The drive group/LUN you are about to create is valid.\nHowever, it has two or more drives on the same drive\nchannel.  For maximum redundancy, each drive in a\ndrive group should be on a different channel.\n \nIf desired, select Cancel and use Options >> Drive\nSelection to view the currently selected drives.

$ #define ST_UNABLE_TO_COLLECT_HDR 2346
2346 Cannot Obtain Data

$ #define ST_UNABLE_TO_COLLECT 2347
2347 An error has occurred while attempting to obtain performance data\nfrom a controller. Run Recovery Guru in the Recovery Application if\nyou suspect a controller problem.\n \nSelect OK to exit the Performance Monitor.

$ #define REC_FIRMWARE_UPGRADE_REQUIRED 2348
2348 The versions of firmware on the controllers in the RAID Module\nare incompatible. One controller has version 2.X and the other\ncontroller has version 3.X. The version 2.X controller must be\nupgraded immediately. Please use the Maintenance and Tuning\napplication to upgrade the controller firmware from version 2.X to\n3.X.\nNOTE: You must select the OFFLINE upgrade type to download\nthe new controller firmware.\n \nNOTE: If the Maintenance and Tuning application was running while\nbringing the controller online, exit and restart the\nMaintenance application before downloading controller firmware.\n \nCAUTION: If the controller you replaced in slot A has 2.5.3\nfirmware or earlier, you MUST use the procedure for upgrading\nfirmware described in the section, "Troubleshooting, Replacing\nControllers", in the installation guide.

$ ************** Trayed Fan (not installed)

$ #define TRAYED_FAN_OUT_TITLE 2351
2351 Fan Not Installed

$ #define TRAYED_FAN_OUT_CAUSE 2352
2352 A fan canister has been removed and not replaced or has not been installed properly.

$ #define TRAYED_FAN_OUT_WARNING 2353
2353 no entry

$ #define TRAYED_FAN_OUT_IMPORTANT 2354
2354 If your RAID Module is configured such that this fan canister is not necessary for safe operation, this warning can be ignored.

$ #define TRAYED_FAN_OUT_STEPS 2355
2355 Replace the fan canister if applicable or make sure that it is installed/seated correctly. 

$ #define TRAYED_FAN_OUT_NOTES 2356
2356 no entry



$ ************** Trayed Power Supply (not installed)

$ #define TRAYED_PS_OUT_TITLE 2361
2361 Power Supply Not Installed

$ #define TRAYED_PS_OUT_CAUSE 2362
2362 A power supply has been removed and not replaced or has not been installed properly.

$ #define TRAYED_PS_OUT_WARNING 2363
2363 no entry

$ #define TRAYED_PS_OUT_IMPORTANT 2364
2364 If your RAID Module is configured such that this power supply is not necessary for safe operation, this warning can be ignored.

$ #define TRAYED_PS_OUT_STEPS 2365
2365 Replace the power supply if applicable or make sure that it is installed/seated correctly. 

$ #define TRAYED_PS_OUT_NOTES 2366
2366 no entry


$ ******************************** Lun Reconfiguring - Dead

$ #define LUN_DEAD_RECONFIG_TITLE 2371
2371 Dead LUN - During Modification

$ #define LUN_DEAD_RECONFIG_CAUSE 2372
2372 Drive(s) have failed in a drive group that is undergoing a LUN modification operation (for example, changing RAID level or a capacity expansion).

$ #define LUN_DEAD_RECONFIG_WARNING 2373
2373 A LUN modification operation will remain suspended (Dead LUN(s) / drive group "modifying") until you replace and revive the failed drive(s).

$ #define LUN_DEAD_RECONFIG_IMPORTANT 2374
2374 no entry 

$ #define LUN_DEAD_RECONFIG_STEPS 2375
2375 1. Remove and replace each Failed drive in this drive group (see drive list above). \\p\\p 2. Select Options>>Manual Recovery>>Drives. The drives you replaced in step 1 should transition to a Replaced status (this may take several minutes). If the drives do not transition to Replaced, reselect the module and Options>>Manual Recovery>>Drives to refresh the screen. \\p\\p 3. Record the LUNs associated with the Replaced drives. \\p\\p 4. Highlight each Replaced drive and select Fail and then Revive (this will transition the LUNs to an Optimal status and the modification operation that was suspended will continue). Allow the modification operation to complete before going to step 5. \\p\\p 5. Select Options>>Manual Recovery>>LUNs, highlight the LUNs you recorded in step 3, and select Format.

$ #define LUN_DEAD_RECONFIG_NOTES 2376
2376 See the Configuration Application to display the percent complete for the ongoing storage modification operation for this drive group. 

$ #define LUN_DEAD_RECONFIG_ICON 2377
2377 no entry

$ #define MOD_NAME_CHANGE_MSG 2378
2378 Module Name changed from %s to %s.

$ #define EVENT_AEN_5D80_CAUSE 2380
2380 A drive has reported that a failure prediction threshold has been exceeded. This indicates that the drive may fail within the next 24 hours.

$ #define EVENT_PRED_FAILURE_ACTION 2381
2381 Policies for drive-predicted failure notifications vary depending on such factors as performance and availability requirements, RAID level, and use of Hot Spare drives. If replacing the drive in advance of failure, you MUST first fix any Failed components to prevent possible data loss. If the drive is contained in a RAID 0 LUN, back up your data BEFORE failing the drive. Fail the indicated drive using Options>>Manual Recovery>>Drives>>Fail in the Recovery Application (its fault LED will turn ON). Then replace it with a spare drive of adequate capacity. You must re-format the affected RAID 0 LUNs and restore data from your back up. For all other RAID levels, the data on the drive will be reconstructed upon replacing the drive. Note that drive-predicted failure notifications generated as a result of normal host-generated LUN I/Os are reported only for the LUNs containing the drive. Notifications as a result of internally generated controller commands to the drive or during controller start-of-day operations are reported for ALL existing LUNS. Contact your Customer Support Representative if you have questions.

$ #define SNMP_69	2382
2382 Drive-reported failure prediction


$ ******************************** Predicted Drive Failure (PDF)

$ #define DRIVE_PREDICT_TITLE 2391
2391 Drive Predicted Failure

$ #define DRIVE_PREDICT_CAUSE 2392
2392 A drive has reported that a failure prediction threshold has been exceeded. This indicates that the drive may fail within the next 24 hours.

$ #define DRIVE_PREDICT_WARNING 2393
2393 \\1 o \\0 Repair any components that have a Failed status first. Failure to do so may result in data loss. \\p\\p\\1 o \\0 Removing and replacing the problem drive with another one without failing it first can cause data corruption or data loss. The data on the replaced drive must be reconstructed or restored from your back up.

$ #define DRIVE_PREDICT_IMPORTANT 2394
2394 \\1 o \\0 Policies for drive-predicted failure notifications vary depending on such factors as performance and availability requirements, RAID level, and use of Hot Spare drives.

$ #define DRIVE_PREDICT_STEPS 2395
2395 To replace the drive in advance of failure: \\p\\p 1. For RAID 0 LUNs you must back up your data BEFORE failing the drive. \\p\\p 2. Fail the drive using Options>>Manual Recovery>>Drives>>Fail in the Recovery Application (the drive's fault LED will turn ON). \\p\\p 3. Replace the drive with a spare drive with capacity equal to or greater than the failed drive. Reconstruction should begin for non-RAID 0 LUNs.\\p\\p 4. For RAID 0 LUNs, re-format the affected LUNs and restore data from your back up. Contact your Customer Support Representative if you have questions. 

$ #define DRIVE_PREDICT_NOTES 2396
2396 \\1 o \\0 You can remove the failed drive while the RAID Module is on and receiving I/O. \\p\\p\\1 o \\0 You can locate a drive using the List/Locate Drives option for the drive group containing this drive in the Configuration Application. \\p\\p\\1 o \\0 Drive-predicted failure notifications generated as a result of normal host-generated LUN I/Os are reported only for the LUNs containing the drive. Notifications as a result of internally generated controller commands to the drive or during controller start-of-day operations are reported for ALL existing LUNS. 

$ #define DRIVE_PREDICT_ICON 2397
2397 UnrespDrive

$ #define STAT_PARITY_INC_FOUND 2398
2398 Parity inconsistencies were found on the given device.  They were not repaired\nbecause parity repair has been disabled.\n \n

$ #define STAT_PARITY_INC_RANGELABEL 2399
2399 Inconsistent Parity Range:\n

$ #define STAT_PARITY_INC_NUMBLKLABEL 2400
2400 Number of Inconsistent Blocks: %ld\n

$ #define PARITY_INCONSISTENT_NOREPAIR 2401
2401 Inconsistent parity found blocks %d-%d (%d blocks).\nBlocks not repaired because parity repair is disabled.\n

$ #define REC_PARITY_INC_NOREPAIR 2402
2402 Parity inconsistencies were found on:\n%s.\n \nSelect Message Log in the Status\nApplication to determine the range and\nnumber of inconsistent data blocks.

$ #define RECONFIG_FAILURE_LUN_CONSTRAINTS 2403
2403 Unable to perform the segment size modification because of an internal\nresource limitation in the RAID Module.\n \nThe only way to complete this modification is to back-up the data on this\nLUN, delete the LUN, and then recreate it with the desired segment size.

$ #define EVENT_9153_CAUSE 2404
2404 Unable to perform the segment size modification because of an internal resource limitation in the RAID Module.

$ #define NVUTIL_USAGE_7 2405
2405 \n     nvutil -d [<device>]

$ #define MSG_DLFW_BAD_FILE_FORMAT 2406
2406 Unable to download firmware.  Bad firmware file format.\n

$ #define MSG_DLFW_CANT_RESET 2407
2407 Unable to download firmware.  Cannot reset controller.\n

$ #define MSG_DLFW_EXCLUSIVE_ACCESS_ERROR 2408
2408 Unable to download firmware.  Cannot get exclusive access to device.\n

$ #define MSG_DLFW_INVALID_BOARD_TYPE 2409
2409 Unable to download firmware.  Incompatible board type for code downloaded.\n

$ #define MSG_DLFW_GENERAL_FAILURE 2410
2410 Unable to download firmware.  The controller detected an error while downloading microcode and storing it in non-volatile memory.\n

$ #define MSG_DLFW_RECONFIG_IN_PROGRESS 2411
2411 Unable to download firmware.  Reconfiguration in progress.\n

$ #define MSG_DLFW_UNKNOWN_ERROR 2412
2412 Unable to download firmware.  Unknown error.\n

$ #define RAID0_DESC 2413
2413 RAID 0 -- NON-REDUNDANT, DISK STRIPING MODE\n  No data redundancy available!\n  NOT recommended for high availability needs.\n  Good for non-critical data.\n  Any drive failure causes TOTAL data loss.

$ #define RAID1_DESC 2414
2414 RAID 1 -- STRIPING / MIRRORING MODE\n  Also called RAID 10 or 0+1.\n  Identical data maintained on drive pairs.\n  Half of the drives are available for user data.\n  Good for very high data availability.\n  Drive pair failure causes TOTAL data loss.

$ #define RAID3_DESC 2415
2415 RAID 3 -- HIGH BANDWIDTH MODE\n  Data and parity striped across a drive group.\n  One drive's worth for redundancy; all other\n  drives available for user data.\n  Good for large data transfers.\n  Any two-drive failure in same group causes\n  TOTAL data loss.

$ #define RAID5_DESC 2416
2416 RAID 5 -- HIGH I/O MODE\n  Data and parity striped across a drive group.\n  One drive's worth for redundancy; all other\n  drives available for user data.\n  Good for small/medium, random I/Os.\n  Any two-drive failure in same group causes\n  TOTAL data loss.

$ #define DEF_RAID_CHANGE_TITLE 2417
2417 Configuration - Create LUN

$ #define DEF_RAID0_CHANGE 2418
2418 Selecting 1 drive causes the RAID Level to\nautomatically default to RAID 0.

$ #define RAID0_WARNING 2419
2419 

$ #define DEF_RAID1_CHANGE 2420
2420 Selecting 2 drives causes the RAID Level to\nautomatically default to RAID 1.

$ #define NO_HOST_INFO_SUPPLIED 2421
2421 You must specify at least one hostname.

$ #define NO_HOSTA_INFO_SUPPLIED 2422
2422 You must specify a hostname for Hostname A.

$ #define NO_PORT_INFO_SUPPLIED 2423
2423 You must specify at least one port.

$ #define UNIQUE_HOSTB_NOT_SUPPLIED 2424
2424 You must specify a unique hostname for Hostname B\nwhen the independent controllers option is selected.

$ #define NO_PORTB_INFO_SUPPLIED 2425
2425 You must specify a port number for Port B.

$ #define UNIQUE_PORTB_NOT_SUPPLIED 2426
2426 The number for Port B must be\ndifferent than the one specified for Port A.

$ #define PORT_INFO_INVALID 2427
2427 A port field must contain only numbers.\nPlease re-enter the port number(s).

$ **** fwutil usage ****

$ #define FWUTIL_USAGE_1 2428
2428 \n     fwutil <file> <raid controller specifier>

$ #define FWUTIL_USAGE_2 2429
2429 \n     fwutil -v [<raid controller specifier>]

$ #define FWUTIL_USAGE_3 2430
2430 \n     fwutil -?

$ #define FWUTIL_USAGE_5 2431
2431 \n

$ #define FWUTIL_USAGE_END 2432
2432 \n


$ #define MSG_DRIVE_UNCERTIFIED     2433
2433 Uncertified


$ ******************************** Uncertified Drive

$ #define DRIVE_UNCERT_TITLE 2440
2440 Uncertified Drive

$ #define DRIVE_UNCERT_CAUSE 2441
2441 One or more Uncertified drives have been detected. A Failed drive may have been replaced by an Uncertified drive.

$ #define DRIVE_UNCERT_WARNING 2442
2442 Uncertified drives are treated similarly to Failed drives. That is, they are unavailable for configuration, reconstruction, or as global hot spares. LUNs containing Uncertified drives cannot be Optimal. That is, they will either be Degraded or Dead.

$ #define DRIVE_UNCERT_IMPORTANT 2443
2443 Drive fault LEDs for Uncertified drives are ON.

$ #define DRIVE_UNCERT_STEPS 2444
2444 Reference any additional Recovery Guru procedures listed in the Summary Information screen for this drive group. Degraded or Dead LUN entries for example. Replace the above drive(s) with certified ones obtained from your vendor. Rerun the Recovery Guru to ensure the drives are Optimal.

$ #define DRIVE_UNCERT_NOTES 2445
2445 See Module Profile > Drives for detailed vendor information for the Uncertified drives.

$ #define DRIVE_UNCERT_ICON 2446
2446 UnrespDrive

$ #define NVRAM_LOOP_SET 2447
2447 %s - The Fibre Channel Loop ID has been changed from %x to %x.\n

$ #define NVRAM_LOOP_DISPLAY 2448
2448 %s - The Fibre Channel Loop ID is %x.\n

$ #define NVUTIL_USAGE_8 2449
2449 \n     nvutil -o -i [<device>]

$ #define NVUTIL_USAGE_9 2450
2450 \n     nvutil -i [-q] <loopID> [<device>]

$ #define NVUTIL_FIBRE_CHANGE 2451
2451 You must power-cycle the RAID Module for the new Fibre Channel ID to take effect.\nYou may need to reboot the host to see the new ID.\n

$ #define REC_CTL_UPGRADE_NOT_SUPPORTED 2452
2452 Failed -- The firmware upgrade operation is not\n%ssupported on this model of controller.

$ #define OPERATION_NOT_SUPPORTED_ON_UTM_LUN 2453
2453 Operation not allowed on access LUN %d.\n

$ #define ABORTED_UTM_LUN 2454
2454 ABORTED - Access LUN\n

$ #define FAILED_INDIRECT_CONNECTION 2455
2455 Could not connect to the controller on host %s\nat port %d.  Check your network connection.\nAlso check to see that the networked server agent\nis running on host %s and that it has\na controller mapped to port %d.\n

$ #define GETPORTS_USAGE_1 2456
2456 \n\t%s <hostname>

$ #define GETPORTS_USAGE_2 2457
2457 \n\t%s [-?]\n

$ #define GETPORTS_USAGE_3 2458
2458 \n\n\tNote:  This utility uses network port %s to\n\t       communicate with the networked server agent.\n

$ #define GETPORTS_NO_MODULES_FOUND 2459
2459 \nFound no modules mapped to ports on host %s.\n\nCheck the system error log on host %s\nfor messages from the networked server agent.\n

$ #define GETPORTS_CANT_CONTACT_NSAGENT 2460
2460 \nUnable to contact the networked server agent on host %s.\n\nCheck the spelling of the hostname.\n\nIf correct, check your network connection\nby typing "ping %s" at a command prompt.\n\nIf the network connection is OK, go to host %s\nand check the system error log for messages from\nthe networked server agent.\n

$ #define GETPORTS_RPC_FAILURE 2461
2461 \nUnexpected remote procedure call error.  Status:  0x%lx = %ld.\n\nTry running this utility again.\nIf it still fails, check your network setup.\n


$ ******************************** Offline Spare Drive

$ #define DRIVE_OFFLINE_TITLE 2462
2462 Offline Unassigned Drive

$ #define DRIVE_OFFLINE_CAUSE 2463
2463 An Unassigned drive has been placed Offline. This can occur if a drive belonging to a LUN was repositioned within this module or was inserted into this module from another module.

$ #define DRIVE_OFFLINE_WARNING 2464
2464 \\1 o \\0 Offline Unassigned drives are unavailable for configuration into new or existing LUNs, dynamic capacity expansion, or as global hot spares. \\p\\p\\1 o \\0 Offline Unassigned drives may contain valid LUN information and data. \\p\\p\\1 o \\0 Scenarios described in this recovery procedure reflect possible causes of Offline Unassigned drives but do not comprise an exhaustive list. User scenarios resulting in Offline drives may differ.

$ #define DRIVE_OFFLINE_IMPORTANT 2465
2465 Drive fault LEDs for Offline drives are ON.

$ #define DRIVE_OFFLINE_STEPS 2466
2466 The recovery steps depend on the root cause of the Offline drive. Samples are enumerated below: \\p\\p\\1 o \\0 The controller automatically recognizes a drive's new location within a module. The drive will remain a member of its LUN provided that another drive is not inserted into the vacated drive's slot BEFORE the original drive is inserted into its new location. If another drive is inserted into the vacated slot first, this drive will be considered a replacement for the removed drive and the appropriate replaced drive action will follow. This action depends on the RAID level and LUN state. For instance, replacing an Optimal drive from an Optimal RAID 5 LUN will initiate reconstruction. After the original drive is inserted into its new slot, it becomes Offline and is decoupled from its LUN. \\p\\pIf the Replaced drive is reconstructing, consider allowing the drive to complete reconstruction and Fail and Revive the Offline drive (using Options>>Manual Recovery>>Drives) to return it to an Optimal Unassigned state. \\p\\pIf the replaced drive is not reconstructing, return the original drive to its position and Revive or Reconstruct it using Options>>Manual Recovery>>Drives. \\p\\p\\1 o \\0 An incomplete set of drives containing a "foreign" LUN was inserted into this module. A foreign LUN is a LUN that was created on another module. Identify the missing drive(s) comprising the foreign LUN and insert them into this module in any empty Unassigned drive slot. Once all drives comprising the foreign LUN are successfully transferred, the controller will recognize the LUN and bring it to an online Optimal state. The drives should be hot-swapped, that is, inserted into a running module. Note that the foreign LUN may be renumbered if a LUN number conflict exists. \\p\\p\\1 o \\0 If the LUN information and data residing on the Offline drives are no longer valid, Fail and Revive them using Options>>Manual Recovery>>Drives. This will return them to Optimal Unassigned so that they are available for new LUN configuration.

$ #define DRIVE_OFFLINE_NOTES 2467
2467 \\1 o \\0 It is possible to move LUNs between modules. To accomplish this, ALL drives comprising the LUNs must be transferred. If any drives are omitted, their LUNs will not appear and the drives that were moved will be marked Offline. \\p\\p\\1 o \\0 Before attempting to transfer foreign LUNs to a module, ensure that the maximum number of LUNs that the operating system can support do not currently exist. \\p\\p\\1 o \\0 Unless foreign LUNs are to be moved, individual drives or entire drive trays inserted into a module from other modules should be cleared of all LUN configuration information to ensure that no old LUN information remains. Use the Configuration application's Clear Configuration to accomplish this. Otherwise the controller may attempt to resurrect the foreign LUNs with unpredictable consequences. \\p\\p\\1 o \\0 An Unassigned Offline drive should remain Offline if it is repositioned to other Unassigned drive slots. Some older versions of controller firmware, however, may transition an Unassigned Offline drive to Replaced. If this occurs, treat the Replaced drive in a similar fashion to an Offline drive as described in this recovery procedure. Note that its fault LED will be OFF.

$ #define DRIVE_OFFLINE_ICON 2468
2468 FailUnassigned

$ #define DCE_WARN_TITLE 2469				
2469 Modify Group Capacity Warning

$ #define DCE_LARGER_DRIVE_CAPACITY 2470
2470 One or more drives you have selected has a capacity that is\nlarger than any of the drives currently in the drive group.\nIf you perform this operation using this drive, you will not\nbe able to use some of the capacity on the\nselected drive(s).\n \nNOTE: If you need to determine the capacity of the drives\nin the current drive group, select Cancel twice to return\nto the main configuration window. Highlight the desired\ndrive group, and then select List/Locate Drives.\n \nSelect OK to proceed with this operation.

$ #define DCE_INSUFFICIENT_DRIVE_CAPACITY 2471
2471 Could not modify the group capacity because either\n(1) another modification is being performed using the same controller, or\n(2)one or more drives you have selected has a capacity that is\ntoo small to hold the LUNs currently on the drive group.\n \nIf another modification is in progress using the same controller,\nwait until that operation has finished.\n \nIf another modification is not in progress using the same controller,\nyou must\na) Replace your smallest drive selections with ones having\nlarger capacities, and/or\nb)  Select more drives for the capacity expansion.

$ #define MSG_IAF_IN_PROGRESS 2472
2472 This operation cannot be performed\nat this time.  A logical unit is still\nbeing initialized in this drive group.\n \nWait for the logical unit to complete\nits initialization and try the operation\nagain.

$ #define EVENT_AEN_0C00_BENIGN_CAUSE 2473
2473 The controller has detected an unexpected battery failure.  Write caching will be disabled.

$ #define EVENT_AEN_0C00_ACTION 2474
2474 The Recovery Guru may help you determine which component has failed. After repairing or replacing the component, you should restore the LUN's data from back up.

$ #define EVENT_AEN_0C80_ACTION 2475
2475 You should restore the LUN's data from back up.

$ #define GENERATED_BY_HEADER 2476
2476 Profile Generated By: %s %s%s

$ #define FIBRE_VERSION  2477
2477 \nFibre Level       %s

$ #define NVUTIL_BAD_ARGS4 2478
2478 Bad argument %s in nvutil command line, the ID must be in the range 0-ff(hexadecimal integer).\n

$ #define DISPLAY_PROD_SERIAL_NUM 2479
2479 %s - Product Serial Number is %s\n

$ #define CHANGE_PROD_SERIAL_NUM 2480
2480 %s - The Product Serial Number was changed from %s to %s\n

$ #define LIMIT_PROD_SERIAL_NUM 2481
2481      Product Serial Number cannot be more than 16 characters.\n

$ #define MODULE_PROD_SERIAL_NUM 2482
2482 Module name = %s\n

$ #define MODULE_FAILURE_CAUSE_INDIRECT_NW 2483
2483 Unable to communicate with the only controller or both controllers in the RAID Module. A Failed Module could be caused by one of the following problems:\\p\\p \\1 o \\0 No power to the RAID Module \\p\\p \\1 o \\0 You have physically removed the RAID Module \\p\\p \\1 o \\0 Disconnected or faulty cables \\p\\p \\1 o \\0 Transceivers (Networked (Ethernet) connection only) \\p\\p \\1 o \\0 The networked server agent on the host system is not running, has assigned different port number(s) for the controller(s), or has failed \\p\\p \\1 o \\0 Adapter failure \\p\\p \\1 o \\0 Defective RAID Controller(s)

$ #define MODULE_FAILURE_STEPS_2INDIRECT_NW 2484
2484 \\p\\p \\1 Fixing Adapter Problem \\0 \\p 3. Fix the adapter problem and then re-run the Recovery Guru.\\p\\p - If a Failed Module is reported again, then the problem is at the connection, host system, or RAID Controller(s). Go to step 4 to check the connection.\\p\\p - If a Failed Module is NOT reported again, then the problem has been fixed. You are done with this procedure. \\p\\p \\1 Checking/Fixing The Connection \\0 \\p 4. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables \\p\\p \\1 o \\0 Transceivers (Networked (Ethernet) connection only) \\p\\p - If there is a problem with the connection, go to step 5.\\p\\p - If these components are OK, the problem is at the host system or RAID Controller(s). Go to step 6.
 
$ #define MODULE_FAILURE_STEPS_3INDIRECT_NW 2485
2485 \\p\\p 5. Fix the connection problem (for example, reconnect or replace cable, etc.) and then re-run the Recovery Guru.\\p\\p - If a Failed Module is reported again, then the problem is at the host system or RAID Controller(s). Go to step 6. \\p\\p - If a Failed Module is NOT reported again, then the problem has been fixed. You are done with this procedure. \\p\\p \\1 Checking The Host System \\0 \\p 6. Check the following on the host system:  \\p\\p - If there is a problem on the host system, correct it using the information below and then go to step 7.\\p\\p - If everything on the host system is OK, the only controller or both controllers in the RAID Module are probably defective. Go to step 8.  \\p\\p \\1 o \\0 Is the host system's OS booted up? If not, boot it. \\p\\p \\1 o \\0 Is the networked server agent running? If not, start it.

$ #define MODULE_FAILURE_STEPS_4INDIRECT_NW 2486
2486  \\p\\p \\1 o \\0 Are there any error messages from the networked server agent in the system's log? If yes, follow the instructions given in the agent's error messages. \\p\\p \\1 o \\0 Do the port number(s) assigned by the networked server agent match the port number(s) entered in the storage management software for the failed module's controller(s)?  Use steps a-d below:  \\p\\p a. On the host system, open the agent's device mapping file and note the port number(s) assigned for the failed controller(s). \\p\\p b. In the Recovery Application, choose Select Module. \\p\\p c. Highlight the failed module and select Edit. \\p\\p d. If the port number(s) do NOT match those noted in step a, use the Select Module interface to remove the failed module and re-add it using the port number(s) noted in step a. \\p\\p 7. Re-run the Recovery Guru.\\p\\p - If a Failed Module is reported again, the only controller or both controllers are probably defective. Go to step 8.\\p\\p - If a Failed Module is NOT reported again, then the problem has been fixed.  You are done with this procedure.

$ #define MODULE_FAILURE_STEPS_5INDIRECT_NW 2487
2487 \\p\\p 8. Read the following notes and then remove the defective controller(s) and insert the new controller(s) firmly into the RAID Module. \\p\\p NOTE 1: If the failed module has PCI RAID controller(s), follow the instructions that came with the controller(s) to replace them.  Then continue with steps 9-11. \\p\\p NOTE 2: Because you are replacing the only controller or both controllers in the RAID Module, the RAID Module name may change because of the different serial numbers associated with each new controller. \\p\\p 9. Stop and restart the networked server agent on the host system, open the agent's device mapping file, and note the port number(s) it assigned to the new controller(s). \\p\\p 10. In the Recovery Application, choose Select Module, highlight the failed module, and select Remove.  Re-add the module using the new port number(s) noted in step 9. \\p\\p 11. Re-run the Recovery Guru to ensure the failure has been fixed. \\p\\p - If a Failed Module is reported again and you have ruled out all other causes listed in this procedure, contact a Customer Support Representative. \\p\\p - If any other type of problem is reported (such as a mismatch of controller firmware versions), fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.

$ #define MODULE_FAILURE_INDIRECT_NOTES 2488
2488 \\1 o \\0 If you replaced the controller and the filesystems/logical units do not respond, you may need to reboot the host system.\\p\\p \\1 o \\0 If you replaced BOTH controllers in your RAID Module, you must reboot the host system to enable RDAC protection on the module.

$ #define CTL_UNRESP_CAUSE_INDIRECT_NW 2489
2489 An unresponsive controller can be caused by the following:\\p\\p \\1 o \\0 Disconnected or improperly seated controller\\p\\p \\1 o \\0 Disconnected or faulty cables \\p\\p \\1 o \\0 Disconnected or faulty transceiver (Networked (Ethernet) connection only)\\p\\p \\1 o \\0 Adapter failure \\p\\p \\1 o \\0 The networked server agent on the host system has assigned a different port number for the controller or is failing to communicate with it\\p\\p \\1 o \\0 Defective RAID Controller

$ #define CTL_UNRESP_INDIRECT_NW_IMPORTANT 2490
2490 \\1 o \\0 The status displayed for the RAID controller may be Unresponsive or Dead. \\p\\p\\1 o \\0 A power cycle of the RAID module during the host operating system's device scan (for example, during a host reboot) may cause the storage management software to detect an Unresponsive controller. Rebooting the host operating system after the RAID module has completed its initialization may fix the problem.

$ #define CTL_UNRESP_STEPS_1INDIRECT_NW 2491
2491 1. Check the following components on both ends of the connection for bent pins, loose connections, or visible damage:\\p\\p \\1 o \\0 External cables \\p\\p \\1 o \\0 Transceivers (Networked (Ethernet) connection only) \\p\\p 2. Fix any connection problems (for example, reconnect or replace cable, etc.).\\p\\p 3. Re-run the Recovery Guru. \\p\\p - If an Unresponsive controller is still reported, go to step 4. \\p\\p - If an Unresponsive Controller is NOT reported again, then the problem is fixed.  You are done with this procedure. \\p\\p 4. Check the host system's log for any error messages from the networked server agent. \\p\\p - If you find an error message, follow the instructions given. \\p\\p - If you don't find any error messages, use steps a-d to ensure that the port number assigned by the networked server agent matches the port number entered in the storage management software for the unresponsive controller.

$ #define CTL_UNRESP_STEPS_2INDIRECT_NW 2492
2492 \\p\\p a. On the host system, open the agent's device mapping file and note the port number assigned for the unresponsive controller.\\p\\p b. In the Recovery Application, choose Select Module. \\p\\p c. Highlight the module with the unresponsive controller and select Edit. \\p\\p d. If needed, change the port number for the unresponsive controller so it matches the port number noted in step a. \\p\\p 5.  If any action was taken in step 4, re-run the Recovery Guru. \\p\\p - If an Unresponsive controller is NOT reported, then the problem is fixed.  You are done with this procedure. \\p\\p - Otherwise, place the unresponsive controller offline using the Options >> Manual Recovery >> Controller Pairs option and re-run the Recovery Guru. Highlight the Offline Controller failure and select Show Procedure. Use the steps in the controller replacement section of that procedure to replace the controller. Consult a Customer Support Representative, if necessary.\\p\\p - If any other problem is reported, fix it by highlighting the failure, selecting Show Procedure, and following the instructions provided.

$ #define CTL_UNRESP_INDIRECT_NW_NOTES 2493 
2493 \\1 o \\0 If the failure has been resolved and the filesystems/logical units do not respond, you may need to reboot the host system. If you have two controllers, select LUN Balancing in the Maintenance and Tuning Application to make sure the logical units are balanced across both controllers. \\p\\p\\1 o \\0 Run the command line utility "lad" to verify all controllers are visible to the storage management software. 


$ *******************************

$ #define SNMP_70	2504
2504 Fibre link error rate threshold exceeded

$ #define CAUSE_FIBRE_ERROR 2505
2505 A link error rate threshold on the fibre channel loop has been exceeded. This indicates that a component (for example, MIA, GLM, or GBIC) on the loop may be failing. More than likely, the fault is not on the component reporting the error but on the component directly upstream in the loop topology.

$ #define ACTION_FIBRE_ERROR 2506
2506 Visually check the components on the loop as well as run any diagnostic tools appropriate for each component.

$ #define REC_CONTNEWGEN 2507
2507 New Generation

$ #define OPEN_NEWGEN_DEVICE_FAILED 2508
2508 Can't open device %s. %s controller.  Aborting\n\n

$ #define CTL_NEW_GENERATION 2509
2509 Controller %s is %s

$ *******************************

$ #define DELETE_LUN_ZERO_MSG 2510
2510 \n \nCAUTION:  You are about to delete LUN 0!\nMany Operating Systems depend on this LUN always\nexisting, so you may lose communication with the array\nat any moment. Re-create LUN 0 immediately.

$ #define DELETE_LUN_ZERO_HEADER 2511
2511 Confirm Deletion of LUN 0

$ #define DELETE_LUN_ZERO_TITLE 2512
2512 Delete

$ #define SC_CURRENT_SW_VER 2513
2513 The controller firmware version for controller %s (module: %s) is %s.\n

$ #define FWUTIL_ARRAYLIST_FAIL 2514
2514 The fwutil program cannot get the array list.\n

$ #define FWUTIL_NO_DEVICE 2515
2515 There are no devices (controllers) in the system.\n

$ #define FWUTIL_INVALID_CTRL_NAME 2516
2516 Invalid controller name (%s) in fwutil command line.\n

$ #define EVENT_AEN_5D90_CAUSE 2517
2517 An excessive number of drive or SCSI bus errors have occurred on a given channel.

$ #define EVENT_CHANNEL_ERRORS_ACTION 2518
2518 An investigation of the given channel should be performed. The channel itself may require corrective action or one or more drives may need to be replaced. Drive failures may result from this channel problem with the resulting effect on LUNs and their data. Contact your Customer Support Representative if you have questions.

$ #define MODULE_FW_MISMATCH 2519
2519 The firmware versions on the controllers in the RAID Module\ndo not match. This can be the result of replacing a\nfailed controller with one containing a different firmware version\nfrom that previously in this slot. Run Recovery Guru to display\nthe recommended recovery steps for a controller firmware mismatch.\nPlease use the Maintenance and Tuning application to upgrade\nthe controller firmware for the replaced controller.

$ #define MODULE_FW_MISMATCH_SUMMARY 2520
2520 The controller firmware versions in the RAID Module do not match.\n

$ #define DRIVUTIL_ERR_8 2521
2521 Invalid lun number (%s); the number must be 0-%d.\n

$ *******************************

$ #define PARITYCK_USAGE_2 2522
2522 \n     parityck [ -a ] [ -f ] [ -n ] [ -q ] [ -r ] [ -R ] [ -t <filename> ] [ -c device ] [ -? ]

$ #define PARITYCK_USAGE_3 2523
2523 \n               [ -a scan all controllers and luns ]

$ #define PARITYCK_USAGE_4 2524
2524 \n               [ -f force parity scan ]

$ #define PARITYCK_USAGE_5 2525
2525 \n               [ -n no notification ]

$ #define PARITYCK_USAGE_6 2526
2526 \n               [ -q quiet display mode ]

$ #define PARITYCK_USAGE_7 2527
2527 \n               [ -r no parity repair ]

$ #define PARITYCK_USAGE_11 2528
2528 \n               [ -R repair parity ]

$ #define PARITYCK_USAGE_8 2529
2529 \n               [ -t trace block data ]

$ #define PARITYCK_USAGE_9 2530
2530 \n               [ -c device name ]

$ #define PARITYCK_USAGE_10 2531
2531 \n               [ -? display usage information ]

$ #define PARITYCK_USAGE_2_END 2532
2532 \n

$ #define PARITY_MEDIA_ERROR 2533
2533 ABORTED - Media Error. See the Message Log of the Status Application.\n

$ #define EVENT_AEN_E003_CAUSE 2534
2534 Destination Channel Error. The drive may be experiencing read errors but has not been failed. 

$ #define EVENT_AEN_E003_ACTION 2535
2535 If the same error continues to be returned, the user should replace the drive. Consider the state of the LUN containing this drive, however, before replacing it. If the drive is contained in a RAID 0 LUN, attempt to back up your data BEFORE failing the drive. Fail the indicated drive using Options>>Manual Recovery>>Drives>>Fail in the Recovery Application (its fault LED will turn ON). Then replace it with a spare drive of adequate capacity. You must re-format the affected RAID 0 LUNs and restore data from your back up. For all other RAID levels, the data on the drive will be reconstructed upon replacing the drive. Run the Recovery Guru or Health Check for possible related problems and recovery actions. Also refer to the Message Log for associated entries. Contact your Customer Support Representative if you have questions.

$ #define PARITY_MEDIA_ERROR_CAUSE 2536
2536 A parity scan on LUN %d was terminated due to an error. This was most likely the result of a media error that occurred during a read operation. If this is the case, the Messsage Log of the Status Application will contain a media error for the particular drive(s) experiencing the difficulty. Locate the hardware error entry in the Message Log that occurred just prior to the parity scan termination and complete the recommended action for this drive. Consult a Customer Support Representative if necessary.
