$ 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:  %ld blocks  (%ld 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 Services 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, check the online help topic, Status Application>>ASC/ASCQ Error Codes, 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 battery or drive error. Attempt to restore your data. If you suspect a drive failure, go to the Recovery Guru.

$ #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 Reconstruction failed because a read error occurred on a drive other than the replaced 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 can not 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 RECGURU_HEADING 159
159 Recovery Guru - Summary Information

$ #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 Finish 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 Finish 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, Status Application>>ASC/ASCQ Error Codes, for details. If needed, contact a Customer Services 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 status, start health check or performance monitor.

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

$ #define LAUNCH_RECOVERY_DESC 216
216 Use the Recovery Guru, start parity check/repair, perform manual recovery.

$ #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 new LUNs from unassigned drives or additional LUNs 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 activity lights.

$ #define CFG_FAILED_LUN_CREATION 259
259 Failed to create the following LUNs on %s: LUN %s.

$ #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\nor more drives on the same drive channel. If possible, for\nmaximum redundancy, each drive in a drive group/LUN should\nbe on a different channel.\n \nIMPORTANT\nIf the number of drives selected is more than the number of\nchannels you have, you cannot avoid this channel conflict.\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 can not\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 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 pair mode to active/active or swap active/passive controllers on RAID Modules.

$ #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, or\n4) another host has the LUNs reserved.\n \nIf another application is using the LUN, wait for the application 

$ #define CONFIG_LIST_LOC_HOTSPARE 343
343 The activity lights of the 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 at this time

$ #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 activity lights of the drives in the\nunassigned drive group are flashing\nin a distinctive 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 backup is detected\nfor this module. Selecting\nCache Without Batteries\n

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

$ #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 An error occurred while saving caching parameters.

$ #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 Controller Mode Change

$ #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 of 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 activity 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 Completed; exception found on 1 RAID Module.

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

$ #define ST_HC_DONE_3 498
498 Health Check Completed; No exceptions found 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 Completed; exception found on %s.

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

$ #define ST_HC_DONE_6 502
502 Health Check Completed; 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: %-100s

$ #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 Refresh message log and change log settings.

$ #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 activity 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 SCSI ID:

$ #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_28 588
588 Optimal

$ #define PROF_MSG_29 589
589 Failed

$ #define PROF_MSG_30 590
590 Replaced

$ #define PROF_MSG_31 591
591 Mismatch

$ #define PROF_MSG_32 592
592 Wrong Replaced

$ #define PROF_MSG_33 593
593 In Warning

$ #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 activity lights of the 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\nON %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.\nReboot the system for the new settings to take effect.\n \n

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

$ #define NVUTIL_ARRAYLIST_FAIL 629
629 The nvutil program can not 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 I/O data path 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 can not 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 can not 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 unknown controller type,\n         which may or may not work properly with this software.\n

$ #define SC_INCOMPATIBLE_SW_VER 662
662 Warning: controller %s(module: %s) has out of date\n         controller software(Version %s),\n         -see the documentation for the correct version.\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 Services 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 backup 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 INVALID_STATE_HEADER 702
702 Verification Failed

$ #define INVALID_STATE_TEXT 703
703 The Recovery Guru cannot verify the failure type(s).\n \nSelect OK and start the Recovery Guru again.

$ #define CANNOT_SECURE_ACCESS_HEADER 704
704 Cannot Secure Access To LUNs

$ #define CANNOT_SECURE_ACCESS_TEXT 705
705 Cannot secure access to the logical units because either:\n \n1) another application or host has reserved the LUNs, or\n2) there are filesystems mounted on the LUNs.\n \nIf another application or host has the LUNs reserved, wait\nuntil it is finished; this recovery procedure cannot proceed\nuntil the LUNs are free.\n

$ #define CANNOT_SECURE_ACCESS_STILL_TEXT 706
706 Still cannot secure access to the logical units.\n \nThe Recovery Guru cannot go any\nfurther with this recovery procedure.\n \nSelect OK to exit this procedure and then\ncontact a Customer Services Representative.

$ #define SUMMARY_REPORT_HEADER 707
707 Summary Report

$ #define SUMMARY_REPORT_DRIVE_TEXT 708
708 The drive(s) at location %s in %s has failed.\n \nAffected Logical Unit(s) = %s\nLUN Status = %s\nRAID Level = %d\n \nYou should replace the drive(s) as soon as possible.

$ #define IMPORTANT_NOTES_HEADER 709
709 Important Notes

$ #define IMPORTANT_NOTES1_3 710
710 NOTE 1:  Make sure you have a replacement drive. Its capacity must\nbe equal to or greater than the failed drive you are replacing.\n \n \nNOTE 2:  You can remove the failed drive while the RAID Module\nis on

$ #define IMPORTANT_NOTE4 711
711  and receiving I/O activity to other drives.\n \n \nNOTE 3:  Make sure you remove the correct drive. Use\nthe drive fault light to help locate the failed drive.

$ #define DEAD_LUN_SPECIALNOTE1_HEADER 712
712 Operating System Consideration

$ #define DEAD_LUN_SPECIALNOTE1 713
713 To the operating system, the inaccessible (dead) logical unit(s)\nis exactly the same as a normal (non-RAID) failed disk drive.

$ #define REPLACEMENT_DRIVE_HEADER 714
714 Replacement For Drive At Location %s

$ #define REPLACEMENT_DRIVE_STEPS1_3 715
715 IMPORTANT\nREAD ALL STEPS BEFORE PROCEEDING.\n \nSTEP 1.  Make sure the replacement drive has adequate capacity.

$ #define REPLACEMENT_DRIVE_STEPS4_6 716
716 \n \nNOTE: In step 4, when you insert the drive, the fault light\nmay come on momentarily.

$ #define CHECKING_DRIVE_HEADER 717
717 Check Drive

$ #define CHECKING_DRIVE_TEXT 718
718 Checking drive at location %s. Please wait...

$ #define RECONSTRUCTION_HEADER 719
719 Reconstruction

$ #define RECONSTRUCTION_TEXT 720
720 Reconstruction has begun on the new replacement drive(s).\n \nNOTE:  To check reconstruction progress or change the\nrate, go to the Status Application.

$ #define RECONSTRUCTION_RAID1_ADP93_NONMIRRORED_TEXT 721
721 Reconstruction has begun on the new replacement drive.\n \nNOTE:  To check reconstruction progress or change\nthe rate, go to the Status Application.\n \nIMPORTANT\nReconstruction must complete before you\ncan replace any other failed drives.\n \nPlease wait...

$ #define RECONSTRUCTION_RAID1_ADP93_COMPLETE_HEADER 722
722 Reconstruction Complete

$ #define RECONSTRUCTION_RAID1_ADP93_COMPLETE_TEXT 723
723 Reconstruction is complete.\n \nSelect OK to continue the recovery procedure.

$ #define RECONSTRUCTION_NOT_BEGUN_HEADER 724
724 Reconstruction Unable To Start

