4 * Text: "%s: The DASD has been put in the quiesce state\n"
5 * Severity: Informational
7 * @1: bus ID of the DASD
9 * No I/O operation is possible on this device.
11 * Resume the DASD to enable I/O operations.
15 * Text: "%s: I/O operations have been resumed on the DASD\n"
16 * Severity: Informational
18 * @1: bus ID of the DASD
20 * The DASD is no longer in state quiesce and I/O operations can be performed
27 * Text: "%s: The DASD cannot be formatted while it is enabled\n"
30 * @1: bus ID of the DASD
32 * The DASD you try to format is enabled. Enabled devices cannot be formatted.
34 * Contact the owner of the formatting tool.
38 * Text: "%s: The specified DASD is a partition and cannot be formatted\n"
41 * @1: bus ID of the DASD
43 * The DASD you try to format is a partition. Partitions cannot be formatted
44 * separately. You can only format a complete DASD including all its partitions.
46 * Format the complete DASD.
47 * ATTENTION: Formatting irreversibly destroys all data on all partitions
52 * Text: "%s: Formatting unit %d failed with rc=%d\n"
55 * @1: bus ID of the DASD
59 * The formatting process might have been interrupted by a signal, for example,
60 * CTRL+C. If the process was not interrupted intentionally, an I/O error
61 * might have occurred.
63 * Retry to format the device. If the error persists, check the log file for
64 * related error messages. If you cannot resolve the error, note the return
65 * code and contact your support organization.
72 * Text: "%s: start_IO run out of retries and failed with request %s\n"
75 * @1: bus ID of the DASD
76 * @2: pointer to request
78 * The start IO function tried to start an IO request but the number
79 * of retries for the I/O was exceeded before the request could be started.
81 * Check for related previous error messages.
85 * Text: "%s: Cancelling request %p failed with rc=%d\n"
88 * @1: bus ID of the DASD
89 * @2: pointer to request
90 * @3: return code of previous function
92 * In response to a user action, the DASD device driver tried but failed to
93 * cancel a previously started I/O operation.
95 * Try the action again.
99 * Text: "%s: Flushing the DASD request queue failed for request %p\n"
102 * @1: bus ID of the DASD
103 * @2: pointer to request
105 * As part of the unloading process, the DASD device driver flushes the
106 * request queue. This failed because a previously started I/O operation
107 * could not be canceled.
109 * Try again to unload the DASD device driver or to shut down Linux.
113 * Text: "The DASD device driver could not be initialized\n"
114 * Severity: Informational
116 * The initialization of the DASD device driver failed because of previous
119 * Check for related previous error messages.
123 * Text: "%s: Accessing the DASD failed because it is in probeonly mode\n"
124 * Severity: Informational
126 * @1: bus ID of the DASD
128 * The dasd= module or kernel parameter specified the probeonly attribute for
129 * the DASD you are trying to access. The DASD device driver cannot access
130 * DASDs that are in probeonly mode.
132 * Change the dasd= parameter as to omit probeonly for the DASD and reload
133 * the DASD device driver. If the DASD device driver has been compiled into
134 * the kernel, reboot Linux.
138 * Text: "%s: cqr %p timed out (%is), %i retries remaining\n"
141 * @1: bus ID of the DASD
142 * @2: pointer to request
144 * @4: number of retries left
146 * One try of the error recovery procedure (ERP) for the channel queued request
147 * (cqr) timed out and failed to recover the error. ERP continues for the DASD.
149 * Ignore this message if it occurs infrequently and if the recovery succeeds
150 * during one of the retries. If this error persists, check for related
151 * previous error messages and report the problem to your support organization.
155 * Text: "%s: cqr %p timed out (%is) but cannot be ended, retrying in 5 s\n"
158 * @1: bus ID of the DASD
159 * @2: pointer to request
162 * A try of the error recovery procedure (ERP) for the channel queued request
163 * (cqr) timed out and failed to recover the error. The I/O request submitted
164 * during the try could not be canceled. The ERP waits for 5 seconds before
167 * Ignore this message if it occurs infrequently and if the recovery succeeds
168 * during one of the retries. If this error persists, check for related
169 * previous error messages and report the problem to your support organization.
173 * Text: "%s: The DASD cannot be set offline while it is in use\n"
176 * @1: bus ID of the DASD
178 * The DASD cannot be set offline because it is in use by an internal process.
179 * An action to free the DASD might not have completed yet.
181 * Wait some time and set the DASD offline later.
185 * Text: "%s: The DASD cannot be set offline with open count %i\n"
188 * @1: bus ID of the DASD
191 * The DASD is being used by one or more processes and cannot be set offline.
193 * Ensure that the DASD is not in use anymore, for example, unmount all
194 * partitions. Then try again to set the DASD offline.
198 * Text: "%s: Setting the DASD online failed with rc=%d\n"
201 * @1: bus ID of the DASD
204 * The DASD could not be set online because of previous errors.
206 * Look for previous error messages. If you cannot resolve the error, note
207 * the return code and contact your support organization.
211 * Text: "%s Setting the DASD online with discipline %s failed with rc=%i\n"
214 * @1: bus ID of the DASD
218 * The DASD could not be set online because of previous errors.
220 * Look for previous error messages. If you cannot resolve the error, note the
221 * return code and contact your support organization.
225 * Text: "%s Setting the DASD online failed because of missing DIAG discipline\n"
228 * @1: bus ID of the DASD
230 * The DASD was to be set online with discipline DIAG but this discipline of
231 * the DASD device driver is not available.
233 * Ensure that the dasd_diag_mod module is loaded. If your Linux system does
234 * not include this module, you cannot set DASDs online with the DIAG
239 * Text: "%s Setting the DASD online failed because of a missing discipline\n"
242 * @1: bus ID of the DASD
244 * The DASD was to be set online with a DASD device driver discipline that
247 * Ensure that all DASD modules are loaded correctly.
250 ---------------------------
253 * Text: "The statistics feature has been switched off\n"
254 * Severity: Informational
256 * The statistics feature of the DASD device driver has been switched off.
262 * Text: "The statistics feature has been switched on\n"
263 * Severity: Informational
265 * The statistics feature of the DASD device driver has been switched on.
271 * Text: "The statistics have been reset\n"
272 * Severity: Informational
274 * The DASD statistics data have been reset.
280 * Text: "%s is not a supported value for /proc/dasd/statistics\n"
285 * An incorrect value has been written to /proc/dasd/statistics.
286 * The supported values are: 'set on', 'set off', and 'reset'.
288 * Write a supported value to /proc/dasd/statistics.
292 * Text: "%s is not a valid device range\n"
297 * A device range specified with the dasd= parameter is not valid.
299 * Examine the dasd= parameter and correct the device range.
303 * Text: "The probeonly mode has been activated\n"
304 * Severity: Informational
306 * The probeonly mode of the DASD device driver has been activated. In this
307 * mode the device driver rejects any 'open' syscalls with EPERM.
313 * Text: "The IPL device is not a CCW device\n"
316 * The value for the dasd= parameter contains the 'ipldev' keyword. During
317 * the boot process this keyword is replaced with the device from which the
318 * IPL was performed. The 'ipldev' keyword is not valid if the IPL device is
321 * Do not specify the 'ipldev' keyword when performing an IPL from a device
322 * other than a CCW device.
326 * Text: "A closing parenthesis ')' is missing in the dasd= parameter\n"
329 * The specification for the dasd= kernel or module parameter has an opening
330 * parenthesis '(' * without a matching closing parenthesis ')'.
332 * Correct the parameter value.
336 * Text: "The autodetection mode has been activated\n"
337 * Severity: Informational
339 * The autodetection mode of the DASD device driver has been activated. In
340 * this mode the DASD device driver sets all detected DASDs online.
346 * Text: "%*s is not a supported device option\n"
349 * @1: length of option code
352 * The dasd= parameter includes an unknown option for a DASD or a device range.
353 * Options are specified in parenthesis and immediately follow a device or
356 * Check the dasd= syntax and remove any unsupported options from the dasd=
357 * parameter specification.
361 * Text: "PAV support has be deactivated\n"
362 * Severity: Informational
364 * The 'nopav' keyword has been specified with the dasd= kernel or module
365 * parameter. The Parallel Access Volume (PAV) support of the DASD device
366 * driver has been deactivated.
372 * Text: "'nopav' is not supported on z/VM\n"
373 * Severity: Informational
375 * For Linux instances that run as guest operating systems of the z/VM
376 * hypervisor Parallel Access Volume (PAV) support is controlled by z/VM not
379 * Remove 'nopav' from the dasd= module or kernel parameter specification.
383 * Text: "High Performance FICON support has been deactivated\n"
384 * Severity: Informational
386 * The 'nofcx' keyword has been specified with the dasd= kernel or module
387 * parameter. The High Performance FICON (transport mode) support of the DASD
388 * device driver has been deactivated.
394 * Text: "The dasd= parameter value %s has an invalid ending\n"
397 * @1: parameter value
399 * The specified value for the dasd= kernel or module parameter is not correct.
401 * Check the module or the kernel parameter.
405 * Text: "Registering the device driver with major number %d failed\n"
410 * Major number 94 is reserved for the DASD device driver. The DASD device
411 * driver failed to register with this major number. Another device driver
412 * might have used major number 94.
414 * Determine which device driver uses major number 94 instead of the DASD
415 * device driver and unload this device driver. Then try again to load the
416 * DASD device driver.
420 * Text: "%s: default ERP has run out of retries and failed\n"
423 * @1: bus ID of the DASD
425 * The error recovery procedure (ERP) tried to recover an error but the number
426 * of retries for the I/O was exceeded before the error could be resolved.
428 * Check for related previous error messages.
432 * Text: "%s: Unable to terminate request %p on suspend\n"
435 * @1: bus ID of the DASD
436 * @2: pointer to request
438 * As part of the suspend process, the DASD device driver terminates requests
439 * on the request queue. This failed because a previously started I/O operation
440 * could not be canceled. The suspend process will be stopped.
442 * Try again to suspend the system.
446 * Text: "%s: ERP failed for the DASD\n"
449 * @1: bus ID of the DASD
451 * An error recovery procedure (ERP) was performed for the DASD but failed.
453 * Check the message log for previous related error messages.
457 * Text: "%s: An error occurred in the DASD device driver, reason=%s\n"
460 * @1: bus ID of the DASD
463 * This problem indicates a program error in the DASD device driver.
465 * Note the reason code and contact your support organization.