4 * Text: "%s: A 64-bit DIAG call failed\n"
7 * @1: bus ID of the DASD
9 * 64-bit DIAG calls require a 64-bit z/VM version.
11 * Use z/VM 5.2 or later or set the sysfs 'use_diag' attribute of the DASD to 0
16 * Text: "%s: Accessing the DASD failed because of an incorrect format (rc=%d)\n"
19 * @1: bus ID of the DASD
22 * The format of the DASD is not correct.
24 * Check the device format. For details about the return code see the
25 * section about the INITIALIZE function for DIAGNOSE Code X'250'
26 * in "z/VM CP Programming Services". If you cannot resolve the error, note
27 * the return code and contact your support organization.
31 * Text: "%s: New DASD with %ld byte/block, total size %ld KB%s\n"
32 * Severity: Informational
34 * @1: bus ID of the DASD
39 * A DASD with the indicated block size and total size has been set online.
40 * If the DASD is configured as read-only to the real or virtual hardware,
41 * the message includes an indication of this hardware access mode. The
42 * hardware access mode is independent from the 'readonly' attribute of
43 * the device in sysfs.
49 * Text: "%s: DIAG ERP failed with rc=%d\n"
52 * @1: bus ID of the DASD
55 * An error in the DIAG processing could not be recovered by the error
56 * recovery procedure (ERP) of the DIAG discipline.
58 * Note the return code, check for related I/O errors, and report this problem
59 * to your support organization.
63 * Text: "%s: DIAG initialization failed with rc=%d\n"
66 * @1: bus ID of the DASD
69 * Initializing the DASD with the DIAG discipline failed. Possible reasons for
70 * this problem are that the device has a device type other than FBA or ECKD,
71 * or has a block size other than one of the supported sizes:
72 * 512 byte, 1024 byte, 2048 byte, or 4096 byte.
74 * Ensure that the device can be written to and has a supported device type
75 * and block size. For details about the return code see the section about
76 * the INITIALIZE function for DIAGNOSE Code X'250' in "z/VM CP Programming
77 * Services". If you cannot resolve the error, note the error code and contact
78 * your support organization.
82 * Text: "%s: Device type %d is not supported in DIAG mode\n"
85 * @1: bus ID of the DASD
88 * Only DASD of type FBA and ECKD are supported in DIAG mode.
90 * Set the sysfs 'use_diag' attribute of the DASD to 0 and try again to access
95 * Text: "Discipline %s cannot be used without z/VM\n"
96 * Severity: Informational
100 * The discipline that is specified with the dasd= kernel or module parameter
101 * is only available for Linux instances that run as guest operating
102 * systems of the z/VM hypervisor.
104 * Remove the unsupported discipline from the parameter string.
108 * Text: "%s: The access mode of a DIAG device changed to read-only"
111 * @1: bus ID of the DASD
113 * A device changed its access mode from writeable to
114 * read-only while in use.
116 * Set the device offline, ensure that the device is configured correctly in
117 * z/VM, then set the device online again.