$ #define RECONSTRUCTION_NOT_BEGUN_TEXT 725
725 Reconstruction was not able to start. There is\nstill failed drive(s) at location %s.\n \nSelect OK and start the Recovery Guru again.

$ #define RECONSTRUCTION_FAILED_HEADER 726
726 Reconstruction Failed

$ #define RECONSTRUCTION_FAILED_TEXT 727
727 A drive failed during reconstruction.\n \nSelect OK and start the Recovery Guru again.

$ #define FORMAT_STARTED_HEADER 728
728 Formatting Logical Units

$ #define FORMAT_STARTED_TEXT 729
729 Formatting the affected logical units. Please wait...

$ #define FORMAT_COMPLETE_HEADER 730
730 Logical Unit Format Complete

$ #define FORMAT_COMPLETE_STEPS 731
731 LUN(s) %s has been reformatted.\n \nIMPORTANT\nDo not start I/O until you complete steps 1 and 2.\n \nSTEP 1.  Add the LUN(s) back to the operating system\n(you may need to reboot the system to see the LUNs).

$ #define LUNS_NOT_FORMATTED_HEADER 732
732 Format Failed

$ #define LUNS_NOT_FORMATTED_TEXT 733
733 The format operation on logical unit(s) %s has failed.\n \nSelect OK and check the Message Log in the Status\nApplication for information. Then, start the\nRecovery Guru again.

$ #define FORMAT_FAILED_HEADER 734
734 Drive Failed During Format

$ #define FORMAT_FAILED_TEXT 735
735 A drive failed during formatting.\n \nSelect OK and start the Recovery Guru again.

$ #define INCORRECT_CAPACITY_HEADER 736
736 Incorrect Capacity

$ #define INCORRECT_CAPACITY_OPENINGTEXT 737
737 The replacement drive at location %s does not have a\ncapacity equal to or greater than the failed drive.\nYou must replace it again using another drive.\n \nIMPORTANT\nIf you do NOT have another drive, select\nCancel to exit this recovery procedure.\n \n

$ #define INCORRECT_CAPACITY_STEPS1_2 738
738 \n \nSTEP 1.  Remove the drive at location %s and replace\nit again using a drive with the correct capacity.\n \n \nSTEP 2.  Select OK below only after you've performed step 1.

$ #define INCORRECT_CAPACITY_ABORT_OPENINGTEXT 739
739 You have chosen to exit this recovery procedure.\n \nREMINDER\nThe drive at location %s still does not have\nthe correct capacity.

$ #define INCORRECT_CAPACITY_ABORT_STEPS1_2 740
740 \n \nSTEP 1.  Insert the original failed drive back into location %s.\nYou should replace it as soon as possible.\n \n \nSTEP 2.  When you are ready to replace the drive, re-select\nthe Recovery Guru and follow the steps.

$ #define WRONG_DRIVE_REPLACED_HEADER 741
741 Wrong Drive Replaced

$ #define WRONG_DRIVE_REPLACED_STEPS 742
742 You have replaced the wrong drive.\n \nSTEP 1.  Remove the drive at location %s and replace\nit immediately with the drive you just removed.\n \n \nSTEP 2.  Select OK only after you've performed step 1.

$ #define WRONG_DRIVE_REPLACED_DEAD_STEPS 743
743 A wrong drive was replaced at location %s.\nThis may be causing the dead LUN status.\n \nSTEP 1.  Remove the drive at location %s and replace\nit immediately with the original drive at this location.\n \n \nSTEP 2.  Select OK only after you've performed step 1.

$ #define WRONG_DRIVE_REPLACED_ABORT_TEXT 744
744 One or more drives have still not been replaced correctly.\n \nThe Recovery Guru cannot go any\nfurther with this recovery procedure.\n \nSelect OK to exit this procedure and\nthen contact a Customer Services Representative.

$ #define LUN_STATUS_CHANGE_HEADER 745
745 LUN Status Change

$ #define LUN_STATUS_CHANGE_TEXT 746
746 The affected logical units have changed to a %s status\nbecause a wrong drive that was replaced is now corrected.\n \nSelect OK and run the Recovery Guru again for the\nproper procedure.\n \nNOTE:  The data on these logical units should still be accessible.

$ #define REPLACEMENT_DRIVE_FAILURE_HEADER 747
747 Drive Replacement Failure

$ #define REPLACEMENT_DRIVE_FAILURE_OPENINGTEXT 748
748 The replacement drive at location %s has failed also (possibly\nbecause the drive does not have enough capacity).\nYou must replace it again using another drive.

$ #define REPLACEMENT_DRIVE_FAILURE_STEPS1_2 749
749 \n \nSTEP 1.  Remove the drive at location %s and replace\nit again using another replacement drive.\n \n \nSTEP 2.  Select OK below only after you've performed step 1.

$ #define REPLACEMENT_DRIVE_FAILURE_ABORT_OPENINGTEXT 750
750 You have chosen to exit this recovery procedure.\n \nREMINDER\nThe drive at location %s is still failed.

$ #define REPLACEMENT_DRIVE_ABORT_ENDTEXT 751
751 You should replace it as soon as possible.\nWhen you are ready to replace the drive, re-select\nthe Recovery Guru and follow the steps.

$ #define HOTSPARE_UNASSIGNED_HEADER 752
752 Drive Replacement Complete

$ #define HOTSPARE_UNASSIGNED_COMPLETE 753
753 The drive has been restored and returned to its original\nstatus (unassigned or hot spare).\n \n \n>>>>>>>>>>Recovery Procedure Is Complete.

$ #define SUBSYSTEM_COMPONENT_SUMMARY_FIRST 754
754 A fan or power supply has failed in %s.\n \nNOTE: On some RAID Modules, the fans/power supplies are located\nin a tray called the controller module.

$ #define SUBSYSTEM_COMPONENT_SUMMARY_SECOND 755
755 \n \nReplace the failed component(s) as soon as possible\nbecause a failure to a second power supply or fan\ncould cause the RAID Module to shut down.\n \nThe Recovery Guru will lead you through the steps to\ncorrect the failure.

$ #define SUBSYSTEM_COMPONENT_REPLACE_HEADER 756
756 Module Component Replacement

$ #define SUBSYSTEM_COMPONENT_REPLACE_FIRST 757
757 Replace all fans/power supplies in %s that\nhave their fault lights on.\n \nIMPORTANT\nIt could take 10 minutes before the module reports that the

$ #define SUBSYSTEM_COMPONENT_REPLACE_SECOND 758
758 \n \n \n>>>>>>>>>>Recovery Procedure Is Complete.

$ #define EXIT_RECOVERY_HEADER 759
759 Exiting Recovery Guru

$ #define WARNING_DRIVE_HEADER 760
760 Warning Drive

$ #define WARNING_DRIVE_TEXT 761
761 There is not a Recovery Guru procedure.\n \nA warning drive only applies to a RAID Module with an\nearlier controller version. Use the applicable\nmanuals or call a Customer Services\nRepresentative for specific instructions.\n \nSelect OK to exit.

$ #define DATA_PATH_SUMMARY 762
762 There is a data path failure on %s. It could be\ncaused by the following:\n \n--  Disconnected or faulty cables\n \n--  Disconnected or faulty terminators (SCSI only)\n \n--  Controller failure\n \n--  Host or network adapter failure

$ #define DATA_PATH_CHECK_CABLES_HEADER 763
763 Check Connection

$ #define DATA_PATH_CHECK_CABLES_TEXT 764
764 \n \nSTEP 1.  Check %s for disconnected/faulty cables or\nterminators (SCSI only). Replace or reconnect them as necessary.\n \n \nSTEP 2.  Select OK below only after you've performed step 1.

$ #define CHECK_DATAPATH_HEADER 765
765 Checking Data Path

$ #define CHECK_DATAPATH_TEXT 766
766 Checking condition of data path in %s.\n \nPlease wait...

$ #define DATA_PATH_COMPLETE_HEADER 767
767 Dath Path Recovery Complete

$ #define DATA_PATH_COMPLETE_TEXT1 768
768 The data path failure has been resolved.\n \nIMPORTANT\nIf the filesystems/logical units do not respond,\nyou may need to reboot your system.\n \n \n>>>>>>>>>>Recovery Procedure Is Complete

$ #define DATA_PATH_COMPLETE_TEXT2 769
769 The data path failure has been resolved.\n \nIMPORTANT\nIf the filesystems/logical units do not respond, you may need to reboot your system.

$ #define DATA_PATH_COMPLETE_TEXT3 770
770 \n \n \nIf you have two controllers, go to the Maintenance and Tuning \nApplication to balance the logical units across both controllers.\n \n \n>>>>>>>>>>Recovery Procedure Is Complete

$ #define CONTROLLER_FAILURE_HEADER 771
771 Controller Failure Detected

$ #define CONTROLLER_ALLONLY_FAILURE_TEXT1 772
772 All of the controllers in %s have failed.\n \nDo you want to remove the RAID Module from the system?\n \nIf you select Yes, the module will no longer\nbe recognized.\n \nIf you select No, you will be given the appropriate\nsteps to replace the controller(s).

$ #define CONTROLLER_ALLONLY_FAILURE_TEXT2 773
773 \n \nIMPORTANT TIP\nNormally, you should select No so that you can replace the\nfailed controller. The only reason you should select Yes is if\nyou don't want to continue to use the RAID Module.

$ #define CONTROLLER_FAILURE_REPLACE_HEADER 774
774 Controller Failure Replacement

$ #define CONTROLLERS_FAILURE_REPLACE_TEXT1 775
775 Make sure you have a replacement controller before proceeding.\n \nCAUTION\nMake sure at least 1 minute has elapsed before inserting the new\ncontroller(s).\n \nSTEP 1. Remove the failed controller(s) on %s (there should \nbe a fault light on).

$ #define CONTROLLERS_FAILURE_REPLACE_TEXT2 776
776 \n \n \nSTEP 2.  Insert the new controller(s) firmly into the RAID Module.\n \n \nSTEP 3.  Select OK below only after performing steps 1-2.

$ #define CONTROLLER_NOTRESTORED_HEADER 777
777 Controller Not Restored

$ #define CONTROLLER_NOTRESTORED_TEXT1 778
778 The controller(s) could not be restored. It could be caused\nby the following:\n \n--  The new controller(s) is faulty\n \n--  The new controller(s) was incorrectly inserted in the RAID Module\n \n--  There is a problem with the host or network adapter\n \n

$ #define CONTROLLER_NOTRESTORED_TEXT2 779
779 Check the possible causes listed above and then select\nOK to exit this recovery procedure. Then, start the Recovery Guru\nagain.

$ #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 ONE_CONTROLLER_REPLACEMENT_CANCEL_TEXT1 785
785 You have chosen to exit this recovery procedure.\n \nREMINDER\nYou still need to replace the failed\ncontroller as soon as possible.

$ #define ONE_CONTROLLER_REPLACEMENT_CANCEL_TEXT2 786
786 \n \nYou will need to reboot your system to see the logical units that\nwere owned by the failed controller. They are now owned by\nthe other redundant controller.

$ #define ONE_CONTROLLER_REPLACEMENT_CANCEL_TEXT3 787
787 \n \nIf applicable, you must also mount the filesystems\non the other controller.

$ #define SUMMARY_REPORT_DRIVE_DEGRADED_NOTE 788
788 \n \n \nIMPORTANT\nBecause the LUN(s) have a %s status,\nthe data on this LUN(s) should still be accessible.

$ #define SUMMARY_REPORT_DRIVE_DEAD_NOTE 789
789 \n \n \nIMPORTANT\nBecause the LUN(s) have a dead status, all data on this LUN(s)\nis lost. This procedure will reformat the affected LUNs.\nYou will be required to restore from back-up.

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

$ #define CHANNEL_FAILURE_HEADER 791
791 Channel Failure

$ #define CHANNEL_FAILURE_TEXT 792
792 A possible failure on drive channel %s has been detected\non %s. The affected drives are\n%s.\n \nA channel failure can be caused by a failed controller\ncomponent, disconnected/faulty drive or drive cable,\nor other subsystem circuitry.

$ #define LUN_STILL_DEAD_HEADER 793
793 LUN Status Still Dead

$ #define LUN_STILL_DEAD_TEXT 794
794 The logical unit(s) still have a dead status due to failed\ndrive(s). Select OK and try the Recovery Guru again.

$ #define FORMAT_LUN_DEGRADED_OPT_COMPLETE1 795
795 LUN(s) %s has been reformatted. However, there is still a failed\ndrive(s) that you need to replace. The LUN status is now at\n%s.\n \nIf you want to use the LUNs before you replace the remaining\ndrive(s), use the following steps. 

$ #define FORMAT_LUN_DEGRADED_OPT_COMPLETE2 796
796 Otherwise, select OK and\nuse the Recovery Guru again to replace the failed drives.\n \nIMPORTANT\nDo not start I/O until you complete steps 1 and 2.

$ #define SUMMARY_REPORT_UNASSIGNEDDRIVE_TEXT 797
797 The drive(s) at location %s in %s has failed.\n \nAffected Logical Unit(s) = %s\nLUN Status = %s\nRAID Level = N/A\n \nYou should replace the drive(s) as soon as possible.

$ #define DATA_PATH_ICON_FAILURE 798
798 The controllers are available, but could not switch to\nactive/active mode. There could be an ICON chip failure;\nplease contact a Customer Services Representative.

$ #define DATA_PATH_SWDOWNLOAD_FAILED 799
799 The controller has been replaced, but the firmware download\nwas canceled or did not succeed.  Switching to active/active\nmode is not recommended until the firmware has been downloaded\nto %s.

$ #define DATA_PATH_SCSIOPFAIL_RETRYGURU 800
800 An array SCSI 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 ONE_CONTROLLER_FAILURE_TEXT2 802
802 One of the controllers in %s has failed.\n \nSelect OK to obtain the appropriate\nsteps to replace the failed controller(s).

$ #define CONTROLLER_STILLFAILED_CANCEL 803
803 You have chosen to exit this recovery procedure.\n \nREMINDER\nThe controller(s) or the data path to the controllers are still failed.\n \nYou should replace it as soon as possible.

$ #define DATA_PATH_ICON_FAILURE_HEADER 804
804 Possible ICON Chip Failure

$ #define DATA_PATH_SWDOWNLOAD_FAILED_HEADER 805
805 Firmware Download Failed

$ #define DATA_PATH_SCSIOPFAIL_RETRYGURU_HEADER 806
806 SCSI Operation Failed

$ #define DATA_PATH_NVRAM_CHANGED_HEADER 807
807 NVSRAM Settings Changed

$ #define DATA_PATH_IMPORTANT 808
808 \n \nIMPORTANT\nAt this time, there may be a fault light on the RAID Module\nindicating a controller failure. However, don't replace\nany controllers until you are told to do so.

$ #define CHECK_FORMAT_TEXT 809
809 The next step is to format the LUN(s).\n \nYOU WILL LOSE ALL DATA ON\nTHE AFFECTED LUN(s)!\n \nSelect OK to format the LUN(s). 

$ #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 REPLACEMENT_DRIVE_FAILURE_IMPORTANT 819
819 \n \nIMPORTANT\nIf you do NOT have another replacement drive,\nselect Cancel to exit this recovery procedure.\n \n

$ #define FORMAT_LUN_DEGRADED_OPT_STEPS1_2 820
820 \n \nSTEP 1.  Add the LUN(s) back to the operating system\n (you may need to reboot the system to see the LUNs).\n \n \nSTEP 2.  Copy backed-up data to the LUN(s).\n \n \n>>>>>>>>>>Recovery Procedure Is Complete

$ #define FORMAT_COMPLETE_STEP2 821
821 \n \n \nSTEP 2.  Copy backed-up data to the LUN(s).\n \n \n>>>>>>>>>>Recovery Procedure Is Complete

$ #define WRONG_DRIVE_HEADER 822
822 Drive Replacement Confirmation

$ #define REPLACE_DRIVE_HEADER 823
823 Drive Replacement Condition

$ #define WRONG_DRIVE_DEAD_LUN1 824
824 The Recovery Guru has detected that the drive at location %s has been marked\n"Replaced" by the controller possibly because it was incorrectly replaced\ninstead of the drive at location %s.

$ #define WRONG_DRIVE_DEAD_LUN2 825
825 \n \nIf you have incorrectly removed the drive at location %s and replaced it\nwith a new drive, then you MUST do the following:

$ #define WRONG_DRIVE_DEAD_LUN3 826
826 \n \n- write down the steps below,\n- select Cancel,\n- use the steps once you exit the Recovery Guru to\ncorrect the drive(s) with the Replaced status.

$ #define WRONG_DRIVE_DEAD_LUN4 827
827 \n \nHowever, if you are sure that you have replaced the drive at location %s\nand want to continue with this procedure, select OK.

$ #define WRONG_DRIVE_DEAD_LUN5 828
828 By pressing OK,\nthe Recovery Guru will direct you to replace any other failed drives (if applicable)\nand then format the affected logical units.

$ #define WRONG_DRIVE_DEG_LUN1 829
829 The Recovery Guru cannot continue.\n \nThe logical unit(s) on the drive group associated with the failed drive at\nlocation %s has changed to a Dead status. Either you removed the\nwrong drive or another drive has failed in the drive group.

$ #define WRONG_DRIVE_DEG_COND1 830
830 \n \nCONDITION #1: If you have removed the wrong drive, then you MUST\ndo the following to ensure that your data is not lost.

$ #define WRONG_DRIVE_DEG_COND2 831
831 \n \nCONDITION #2: If another drive has failed during this recovery procedure, then\nall data on the associated logical units is lost. You must then start the Recovery\nGuru again to obtain proper instructions for this situation.

$ #define WRONG_DRIVE_STEPA 832
832 \n \nSTEP 1.  Remove the drive at location %s and replace\nit immediately with the drive you just removed.\n \nSTEP 2.  Make sure you have %s selected, then go to\nOptions in the top menu bar and select Manual Recovery - Drives.

$ #define WRONG_DRIVE_STEPB 833
833 \n \nSTEP 3.  Highlight the drive at location %s and select\nfail, then select revive.\n \nSTEP 4.  Start the Recovery Guru again.

$ #define STILL_FAILED_DRIVE1 834
834 The Recovery Guru has NOT detected that the drive at location %s\nhas been physically replaced. This could be for the\nfollowing reasons:\n \n- You have not replaced the drive.

$ #define STILL_FAILED_DRIVE2 835
835 \n- The replacement drive you used does not have enough capacity\nfor the existing LUNs on this drive group.\n- Reconstruction has not automatically started (degraded\nsituation only).

$ #define STILL_FAILED_DRIVE3 836
836 \n \nAre you certain that you have replaced it and that it has\nenough capacity?\n \n- Select Yes to continue.\n- Select No to obtain instructions again on replacing the drive.

$ #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\nor both of the controllers are not\ncapable of an upgrade to the specified\nfirmware file(s). An intermediate firmware\ndownload may be required.\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.\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 data path 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

$ #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 SUMMARY_REPORT_DRIVE_TEXT1 951
951 \n \nThe Recovery Guru will lead you through the steps to\ncorrect the failure.

$ #define DEAD_LUN_SPECIALNOTE1A 952
952 \nSee your operating system documentation for any special\nrequirements for replacing a failed disk drive and perform\nthem if necessary before proceeding with this procedure.

$ #define REPLACEMENT_DRIVE_STEP3 953
953 \n \nSTEP 2.  Remove the failed drive at location %s from\n%s. Use the fault light to help locate the drive.\n \nSTEP 3.  Keep the failed drive nearby until the replacement\nprocedure is complete.

$ #define REPLACEMENT_DRIVE_STEPS5_6 954
954 \n \nSTEP 4.  Make sure at least 30 seconds have elapsed. Then,\ninsert the new drive completely into the RAID Module.\n \nSTEP 5.  Select OK below only after performing steps 1-4.

$ #define DATA_PATH_SUMMARY1 955
955 \n \nThe Recovery Guru will lead you through the steps to\ncorrect the failure.

$ #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 PREPARE_LUN_FORMAT_HEADER 976
976 Preparing Drives

$ #define PREPARE_LUN_FORMAT_TEXT 977
977 Preparing the replaced drives for LUN formatting. The drive\nfault lights on these drives may turn on. Please wait...

$ #define WRONG_DRIVE_DEG_STEPS 978
978 \n \n- write down the steps below,\n- select OK,\n- use the steps once you exit the Recovery Guru to\ncorrect the drive(s) with the Replaced status.

$ #define PREPARE_UNSUCCESSFUL_HEADER 979
979 Preparation Failed

$ #define PREPARE_UNSUCCESSFUL_TEXT 980
980 An error occurred while preparing the replaced\ndrives for LUN formatting.

$ #define CHANNEL_FAILURE_TEXT1 981
981 \n \nThe Recovery Guru cannot determine the specific hardware\ncomponent causing the channel failure. However, if the\nfailure can be corrected, the steps on the next screen\nprovide instructions on how to restore access to the\ndata on the drives.

$ #define WRONG_DRIVE_DEGRADED_STEPA 982
982 \n \nSTEP 1.  Remove the drive you just inserted and replace\nit immediately with the drive you just removed.\nMake note of its location.\n \nSTEP 2.  Make sure you have %s selected, then go to Options\nin the top menu bar and select Manual Recovery - Drives.

$ #define WRONG_DRIVE_DEGRADED_STEPB 983
983 \n \nSTEP 3.  Highlight the drive that was incorrectly removed\n(use the location information you recorded in step 1)\nand select fail, then select revive.\n \nSTEP 4.  Start the Recovery Guru again.

$ #define STARTUP_PARAMFILE_MISSING 984
984 The parameter file %s is not present - obtain a copy from\nthe installation media, or from a backup.\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 configured LUNs.\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 -- SCSI command (Write Buffer) 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_DRIVEOPTIMAL 1023
1023 Optimal

$ #define REC_DRIVEFAILED 1024
1024 Failed

$ #define REC_DRIVEREPLACED 1025
1025 Replaced

$ #define REC_DRIVEMISMATCH 1026
1026 Mismatch

$ #define REC_DRIVEWRONG 1027
1027 Wrong Replaced

$ #define REC_DRIVEWARNING 1028
1028 In Warning

$ #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 activity 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 An error occurred while attempting\nto fail the drive at location %s.

$ #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\nmistakenly removed it and it originally\nhad an optimal status.\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 drive(s) by\nselecting 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 in the drive group!\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 LUN\n3) another host has the LUNs reserved,\n4) There are one or more drives failed and the LUN(s) are dead, or\n5) A data path failure has occurred.\n \nFor causes 1-3, either wait for the application to finish, unmount\nthe filesystem, or have the other host release the LUNs and then\nretry the format operation.  For causes 4 and 5, run the Recovery\nGuru to verify and fix any data path or drive failures, and then\nretry the operation.

$ #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\nto revive LUN(s) %s.

$ #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\nplace controller %s online.

$ #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 manual recovery.

$ #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 \nThe hot spare drive just created at location %s\nhas a smaller capacity than some of the drives\nin the module. It will not provide coverage for\nthose drives.  

$ #define CREATE_HS_SMALL_DRIVE_ERROR 1120
1120 \nThis drive was not made a hot spare because it has a smaller\ncapacity than all of the assigned drives in the module.

$ #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 occured on %s.  Check the event log for\nmore information.

$ #define REC_FAILED_SCSI_PROBLEMS_2 1139
1139 Rerun the Recovery Guru.  If this problem persists, call\nyour Customer Service Representative.

$ #define CFG_DELHOTSPFAIL 1140
1140 An error occurred while attempting to delete the\nhot spare at location [%d,%d].  Check the Message Log\nin the Status Application for more information.

$ #define ABOUT_BOX_NETWORK_VERSION 1141
1141 Networked Version 

$ #define ABOUT_BOX_SCSI_VERSION 1142
1142 SCSI Version 

$ #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 in one of the disk drive trays have failed. This is a critical condition that may cause the drive 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 An over-temperature condition has been detected in a disk drive tray. This is a critical condition that may cause the drive tray to turn off if you do not resolve the problem quickly.

$ #define RECGURU_TITLE 1162
1162 Recovery Guru - 

$ #define RECGURU_ENVIRON_LABEL 1163
1163 Environmental Card Replacement

$ #define RECGURU_ENVIRON_REPLACE1 1164
1164 There are several conditions which may cause loss of\ncommunication with the environmental card. Therefore,\nuse your hardware manual and the instructions on the\nnext screen to help pinpoint the problem. One possible\nproblem may be that you changed the ID of the card\nwithout cycling power on the controller tray. \n \nCAUTION\nIn some cases, the drives in the drive tray associated\nwith the failed card will

$ #define RECGURU_ENVIRON_REPLACE2 1165
1165  be spun down (failed) to avoid\npotential damage to the drives. This will result in the\nRecovery Guru reporting a series of drive or channel\nfailures.\n \nDO NOT ATTEMPT TO RECOVER THE DRIVE FAILURES\nWITHOUT READING THE STEPS ON THE NEXT SCREEN.\n

$ #define RECGURU_TRAYED_FAN_LABEL 1166
1166 Single Fan Replacement

$ #define RECGURU_TRAYED_FAN_REPLACE1 1167
1167 A fan in one of the disk drive trays has failed.\n \nReplace the fan as soon as possible to keep the drives\nfrom overheating. Consult your hardware manual for\nspecific details.\n \nSTEP 1.  Locate the disk drive tray with the fan\nmodule warning light on.

$ #define RECGURU_TRAYED_FAN_REPLACE2 1168
1168 \n \nCAUTION\nDo not operate the disk drive tray without a fan\nmodule for more than 5 minutes.\n \nSTEP 2.  Remove the fan module on the back of the\ndisk drive tray and replace it. 

$ #define RECGURU_TRAYED_FANS_LABEL 1169
1169 Multiple Fan Replacement

$ #define RECGURU_TRAYED_FANS_REPLACE1 1170
1170 Both fans in one of the disk drive trays have failed.\n \nReplace the fans as soon as possible to keep the drives\nfrom overheating. Consult your hardware manual for\nspecific details.

$ #define RECGURU_TRAYED_FANS_REPLACE2 1171
1171 \n \nSTEP 1.  Locate the disk drive tray with the fan module\nfault light on. Note that the fan module warning light\nmay also be on.\n \nCAUTION\nDo not operate the disk drive tray without a fan\nmodule for more than 5 minutes.

$ #define RECGURU_TRAYED_FANS_REPLACE3 1172
1172 \n \nSTEP 2.  Remove the fan module on the back of the disk\ndrive tray and replace it.\n \n>>>>>>>>>>Recovery Guru Procedure Is Complete

$ #define RECGURU_TRAYED_PWRSUPPLY_LABEL 1173
1173 Single Power Supply Replacement

$ #define RECGURU_TRAYED_PWRSUPPLY_REPLACE1 1174
1174 A power supply in one of the disk drive trays has failed.\n \nReplace the power supply as soon as possible because a failure\nto a second power supply may cause the drive tray to shut down.\nConsult your hardware manual for specific details.

$ #define RECGURU_TRAYED_PWRSUPPLY_REPLACE2 1175
1175 \n \nSTEP 1.  Locate the disk drive tray with the power supply\nfault light on.\n \nCAUTION\nDo not operate the disk drive tray without a fan\nmodule for more than 5 minutes.

$ #define RECGURU_TRAYED_PWRSUPPLY_REPLACE3 1176
1176 \n \nSTEP 2.  Remove the fan module on the back of the disk\ndrive tray and replace the faulty power supply. Be sure\nto reinstall the fan module.\n \n>>>>>>>>>>Recovery Guru Procedure Is Complete

$ #define RECGURU_TRAYED_PWRSUPPLIES_LABEL 1177
1177 Multiple Power Supply Replacement

$ #define RECGURU_TRAYED_PWRSUPPLIES_REPLACE1 1178
1178 Both power supplies in one of the disk drive trays have failed.\n \nConsult your hardware manual for specific details.\n \nSTEP 1.  Locate the disk drive tray with the two power supply\nfault lights on.

$ #define RECGURU_TRAYED_PWRSUPPLIES_REPLACE2 1179
1179 \n \nCAUTION\nDo not operate the disk drive tray without a\nfan module for more than 5 minutes.

$ #define RECGURU_TRAYED_PWRSUPPLIES_REPLACE3 1180
1180 \n \nSTEP 2.  Remove the fan module on the back of the disk\ndrive tray and replace the faulty power supplies. Be sure\nto reinstall the fan module.\n \n>>>>>>>>>>Recovery Guru Procedure Is Complete

$ #define RECGURU_TEMP_EXCEEDED_LABEL 1181
1181 Resolving A Temp. Exceeded Condition

$ #define RECGURU_TEMP_EXCEEDED_REPLACE1 1182
1182 An over-temperature condition has been detected in a\ndisk drive tray.\n \nThis is a critical condition that may cause the drive tray\nto be automatically turned off if you do not resolve\nthe condition within a short time.

$ #define RECGURU_TEMP_EXCEEDED_REPLACE2 1183
1183 \n \nSTEP 1. Locate the disk drive tray with the over-temperature\nlight on and determine if there is any corresponding\nfan fault lights on.

$ #define RECGURU_TEMP_EXCEEDED_REPLACE3 1184
1184 \n \n \nSTEP 2. If there are fan fault lights on, select OK and use\nthe appropriate Recovery Guru procedure to fix the fan\nfailure(s). If there are NOT any fan fault lights on,\nselect OK and fix any potential room cooling problems.

$ #define RECGURU_TEMP_EXCEEDED_REPLACE4 1185
1185 \n \nNOTE: The Recovery Guru will always show a No in the "Fixed?"\ncolumn for a temp. exceeded condition because it can only\nbe fixed by correcting the cause of the overheating.

$ #define RECGURU_TRAYED_FAN_REPLACE3 1186
1186  \n \n>>>>>>>>>>Recovery Guru Procedure Is Complete

$ #define DATA_PATH_CHECK_CABLES_TEXT1 1187
1187 CAUTION\nIf you are using the Networked version, make absolutely\ncertain there are no network problems BEFORE\nselecting OK. Selecting OK could cause an operational\ncontroller to be failed if the problem is really with the\nnetwork or its connection.

$ #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 Do you still want to use it?

$ #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 HS_INCORRECT_CAPACITY_OPENINGTEXT 1199
1199 The capacity of the new drive is not large enough to cover all of\nthe drives in the RAID Module. If a drive with a capacity larger\nthan the new drive fails, this new hot spare drive will not take\nover for it.

$ #define HS_INCORRECT_CAPACITY_STEPS 1200
1200 \n \nPlease read ALL of the following statements before proceeding:\n \n- If you want to use this new hot spare drive anyway, select OK.\n \n- If you do NOT want to use this new drive, replace it with one\n    with appropriate capacity, and then select OK.

$ #define HS_INCORRECT_CAPACITY_STEPS_2 1201
1201 \n \n- If you do not have another replacement drive, select Cancel.

$ #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 RECGURU_ENVIRON_REPLACE3 1209
1209 \nREAD ALL OF THESE STEPS AND WRITE THEM DOWN BEFORE PROCEEDING.\n \nSTEP 1.  If there are failed drives, record their locations (for example, [4,8], [4,9], etc.). They should\nall be in the drive tray associated with the failed environmental card.

$ #define RECGURU_ENVIRON_REPLACE4 1210
1210 \n \nSTEP 2.  Diagnose the card for possible problems and replace it if necessary. Make sure it has\nthe same ID as the failed card. You can skip step 3 if you have 2.05.02 or later controller firmware\nAND a system reboot or power cycle did NOT occur before you replaced the failed card.\n \nSTEP 3.  Turn the controller power switches off and on again\n \nSTEP 4.  Re-run the Recovery Guru. If you still see associated drive/channel failures, you MUST\nuse steps 5 and 6 to take care of these failures; otherwise, you are done with this procedure.

$ #define RECGURU_ENVIRON_REPLACE5 1211
1211 \n \nSTEP 5.  Select Options>>Manual Recovery>>Drives for the appropriate RAID Module. Stop all\nI/O processes to any LUNs with a DEAD status before going to step 6.

$ #define RECGURU_ENVIRON_REPLACE6 1212
1212 \n \nSTEP 6.  Take the appropriate action below:\n \n- If a drive has failed in a RAID 0, 1, 3, or 5 LUN (Dead status), highlight the drive(s), and select\nRevive.\n \n- If a drive has failed in a RAID 1, 3 or 5 LUN (Optimal or Degraded status),

$ #define RECGURU_ENVIRON_REPLACE7 1213
1213  highlight the drive(s)\nand select Reconstruct.\n \n>>>>>>>>>>Recovery Procedure Is Complete.

$ #define CONTROLLERS_FAILURE_REPLACE_TEXT3 1214
1214 \n \nNOTE\nBecause the controller serial number(s) will change with the new\ncontroller(s), the RAID Module number may change.

$ #define RECGURU_CHECK_REPLACED_CTRLS 1215
1215 Waiting for controllers to go online,\nand reestablishing module numbers.\n \nPlease wait...

$ #define RECGURU_MODULE_NAME_CHANGED 1216
1216 The module name has changed.\n \n"%s" is now "%s".

$ #define RECGURU_MODULE_LOST 1217
1217 Check the causes listed above; then select OK to exit\nthis procedure. You will need to exit and restart the\nRecovery Application once the module has been fixed.

$ #define RECGURU_NOTE_MODULE_NAME_CHANGED 1218
1218 \n \nNOTE\nThe old RAID Module name "%s" is no longer valid.\nInstead, it is now referred to as "%s".  You must\nreboot the host to enable RDAC protection on the module.

$ #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 RECGURU_MODULE_NAME_NOT_CHANGED 1221
1221 The module name has not changed.\n \n"%s" is still "%s".

$ #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_UNRESP_TITLE 1239
1239 Recovery Guru - Unresponsive Drives
 
$ #define RECGURU_UNRESP_TEXT1 1240
1240 The above drives in %s are Unresponsive (no longer accessible).\nIf these drives receive any I/O, the controller will fail them.\n \n
 
$ #define RECGURU_UNRESP_TEXT2 1241
1241 Unresponsive Drive Locations = %s
 
$ #define RECGURU_UNRESP_TEXT3 1242
1242 STEP 1.  If there is a failure of an Environmental Card (contained\nby some RAID modules), fix this first and rerun Recovery Guru.\n \nSTEP 2.  Ensure the affected drives are inserted correctly and\nrerun Recovery Guru.\n \n
 
$ #define RECGURU_UNRESP_TEXT4 1243
1243 NOTE: Recovery Guru will display both Unresponsive and Failed drives in the same\ndrive group as separate failure entries.  You should fix the Unresponsive drive(s) first\nstarting with step 1.  If the Unresponsive drives persist, try the next step.\n \n
 
$ #define RECGURU_UNRESP_TEXT5 1244
1244 a) If the associated LUNs are Optimal or Degraded, use Options>>Manual Recovery>>Drives.\nb) If the associated LUNs are Dead, use the command line utility drivutil as follows:\ndrivutil -f <drive location> <RAID module>\n
 
$ #define RECGURU_UNRESP_TEXT6 1245
1245 STEP 3.  If you fail the drives using this step and the associated LUNs are RAID 0\nor are in a degraded state, the data on those LUNs will be lost.\nFail the Unresponsive drive(s) using one of the options below and rerun Recovery Guru\nto replace these failed drives.\n \n

$ #define RECGURU_UNRESP_DRV 1246
1246 Unresponsive Drive             

$ #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 REC_FORMATERROR_EXCL 1268
1268 Could not format the LUN because either:\n \n1) an application is using the LUN,\n2) a filesystem is mounted on the LUN, or\n3) another host has the LUN reserved.\n \nIf another application is using the LUN, wait for the application to\nfinish or stop the application. If there are mounted filesystems on the\nLUN, dismount them. If another host has the LUN reserved, have that\nhost release the LUN. Afterwards, you can retry the operation.

$ #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 CANNOT_SECURE_ACCESS_TEXT2 1274
1274 \nIf you have mounted filesystems, it is best to unmount them\nbefore proceeding. However, this recovery procedure can continue\nwith mounted filesystems.

$ #define CONFIG_DEL_LUN_ERR_MSG2 1275
1275 to finish\nor stop the application. If there is a mounted filesystem on the LUN,\ndismount it. If the LUN is reconstructing, wait until reconstruction \nis complete. If another host has the LUNs reserved, have that host\nrelease those LUNs. Afterwards, you can retry the LUN deletion.

$ #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 Replace the battery as soon as possible. Then, use the -R parameter of the raidutil command line program to reset the battery age.

$ #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 Unrecoverable write error. The controller has detected that its batteries, as well as those of its alternate controller (if present) are not functioning.

$ #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 and Support 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 RECGURU_OFFLINE_TITLE 1407
1407 Drive Failed/Offline

$ #define RECGURU_OFFLINE_TEXT1 1408
1408 An interrupted write recovery process has failed during a controller\nreset or a power failure. The drives associated with this error have\nbeen failed and/or placed offline. You can recover the data on\nthese drives by performing the following steps:

$ #define RECGURU_OFFLINE_TEXT2 1409
1409 \n \nSTEP 1.  Start the Status Application and record the LUN number of\nany LUNs that reported a hardware error code of 3FEB.\n \nSTEP 2.  Stop all I/Os to the LUNs you recorded in step 1.

$ #define RECGURU_OFFLINE_TEXT3 1410
1410 \n \nSTEP 3.  Go to Options>>Manual Recovery>>Drives in the Recovery Application.\n \nSTEP 4.  Highlight the drives associated with the affected LUNs\n(the drives will have a status of Failed and/or Offline) and\nselect Revive.

$ #define RECGURU_OFFLINE_TEXT4 1411
1411 \n \nSTEP 5.  Go to Options>>Manual Recovery>>LUNs.\n \nSTEP 6.  Highlight the LUNs that you recorded in step 1 and select Format.

$ #define RECGURU_OFFLINE_TEXT5 1412
1412 \n \nSTEP 7.  Restore the data from back-up to the LUNs you formatted in step 6.

$ #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 SPLIT_DATAPATH_HOST2_INTRO 1416
1416 Cannot communicate with the controller connected to\nhost %s.\n \nNOTE: You must perform several steps from the other\nhost (host #2).\n \nPerform the following steps from host #2:\n \nSTEP 1.  Start the Recovery Application and select the same RAID Module.

$ #define SPLIT_DATAPATH_HOST2_STEPSA 1417
1417 \n \nSTEP 2.  Select Module Profile.\na. Select Drives. Record LUNs with an inaccessible status.\nb. Select Controllers. Record firmware version of the good controller.\n \nSTEP 3.  From the top menu, select Options>>Manual Recovery>>Controller Pairs.

$ #define SPLIT_DATAPATH_HOST2_STEPSB 1418
1418 \na. Highlight the inaccessible controller and select Place Offline.\nb. Replace the controller.\nc. Highlight the offline (inaccessible) controller and select Place Online.\n \nYou are done with host #2.\n \nSTEP 4. Select OK only after performing steps 1-3.

$ #define SPLIT_DATAPATH_FIRMWARE_CHECK_TITLE 1419
1419 Firmware Check

$ #define SPLIT_DATAPATH_FIRMWARE_CHECK 1420
1420 \nPerform the following steps from host %s:\n \nSTEP 5.  Start the Maintenance Application and select Module Profile>>Controllers.\n \nCompare the firmware versions of the new controller connected to host\n%s and the controller from host #2 that you recorded

$ #define SPLIT_DATAPATH_FIRMWARE_CHECK1 1421
1421  in step 2.\n \n-- If the versions match, select OK.\n \n-- If they do NOT match, go to the Maintenance Application for the applicable\nhost and select Firmware Upgrade. Download the firmware to the\ncontroller using the Offline Method. Then select OK.

$ #define SPLIT_DATAPATH_LUNDIST_TITLE 1422
1422 Automatic LUN Re-Distribution

$ #define SPLIT_DATAPATH_MANUAL_LUNDIST_TITLE 1423
1423 Manual LUN Re-Distribution

$ #define SPLIT_DATAPATH_LUNDIST1 1424
1424 \nSTEP 6.  Do you want to re-distribute all LUNs that were previously\nowned by host %s?\n \nWARNING\nStop all I/Os to the LUNs you recorded in step 2 before selecting Yes.\n \n-- If you select Yes, the LUNs will be automatically distributed back\n

$ #define SPLIT_DATAPATH_LUNDIST2 1425
1425 to host %s.\n \n-- If you select No, you will be provided instructions on how to\nre-distribute the LUNs manually for more control of the\nLUN re-distribution.

$ #define SPLIT_DATAPATH_LUNDIST_MANUAL1 1426
1426 Perform the following steps using the Maintenance Application\nfrom host %s.\n \nSTEP 7.  Select Controller Mode. Change the controller pair to Active/Active.\n \nWARNING\nBefore performing step 8, stop I/Os to the LUNs you want to re-distribute\n to host %s.

$ #define SPLIT_DATAPATH_LUNDIST_MANUAL2 1427
1427 \n \nSTEP 8.  Select LUN Balancing. Highlight the drive groups with the LUNs that\nyou recorded in step 2 and select Move and then Save.

$ #define UNREGISTER_MODULE_FAILED 1428
1428 Could not unregister the module. Try again later.\n

$ #define EXIT_GURU_EARLY 1429
1429 You have chosen to exit this procedure before it is complete.\n \nDo you really want to exit this procedure?\n \n-- Select Yes to exit.\n \n-- Select No to continue with this procedure.

$ #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 host names you entered are not in the proper order.\nPlease switch the host names.

$ #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 CHANNEL_FAILURE_TEXT2 1450
1450 \n \nDo NOT attempt to fix the channel failure without\nreading the information on the next screen.

$ #define CHANNEL_FAILURE_TEXT3 1451
1451 CAUTION\nRead all of the steps and write them down before proceeding. Do NOT re-rerun Health\nCheck or Recovery Guru until you have performed steps 1-4. 

$ #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 CHANNEL_FAILURE_TEXT4 1455
1455 \n \nSTEP 1.  Fix the problem causing the channel failure. Consult appropriate hardware\nmanuals or a Customer Services Representative.\n \nSTEP 2.  Select Options>>Manual Recovery>>Drives for the affected RAID Module.

$ #define CHANNEL_FAILURE_TEXT5 1456
1456 \n \nCAUTION\nStop all I/Os to any LUNs with a Dead status before performing Step 3.\n \nSTEP 3.  Take the appropriate action below:\n \n-- If a drive has failed in a RAID 0 LUN (dead status), highlight the drive(s)\nand select Revive.

$ #define CHANNEL_FAILURE_TEXT6 1457
1457 \n \n-- If a drive has failed in a RAID 1, 3, or 5 LUN (degraded or optimal status),\nhighlight the drive(s) and select Reconstruct.\n \n-- If a drive has failed in a RAID 1, 3, or 5 LUN (dead status), highlight the\ndrive(s) and select Revive.

$ #define CHANNEL_FAILURE_TEXT7 1458
1458 \n \nSTEP 4.  Run manual parity check/repair on any LUNs that had a dead status. If\nthere are NO inconsistencies reported, then the procedure is complete. If there\nare inconsistencies reported, you need to restore the data from back-up.

$ #define INTERNAL_PROCESSING_ERROR 1459
1459 An internal processing error occured 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 PRODUCT_NAME_ABOUT_BOX_OEM 1469
1469 RAID Manager
 
$ #define PRODUCT_NAME_OEM 1470
1470 RAID Manager

$ #define OEM_ICONIZED_NAME 1471
1471 rm6

$ #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 CANNOT_SECURE_ACCESS_TEXT3 1476
1476 \nPress OK to return to the main Recovery Guru screen.\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 FWUTIL_USAGE_1 1484
1484 \n     fwutil <file> <raid controller specifier>


$ #define FWUTIL_USAGE_2 1485
1485 \n


$ #define FWUTIL_USAGE_3 1486
1486 \n     fwutil -?

$ #define FWUTIL_USAGE_END 1487
1487 \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 ] [ -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 ge 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 STORUTIL_USAGE_1 1549
1549 \n     storutil  -c <raid module specifier>


$ #define STORUTIL_USAGE_2 1550
1550 \n               [ -w clear host store ]


$ #define STORUTIL_USAGE_3 1551
1551 \n               [ -n <new module name> change module name ]


$ #define STORUTIL_USAGE_4 1552
1552 \n               [ -i <on | off> independent controller setting ]


$ #define STORUTIL_USAGE_5 1553
1553 \n               [ -? display usage information ]

$ #define STORUTIL_USAGE_END 1554
1554 \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 CONTROLLERS_FAILURE_REPLACE_TEXT4 1604
1604 \n \n \nSTEP 2.  Record the hardware ethernet address of the new controller(s).\nThere is a label located near the back of the controller canister.\n \n \nSTEP 3.  Insert the new controller(s) firmly into the RAID Module.\n \n \nSTEP 4.  Look up the record on the bootp server for the failed controller,\nand change only the hardware ethernet address entry to the one you recorded\nin step 2.  Make sure you do NOT change the host name and IP address.\n \n \nSTEP 5.  Select OK below only after performing steps 1-4.

$ #define REMOVE_RAIDMOD_CAUTION	1605
1605 \n \nCAUTION\nBefore continuing, make sure you disconnect the SCSI\ncable between the host and the RAID Module; otherwise\nthe RAID Module will continue to be shown each time\nyou enter an application.

$ #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 Using 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 UNIT_FAILURE_TEXT	1640
1640 Logical unit(s) %s in %s are dead.\n \nA Unit Failure represents a Dead LUN that is caused by either:\n \n- Unformatted LUN(s) containing Replaced drives:\nThis is the result of an aborted Dead LUN recovery process\nwhere Failed drives were Replaced but the LUN was not formatted.\nClick OK to format the affected LUN(s).\n \n- Failed drives that were caused by a channel failure:\nRecovery Guru will display a channel failure entry. Click Cancel\nand repair the channel failure first, then rerun the Recovery Guru.

$ #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 RECGURU_UNRESP_LUNS 1643
1643 Affected Logical Units (LUNs) = %s\nLUN Status = %s\nRAID Level = %d\n \n

$ #define EVENT_AEN_4081_CAUSE 1644
1644 The controller has detected a bad memory module. This controller will remain inoperative until you replace it with a new controller.

$ #define EVENT_AEN_4081_ACTION 1645
1645 Use Options>>Manual Recovery>>Controller Pairs in the Recovery application to determine if the controller listed in this message is offline. If the controller is not offline, then place it offline. Use Recovery Guru to replace the controller.

$ #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 ST_DET_MSG_AFF_LBL12			1664
1664 Affected Component:     Drive Channel %s\n

$ #define CACHE_BATTERY_FAILURE			1665
1665 Cache Battery

$ #define CACHE_BATTERY_FAULT			1666
1666 Cache Battery Fault            

$ #define RECGURU_CACHE_BATT_LABEL		1667
1667 Resolving A Cache Battery Failure Condition

$ #define CACHE_BATTERY_REPLACE1		1668
1668 \nThe battery and its replacement procedure vary depending on the type of RAID Module\n you have.  The following steps provide common procedures you will need to perform for\nthe battery replacement.  Consult your hardware manual for specific details.\n\nSTEP 1. Stop all I/O and turn off the power to the RAID Module.\n\nSTEP 2. Remove the battery cannister and replace it with a new one.

$ #define CACHE_BATTERY_REPLACE2		1669
1669 \n\nSTEP 3. Record today's date (installation) and the new replacement date on the label.\n             The replacement date is 2 years from the installation date.\n\nSTEP 4. Use the raidutil command line utility as follows to reset the battery age for\n              EACH controller (device) in the RAID Module:\n\n            raidutil -c <device name> -R

$ #define CACHE_BATTERY_REPLACE3		1670
1670 \n\n If you need information on the device name, select Module Profile and look at the Summary\n Information screen.\n\n

$ #define CACHE_BATTERY_CAUSE			1671
1671 A cache battery alert has been detected

